• Product Owner is responsible for creating and ordering a list of features. This is the Product Backlog, a complete but ever changing work items list for the project.
• Before each Sprint, the Development Team decides in a Plan Sprint meeting, how many of the highest ordered features they can deliver during the Sprint. The Team decides how to create the increment and decides what tasks are necessary and enters them into the Sprint Backlog.
• During the Sprint, the Development Team coordinates their work in a Hold Daily Scrum meeting and tracks the progress in the Sprint Burndown Chart .
• The Scrum Master coaches the team, removes impediments and ensures that the team is working effectively.
• During the Sprint, valuable functionality is developed and a potentially shippable product increment is created and demonstrated to the Product Owner and stakeholders during a Conduct Sprint Review meeting.
• The Team reflects on the Sprint during a Conduct Sprint Retrospective and identifies concrete process improvement for the next Sprint.

Sprint guidelines

• Time-box of one month or less during which “done”, usable and potentially releasable product increment is produced
• The duration of Sprints is consistent for a team and should not be more than one month
• New Sprint starts immediately after the conclusion of the previous one
• No changes made that would put the Sprint goal at risk
• Quality goals do not decrease
• Scope may be clarified and re-negotiated with Product Owner

Cancelling a Sprint

• Sprint can be cancelled before its time-box is over, however, cancellation rarely makes sense
• Only the Product Owner has the authority to cancel a Sprint, although he/she may do so under the influence from the Development Team, the Scrum Master, or the Stakeholders
• A Sprint would be cancelled if its Sprint Goal becomes obsolete, or if it no longer makes sense to complete the Sprint. Examples: Changes in company direction, technology and/or market
• Any completed and done work is evaluated. Product Owner accepts or rejects work. All incomplete and still viable Product Backlog items are put back on the Product Backlog