9910 Research Drive, Irvine, California 92618, United States
Why Scrum?
- Ability to manage changing priorities
- Project visibility
- Business / IT alignment
- Team morale
- Delivery speed
- Time to market
- Increased team productivity
- Project predictability
- Project risk reduction
- Software quality
What is Scrum?
Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
There are 3 roles, 5 events and 3 artifacts in the Scrum Framework.
Scrum Roles
Product Owner
Development Team
Product Owner
The Product Owner is responsible for maximizing value and defines the product vision and goals. They manage the Product Backlog, own Backlog Refinement, accept work as done, and are the customer proxy to the development team.
Scrum Master
Development Team
Product Owner
The Scrum Master is a servant leader to the Product Owner, Development Team and the organization. They promote and support the Scrum practice through coaching, impediment removal and the facilitation of Scrum events.
Development Team
Development Team
Development Team
The Development Team is a self-organizing, cross-functional team. There are no titles or sub-teams on a development team. The team is able to determine how work will be executed.
Scrum Events
Sprint
Sprint Planning
Sprint Planning
The Sprint is a time box of no more than 1 month in which potentially releasable product is developed. The most common time box is 2 weeks.
Sprint Planning
Sprint Planning
Sprint Planning
Sprint Planning occurs at the start of the Sprint and has a maximum
time box of 8 hours for a 1 month Sprint. The planning session is facilitated by the Scrum Master and results in an actionable plan and team commitment.
Daily Standup
Sprint Planning
Sprint Review (Demo)
The Daily Standup is held at the same location, the same time, every working day. It has a 15 minute maximum time box and is a meeting for the development team.
Sprint Review (Demo)
Sprint Review (Demo)
Sprint Review (Demo)
Occurs at the close of the Sprint
4 hours time box for 1 monthsprint
Also known as Demo
Inspect Potentially Releasable Increment
Adapt the Product Backlog
Customer feedback
Sprint Retrospective
Sprint Review (Demo)
Sprint Retrospective
Occurs after Sprint Review
3 hourtime box for 1 month sprint
What went well in the Sprint?
What could be improved?
What will we commit to improve the next Sprint “Kaizen”?
Scrum Artifacts
Product Backlog
Product Increment
Product Backlog
The Product Backlog contains all work necessary to develop a product. It is constantly evolving as work progresses and the team understands more about the product. Scope is kept high level and is decomposed using just in time techniques.
Sprint Backlog
Product Increment
Product Backlog
The Sprint Backlog belongs to the Development Team and contains an improvement opportunity, or Kaizen, and all work necessary to complete the Sprint Goal.
Product Increment
Product Increment
Product Increment
The Product Increment is a sum of all Product Backlog Items that have been completed and should be in a usable condition.