When all committed Product Backlog items meet their definition of "Done"
When the timebox expires
When all tasks are complete
Inform the Product Owner so he/she can work with the CEO
Add it to the current sprint while swapping out the committed work of equal size
Add it to the next sprint
Add it to the current sprint.
Nail down the architecture
Build a thin slice of potentially ship-able functionality
Develop a detailed plan for the rest of the project
Test the product
Scrum Master, with inputs from Scrum team.
Product Owner, with inputs from Scrum Team
Scrum Team, after clarifying the requirement.
Project Manager and Stakeholders
Coordinating daily during the sprint to meet the sprint goal.
Resolving internal conflicts.
Increasing productivity and learning.
Selecting the product owner.
Planning how to meet the Sprint goal.
Never, Sprint tasks are fixed and are decided during sprint planning.
When Product Owner identifies a new task.
When Scrum Master approves them.
As soon as possible after they are identified, unless they reflect a scope change in sprint goals, or committed Product Backlog items.
Act as a go-between for them.
Teach the team to talk in terms of business needs and objectives.
Listen to their communications.
Teach the product owner about technologies the team uses
No Rules, only guidelines.
As soon as QC team is available.
Every time the code changes
Once per night or day
Once a week
To get more features out.
To accelerate our understanding of the users needs.
It gets larger as it contains list of completed items.
It gets smaller as the teams complete all tasks.
It gets smaller because the scrum master removes all tasks that are not needed
It gets larger as the Sprint Review demonstration prompts requests for more or different features.
Always, The product owner should re-prioritize the backlog constantly as we learn more.
Sometimes, before the elaboration stage gate.
At the end of each sprint, after the sprint review meeting
At the beginning of the project
At the end of the project
Depends on the Scrum Masters availability.
Are doing it as well as possible.
Have modified the difficult, uncomfortable parts that could have led to breakthroughs.