After getting scrum.org the PSM I I wanted to capture the relevant content.
The complete guido can be downloaded here: scrumguides.org
1. What is Scrum?
Scrum is a framework for developing and sustaining complex products. A framework in which complex adaptive problems can be addressed. It is lightweight, simple to understand and yet difficult to master. To simplify, Scrum is not a process or a technique - it is a framework within which you can use different processes and techniques. It has roles, events, artefacts and rules that bind them together. Each component has a specific purpose. Scrum takes an iterative and incremental approach - optimizing predictability and control risk.
Scrum has its foundation based on the Empirical Process Theory - where knowledge comes from experience and decisions are made based on what is known. There are three pillars that uphold every implementation of empirical process control. - Transparency - Inspection - Adaptation
1.1. Scrum Values
The five core values that are reflective in the work of a Scrum Team.
- People personally commit to achieving the goal of the Scrum team.
- Scrum member have the Courage to do the right thing.
- Everyone’s focus is on the sprint and Scrum team goals.
- Everyone agrees to be Open about all the work and challenges.
- Scrum team members Respect each other of being capable and independent.
2. Scrum Team
A self-organised and cross functional team - designed to optimize flexibility, creativity and productivity.
3. Scrum Events
All events in Scrum are time boxed. Sprint duration cannot change once it's started. However, it can be cancelled before the time box is over. Only a Product Owner can cancel a Sprint if the organisation changes direction or the market or the technology conditions change. Events enable transparency and create an opportunity to inspect and adapt.
The Sprint is the heart of Scrum, a time box of one month or less during which a DONE, usable, and potential releasable product increment is created.
|Sprint Planning||08 Hours||
|Daily Stand-ups||15 Minutes||
||The Development team|
|Sprint Review||04 Hours||
||The Scrum Team and the Stakeholders|
|Sprint Retrospective||03 Hours||
||The Scrum Team|
*Time box mentioned above is for one month sprint. For short sprint, it’s usually shorter. Scrum activities - Backlog refining or grooming.
This is an on-going activity and should not take more than 10 % of the Development Team’s time where product Backlogs are groomed or refined. The Product Owner is responsible for prioritizing the product Backlog items and the Development Team is responsible for estimating them.
4. Scrum Artefacts
Scrum's artefacts reflect the three pillars of the Empirical Theory Process in the work or value to increase transparency and opportunities for inspection and an enhanced scope for adaptation.
Increment 1 = Sprint 1 Increment 2 = Sprint 1 + Sprint 2
Increment 3 = Sprint 1 + Sprint 2 + Sprint 3.
|Monitoring progress towards a Goal (delivering the product)||
|Monitoring Sprint Progress||
5. Progress Tracking Tools
Burn-down charts: Burn-down chart shows the progress the Development Team is making and is a powerful tool for visualising progress and work remaining. Burn-down charts may be used for financial tracking, resource tracking etc. In respect to a sprint, a burn-down chart is represented as -
- vertical Axis - remaining work (total estimated hours) for the sprint or product Backlog
- horizontal Axis - time, in days or sprints
A burn-down chart enables everyone to view the status of a sprint at any time.
6. Estimation Techniques
There are number of estimation techniques used in Agile. Most widely used in planning is the poker technique to estimate items. Participants use cards to estimate an item. This exercise is repeated in iterations until everyone’s estimates are unanimous. Units used are hours, days or story points. Other techniques in practice are:
- The Bucket System
- Dot voting
- T-shirt sizes
- Affinity mapping and more
A product Backlog item or an increment that is releasable is called DONE. Everyone in the Scrum team should have common understanding of DONE.
DONE should include all the development practices before the item is released into production.
- Average of items done per Sprint to deliver a product.
e.g. It took 5 sprints to deliver a product.
Sprint1 - 10 Units
Sprint2 - 12 Units
Sprint3 - 9 Units
Sprint4 - 11 Units
Sprint5 - 13 Units
Velocity of the team in this example is 11 ((10 + 12 + 9 + 11 + 13)/5) units per Sprint.
- Time box
- Fixed time-period, it is an agreed previous agreed duration which the team has been consistently delivering a task or completing a goal.
- Sprint Goal
- Description of what the Development Team agrees to achieve in a sprint.
What I also found quite interesting are the number of people that took the certifications: https://www.scrum.org/professional-scrum-certifications/count