The Daily Scrum is a short (usually limited to 15 minutes) discussion where the team coordinates their activities for the following day. This protects the team from scope changes within that Sprint. Once the team and product owner establish the scope of the Sprint as described by the product backlog items no more items can be added to the Sprint Backlog. The product backlog items identified for delivery and tasks if applicable, makes up the Sprint Backlog. The team may identify specific tasks necessary to make that happen if that is one of their practices. In the Second Part of Sprint Planning, the team determines how they will successfully deliver the identified product backlog items as part of the potentially shippable product increment. In the first part, the product owner and the rest of the team agree on which product backlog items will be included in the Sprint. Sprint Planning typically occurs in two parts. The end result of Sprint Planning is the Sprint Backlog. Start date and end date of Sprint are fixedĪ team starts out a Sprint with a discussion to determine which items from the product backlog they will work on during the Sprint.
The team constantly investigates how things are going and revises those items that do not seem to make sense. These inspection points include the Daily Scrum meeting and the Sprint Review Meeting. Teams surface issues within the organization, often ones that have been there for a long time, that get in the way of the team’s success.įrequent inspection points built into the framework to allow the team an opportunity to reflect on how the process is working. The team must work in an environment where everyone is aware of what issues other team members are running into. The following principles underpin the empirical nature of scrum: Team members respect each other to be capable and independent. Team members and stakeholders are open about all the work and the challenges the team encounters. Team members do the right thing and work on tough problems.Ĭoncentrate on the work identified for the sprint and the goals of the team. Team members personally commit to achieving team goals Teams following scrum are expected to learn and explore the following values: Scrum is best suited in the case where a cross functional team is working in a product development setting where there is a non trivial amount of work that lends itself to being split into more than one 2 – 4 week iteration. Scrum is structured in a way that allows teams to incorporate practices from other frameworks where they make sense for the team’s context. That is, when the framework is used properly. Scrum is empirical in that it provides a means for teams to establish a hypothesis of how they think something works, try it out, reflect on the experience, and make the appropriate adjustments. Scrum is a process framework used to manage product development and other knowledge work.