A product owner with experience in a predictive approach wants the team to develop very detailed schedules and cost estimates for the next 10 sprints. What should the Scrum Master do?
A.
Suggest the product owner start by focusing on the next 2 sprints instead of 10
B.
Spend the first few sprints to develop detailed schedules and budgets
C.
Invite the product owner to the retrospective to explain the team's approach to schedule and budget
D.
Explain that detailed project schedules and budgets are not artefacts in agile projects
I'll go with D. It is the job of the SM do make the team including the PO aware of the Agile principles and mindset. Option A doesn't really communicate the agile principles to the PO but is merely an authoritative way of communicating ( not recommended in Agile). Option B is against the Agile principles since there are no detailed budgets and schedules and these are artifacts of the predictive project management. Option C leaves the resolution to the issues on hand to the retro which is done after the sprint, leaves it too late so incorrect. Option D is a direct and most suitable option without wasting any time. I would go with D.
A. Suggest the product owner start by focusing on the next 2 sprints instead of 10
Explanation:
Incremental Planning: Agile methodologies emphasize incremental and iterative planning. Focusing on the next 2 sprints allows the team to adapt to changes and feedback more effectively.
Flexibility: Detailed schedules and cost estimates for 10 sprints can be rigid and may not accommodate the dynamic nature of agile projects. Shorter planning horizons provide the flexibility to adjust as needed.
Learning and Improvement: By focusing on shorter time frames, the team can learn from each sprint and improve their estimates and planning processes over time.
Stakeholder Engagement: This approach helps in managing the product owner's expectations and gradually transitioning them from a predictive to an agile mindset.
D = correct. Schedules are milestones and it is good to know, but budgets are irrelevant information to the developers.
C = wrong. Retro is not about that.
D) - Being agile, rather than doing agile(A). C) doesn't make sense,because retrospectives are not intented to educate the PO + it will take a lot of time.
I assume that C is the best answer.
Scrum Master should coach team and the company about agile methods and mindsets.
Answers A and D just poing P.O. to some solution without coaching.
Answer C explains and coaches P.O. about agile methods.
C is absolutely wrong as retrospective is for what is going well, where could use improvements, and what should be done differently.
For me A is the best choice for this approach.
It should be A, retrospective is not a meeting to explain the team approach
upvoted 2 times
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
saponazureguy
Highly Voted 3 years, 5 months agothewalker
Most Recent 3 weeks agoNhuho
1 year, 2 months agoPetrevski
1 year, 4 months agoAzharmak
1 year, 4 months agoTroplev
1 year, 5 months agoMinhha3
1 year, 5 months agorichck102
2 years, 2 months agothuha1704
2 years, 6 months agoAlaaradwan
3 years, 2 months agoDsugandhi
3 years, 3 months agoSILLYACP
3 years, 5 months agosrv3
3 years, 9 months agohadecrown
3 years, 6 months agosnow5
3 years, 10 months agotsangckl
3 years, 11 months ago