[Tarun Bhatt] MO
Operational part:
Align team on vision of product than identify gap which are mostly around, DOD n DOR for stories, Also setup a clear n Transparent process for BAU’s, Support Tickets.

Coaching part:
Coach team for Agile values (commitment, Courage, openness, focus, n Respect)n impact on product.

[Chethan Venkateshan] My observation usually teams missing sprint goals often have these challenges some times combination of them. As coach mostly I work with teams to commit to achieve the smallest possible goal keeping aside velocity and capacity math aside and observe who and what is disturbing them is achieving the sprint goal and start working on it collectively

1. Lack of Visualisation of Progress: Team fail to track progress of work towards sprint goal.
2. Hung up on Scrum : Team is hug upon scrum even though consistently there is flow of work more than 50% of work is unpredictable. No inspect and adapt system in place
3. Gold-Plating: Expand the scope of the Sprint beyond the agreed-upon Sprint Goal by adding extra, unnecessary work to the Product Backlog items in the Sprint Backlog.
4. PBI not aligned to sprint goal: Team picking stories that are unrelated to Sprint Goal.
5. Decided Sprint Goal: Sprint Goal is not a collective decision of the team but rather dictated by an individual, often a dominant PO or tech lead.

[Manoj Jha] Some of the reasons for missing Sprint goals. First, find out the reasons or causes:
1. Overcommitment 2. Incomplete requirements 3. Scope changes 4. Dependency bottlenecks
5. Technical Challenges 6. Poor Estimation 7. Team Member Availability 8. Lack of Experience
9. Inadequate testing (Not allocating sufficient time for testing activities) 10. Unclear DOD
11. External Factor 12. Ineffective Sprint Planning 13. Lack of Continuous Improvement 14. Changing Priorities.

If above all points or the checklist is as per expected. Due to unforeseen issues, if the team struggles to meet the sprint goal in such cases the following points can be evaluated.
1. Assess the situation 2. Review Sprint Goal and Commitment.
3. Evaluate the Spring Backlog 4. Identify Impediments
5. Reinforce Agile Practices (i.e. Task breakdown, Daily Standup, Backlog refinement etc.)
6. Adjust Scope 7. Monitor Progress 8. Collaborate with Product Owner
9. Engage the team 10. Provide Support and Motivation 11. Retrospective action items 12. Escalate if necessary 13. Learning and Adaptation.

[Rashmi Mhadesar] Immediate action Plan will be
1. Set up a meeting with scrum team to understand there challenges
2. Understand whether team is aware of DOD
3. During retrospective meeting understand the reasons of spill over and create a action item plan. In retrospective we will understand whether it's technology issue, Skills or resource issue.

Long term action Plan will be
1. Make sure during sprint planning team understands the Sprint Goal
2. May be team is not fully aware of the skills needed for delivery
3. If team fixing defects which are not related to story so its actually as part of new implementation and will need a story in future release. Scrummaster should guide team about same
4. Dependent teams are not ready so before release planning commitment of dependent team is needed
5. Environment not being stable
6. Test data is not ready so team should have task of test data analysis one sprint ahead
7. Requirements changing frequently and this impacts team sprint Goal
8. In sprint automation challenges when it's part of DOD
9. Team members not collaborating and communicating