Scrum in a Nutshell

Scrum framework

Scrum was founded by Ken Shwabber and Jeff Sutherland (co-founders of agile manifesto) as a framework to develop and deliver a working software using a light weight and collaborative methods via a continuous delivery stream called sprint. Incremental delivery approach in Scrum reduces the project risks as scrum team members work in a highly collaborative manner to deliver a set of predefined backlog in each sprint.

Transparency, inspection and adoptability

Scrum teams must follow a common and transparent standard to ensure all cross functional team members have the same understanding, inspect their deliverables frequently to adjust variation to an agreed standard and adopt and adjust their working practices accordingly.

Scrum events

Scrum teams typically repeat four events continually, sprint planning, daily scrum, sprint review and sprint retrospective.

Sprint planning

In the Sprint planning, scrum teams decide which set of backlog items prioritised by the product owner can be delivered in one sprint. What could be delivered in a sprint, depends on the team capacity based on the size of the team and the speed of the team (velocity) established in previous sprints.

Product backlog and Product owner

Product backlog is a collection of discrete functions in forms of user stories prioritised by the product owner. Product owner is a representative from the business who collates the requested business features and prioritises the product backlog in line with the group priority.

While the product owner prioritise “what” needs to be delivered, scrum team members decide on “how” the prioritised  backlog should be delivered.

Daily Scrum

In daily stand-ups, scrum team members reports on what they have achieved, what they plan to do and flag any blockers or impediments.

Sprint review

Scrum teams inspect the quality of artefacts developed during a sprint in the sprint planning to ensure sprint goals are on track.

Sprint retrospective

Scrum team members reflect on their deliverables in a retrospective meeting to adjust any deviation from standard, and identify actions for continuous improvements.

Definition of done.

Everyone in a scrum team must understand and agree upon what “Done” means. Definition of “Done” should be well defined to cover all aspects of a finished artefacts to cover when a work is completed at the end of each sprint for the product increment.