Definition of scrum
Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
Scrum is;
- lightweight;
- simple to understand;
- difficult to master;
Four events for inspection and adaptation
- sprint planning;
- daily scrum;
- sprint review;
- sprint retrospective;
Scrum team members
- product owner;
- development team;
- scrum master;
Product owner
Is responsible for maximizing the value of the product and the work of the development team. -> managing product backlog
Product backlog management
- clearly expressing product backlog items;
- ordering the items in the product backlog to best goals and missions;
- optimizing the value of the work the development team performs;
- ensuring that the product backlog is visible, transparent, and clear to all, and shows what the scrum team will work on next, and,
- ensuring the development team understands items in the backlog to the level needed.
Development team
Consists of professionals who do the work of delivering a potentially releasable increment of ‘done’ product at the end of each sprint. Only members of the development team create the increment.
Scrum master
Is responsible for ensuring scrum is understood and enacted. Is a servant-leader for the scrum team.
Scrum master to Product Owner
- finding techniques for effective Product Backlog management;
- Helping the scrum team understand the need for clear and concise Product Backlog Management.
- Understanding product planning in an empirical environment
- ensuring the product owner knows how to arrange the product backlog to maximize value.
- understanding and practicing agility.
- facilitating scrum events as requested or needed.
Scrum master to Development team
Scrum master facilitates development team:
- coaching development team in self-organization and cross-functionality.
- Helping development team to create high-value products.
- removing impediments to development team’s progress.
- facilitating scrum events as requested or needed.
- coaching development team in organizational environments in which scrum is not yet fully adopted and understood.
Scrum master to organization
Scrum master serves organization:
- Leading and coaching the organization in its scrum adoption;
- planning scrum implementations within organization;
- helping employees and stakeholders understand and enact scrum and empirical product development.
- causing change that increases the productivity of the scrum teams.
- working with other scrum masters to increase the effectiveness of the application of scrum in the organization.
The Sprint
Is a time-box of one month, or less during which a ‘done’, useable, and potentially releasable product increment is created.
During the sprint;
- no changes are made that would endanger the sprint goal;
- quality goals do not decrease;
- scope may be clarified and re-negotiated between the product owner and development team as more is learned.
Sprint planning
Is time-boxed to a maximum of eight hours for a one-month sprint. Scrum master ensures that event take place.
Answer sprint planning;
- what can be delivered in the increment resulting from the upcoming sprint?
- how will the work needed to deliver the increment be achieved?
Sprint goal
Is an objective set for the sprint that can be met through the implementation of product backlog. It’s created during sprint planning meeting.
Daily scrum
Is a 15 minute time-boxed event of the development team to synchronize activities and create a plan for the next 24 hours. Inspecting work since last daily scrum and forecast work that could be done for next one. Team members explain;
- what did I do yesterday that helped the development team meet the sprint goal?
- what will I do today to help the development team meet the sprint goal?
- do I see any impediment that prevents me or the development team from meeting the sprint goal?
Sprint review
Is held at the end of a sprint to inspect the Increment and adapt product backlog if needed.
It’s a four-hour time-boxed meeting for one-month sprint.
Sprint retrospective
Is an opportunity for the scrum team to inspect itself and create a plan for improvements to be enacted during the next sprint.
It’s a three-hour time-boxed meeting for one-month sprints.
Purpose of the retrospective is;
- inspect how last sprint went with regards to people, relationships, processes and tools;
- identify and order the major items that went well and potential improvements;
- create a plan for implementing improvements to the way the Scrum Team does its work;
Product backlog
Is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product.
It’s a living artifact.
Sprint backlog
Is the set of product backlog items selected for the sprint, plus a plan for delivering the product increment and realizing the sprint goal.
Increment
Is the sum of all the backlog items completed during a Sprint and the value of the increments of all previous sprints.
at the end of the sprint the new increment must be “done” which means it must be usable condition and meet the scrum team’s definition of “done”.
Definition of “done”
Definition varies significantly per scrum team. Members must have a shared understanding of what it means for work to be completed, to ensure transparency.
