During a retrospective, a team member claims that a specific set of documentation that is continuously updated during iterations is not being used by any stakeholder. What should the team do?
An agile team had unexpected technical problems in a project and was not able to complete the deliverables on time. During the retrospective meeting, the team openly discussed the causes for these issues and what can be done to avoid similar situations in the future.
What agile values and principles did the team demonstrate?
On an agile project, some of the development team is struggling to understand how the tasks and user stones fit into the overall product. How should this be addressed?
What should a Scrum Master do when one team member falls behind in their tasks?
A client has provided their requirements and deadline to the project team. The requirements are confusing, and the team is frustrated.
What should the team's servant leader do?
A project manager noticed that a team member had been a consistently high performer until a few months ago. Recently, the team member seems distracted and is not performing well.
How should the project manager handle a review with the team member?
The product owner is present at the sprint review meeting and states that an estimation for the end of the project must be shared with the company’s steering committee. The scrum master declares that the team reached an average velocity of 40 story points per sprint, considering a biweekly iteration. The team members predict that there are 240 story points remaining.
What is the estimated project conclusion?
The coach on a new agile team notices that one team member is influencing most of the team's decisions. What should the coach do?
A project team's manager is responsible for delivering a specific initiative for the organization. They are preparing for a monthly meeting where the manager will present on the current state of this initiative. The agile project lead sends the manager the following email with the current initiative status (see Exhibit A).
At the end of which sprint will the minimum viable product (MVP) be completed?
During a sprint, the team encounters a technical problem that becomes an impediment to completing two stories What should the scrum master do?
Velocity = 40 story points per sprint
Remaining Work = 240 story points
Sprint Duration = 2 weeks
Accessibility – color blind → 4 story points
Increase security → 21 story points
Add AI chatbot → 5 story points
The risk register mentions a reduction of 1 story point per sprint from sprints 4 through 6 due to the holiday schedule.
If we assume the team's normal velocity is 10 story points per sprint (hypothetically), it would drop to 9 story points per sprint for sprints 4-6.