Please enable JavaScript.
Coggle requires JavaScript to display documents.
SCRUM - Coggle Diagram
SCRUM
VALUES
- Commitment
- Focus
- Openness
- Respect
- Courage
COMMITMENT
- People personally commit to achieving the goals of SCRUM TEAM
FOCUS
- Everyone focuses on work towards the sprint goal and goals of SCRUM TEAM
OPENNESS
- The SCRUM TEAM and its stakeholders agrees to be open about work and the challenges of performing the work
RESPECT
- SCRUM TEAM members respect each other to be capable, effective and independent people
COURAGE
- SCRUM TEAM has the courage to work on difficult tasks and do things right
EVENTS
- Each event is time-boxed and has pre-defined maximum duration
- These events enable project transparence for all who are involved into the project
THE SPRINT
- Here idea is turned into value
- Usable, potentially releasable increment is created during each sprint
- Time- boxed, 1 month max
- All Scrum Events are held within Sprint
- During Sprint no changes are made that would endanger sprint goal
- Quality does not decrease
- The Product backlog is refined as needed
- Scope may be clarified and renegotiated with the Product Owner as more is learned
SPRINT PLANNING
- Initiates the sprint by laying down the work to be performed during Sprint
- Performed by the entire Scrum Team
- Timeboxed to 8 hours max for 1-month Sprint
- Addresses the following topics:
a) Topic One: Why this Sprint valuable
b) Topic two: What can be Done during the sprint?
c) Topic three: How will the chosen work get done?
DAILY SCRUM
- Optimizes team collaboration by inspecting work since last Daily Scrum and forecasting upcoming Sprint work
- Daily time-boxed event 15 min max
- Plans for 24-h period
- Answers the following questions:
a) What has been done since last Daily Scrum?
b) What are the plans for today?
c) Are there any circumstances that affect the Sprint Goal?
- Same time, same place
SPRINT REVIEW
- Time-boxed to a max. of 4 hours for 1-month Sprint
- The purpose is to inspect the outcome of the Sprint and determine future adaptations
- Scrum Team reviews what was accomplished in the Sprint and what has changed in their environment
- Product Backlog is revised. Items for the next Sprint are selected
- Scrum Team and Stakeholders collaborate
SPRINT RETROSPECTIVE
- Timeboxed to a max. 3 hours for a 1-month Sprint
- The purpose is to plan ways to increase quality and effectiveness
- The Scrum Team Inspects how Sprint went in regard to people, relations, processes, tools and the Definition of Done
- Inspects what went well, what problems were encountered, what problems weren't solved and potential improvements
SCRUM TEAM
- consists of 10 or less people
- self-organizing and cross-functional
- designed to optimise flexibility and productivity
- delivers product iteratively and incrementally
- maximizes opportunities for a feedback loop
DEVELOPERS TEAM - ACCOUNTABLE FOR CREATING RELEASABLE INCREMENTS
- Up to 9 people
- A group of people in charge of creating a potentially shippable increment at the end of each sprint
- Collectively present at each sprint planning
- Determine the complexity of each task (scrum poker)
- Each increment should respond to Definitionof Done requirements
PRODUCT OWNER - ACCOUNTABLE FOR MAXIMIZING THE VALUE OF WORK
- Accountable for maximising the product value resulting from the work of SCRUM TEAM
- Creates and maintains product backlog
- Adds details to the backlog items - candidates for next sprint
- Responsible for anything product-related from the customer side, "what" - person
- Collaborates with stakeholders in order to optimise work and achieve best result for each incremment
- Makes decision on releasing
SCRUM MASTER - ACCOUNTABLE FOR UNDERSTANDING AND APPLICATION OF SCRUM AND FOR THE TEAM BEING PRODUCTIVE
- Servant-leader of a SCRUM TEAM
- Trains team to follow SCRUM procedures
- Maintains SCRUM ceremonies throughout the process
- Facilitates collaboration and meetings
- Enables self-organization
- Encourages transparency
ARTIFACTS
- SCRUM artifacts represent work or value. They are designed to maximise the transparency of key information. Thus, everyone inspecting them has the same basis for adaptation.
PRODUCT BACKLOG
- Ordered list of everything need to be done to achieve product goal
- Single source of requirements
- The product owner is responsible for it including its content, availability and ordering
- It is never complete
- It exist while the product exist
It changes to identify the product needs
SPRINT BACKLOG
- Set of Product Backlog items selected for the Sprint
- A plan for delivering the product increment
- Realizing the Sprint Goal
- Highly-visible, real-time picture of work that the Development Team plans to accomplish during Sprint
INCREMENT
- Sum of all the Product Backlog items completed during the Sprint and the value of all the Increments of previous Sprints
- Each new increment has to be potentially shippable and meet the SCRUM teams "Definition of Done"
SCRUM THEORYSCRUM is founded on:
- Empiricism. Knowledge comes from experience, decision-making is based on what is known
- Lean thinking. Reduce waste, focus on essentials
TRANSPARENCY
- Significant aspects of process must be visible to those responsible for the outcome. Low transparency can diminish product value and increase risk
INSPECTION
- SCRUM users must frequently inspect SCRUM artifacts and progress towards Sprint foal to detect undesirable variances
ADAPTATION
- If inspector detects if one or several aspects process deviate outside acceptable limits, and the resulting product will be unacceptable, the process or the material being processed must be adapted
DEFINITION
- It is a lightweight framework that helps develop, deliver and sustain complex products.
- It helps maintain work structure that is, in its turn, helps the team to stay in focus whatever the ongoing or new task it is