Understanding what functionality the Product Owner desires within the next Sprint and figuring out how to do it.

Updating the scope of the release with all Sprints, end dates, and costs

Reviewing current functionality that binds the software solution

Recalculating empirical velocity, adjusting team capacity accordingly, and projecting end dates

Remove Carlos from the team.

Use Carlos as an asset, particularly during risk identification

Ignore him and hope it goes away

Escalate the issue with the higher authorities

At the end of every Sprint

When the Team feels is done with every Sprint

Whenever the increment is free of defects

When it makes sense

To share with the team what each member has completed in the Sprint, what each member will work on next, and to report progress roadblocks

To give a status report to the Product Owner on what each member has completed in the Sprint, what each member will work on next, and to report progress roadblocks.

To discuss work details with the team since every team member must attend the meeting

To give a status report to the Scrum Master on what each member has completed in the Sprint, what each member will work on next, and to report progress roadblocks.

As long as it takes

1 hour

45 minutes

15 minutes

15 minutes, proportionally less for shorter Sprints

Undefined or poorly defined Product Backlog items should be placed on the Product Backlog with a low priority

All Product Backlog items are the result of a(n) analysis, requirements and/or design phase(s).

Undefined or poorly defined Product Backlog items should be kept out from the Product Backlog until sufficient detail is known.

Every Product Backlog item, whether low priority or high priority, should possess sufficient detail for the Team to complete in a Sprint.

Establish priorities together with product owner for Product Backlog items

Preventing Senior Management from shifting team priorities

Empowering the team

Socializing scrum throughout the organization

A graph indicating what has been completed by the Scrum Team

A measure of the remaining Product Backlog across the time of a release plan

What has been completed by the Scrum Team to date

The work remaining to be completed by the Product Owner

Forming. Storming. Norming. Performing

Low. Medium. High

Developing. Shaping. Finishing

Gathering. Building. Developing. Educating

release planning

backlog planning

sprint planning

product planning