Scrum Flashcards
Provide an overview of Scrum
• Created by Schwaber & Sutherland 1995
• Framework for developing/sustaining complex products
- Collection of roles, events, artfacts and rules
• A way to assess efficency of practices to promote improvement
• Created as an alternative to Waterfall
• NOT a project management lifecycle
• CAN be used as BAU alone
Provide an overview of the Scrum Team
• Self-organising & empowered
• Cross-functional
• Flexible, creative & productive
• Roles:
- Product Owner
- Development Team
- Scrum Master
• 3-9 People focused on 1 objective at a time, the product goal
•Responsible for all Product related activities from stakeholder collaboration, verification, maintenance, operation, experimentation & R&D
• Accountable for creating a valuable, useful increment every sprint
What should ideally happen if a Scrum team is too large?
Split into multiple cohesive Scrum teams, each focused on the same product (Product goal, Backlog & Product Owner)
Outline the Scrum Team role of “Developers”
• Build the product
• Committed to creating any aspect of a useful increment each sprint
• Broad range of skills varying with the work
• Accountable for:
- Creating a plan for the sprint
- Creating a product backlog
- Instilling quality by adhering to “Definition of Done”
- Adapting their plan daily toward the sprint goal
- Holding each other accountable as professionals
Outline the Scrum Team role of “Product Owner”
• Accountable for maximising product value
• Liaise with customer to get high level requirements/ EPICS
• understand customer vision
• 1 person
• Accountable for effective product backlog management (can delegate):
- Developing/communicating Product Goal
- Creating/communicating Product Backlog items
- Ordering Product Backlog items
- Ensuring transparency, visibility & understanding of Product Backlog
• Decisions visible via Product Backlog, inspectable Increment at sprint review
In a Scrum Team, how could people change the Product Backlog?
Convince the Product Owner
Outline the Scrum Team role of “Scrum Master”
• Accountable for establishing Scrum as defined in the Scrum Guide
• Aid in Scrum understanding and practice in the team & organisation
• Accountable for the team’s effectiveness
• Serves the Scrum Team & organisation
How does the Scrum Master serve the Scrum Team?
Serves the Scrum Team:
- Coaching self management & cross-functionality
- Help create high value increments that adhere to a Definition of Done
- Removal of impediments
- Ensure all Scrum events occur being positive, productive and kept in the timebox
How does the Scrum Master serve the Product Owner?
Serves the Product Owner:
- Help find techniques for effective Product Goal Definition & Product Backlog Management
- “ team understand need for clear/concise Product Backlog items
- “ establish empirical Product planning for a complex environment
- Facilitating stakeholder collaboration
How does the Scrum Master serve the organisation?
• Leading, training & coaching in Scrum adoption
• Planning & advising Scrum implementations
• Helping employees/stakeholders understand and enact an empirical approach to complex work
• Remove barriers between stakeholders & Scrum teams
What are the characteristics of Scrum Events?
• Prescribed to create regularity
• Each has a maximum duration
• Sprint at the heart of this concept
• Forces transparency
• Provide opportunities to inspect & Adapt
- Fail Fast, Learn Quickly
- Iterative development
What comprises the Product Backlog?
Product Owner translates from the customer:
- EPICS
- High Value Requirements
- EPICS/HVRs broken down into user stories
Summarise the Scrum process
• Product Owner translates Customer EPICS into a Product Backlog list
• Develoment Team breaks down one EPIC at a time after each sprint (in case of EPIC change over time)
- A plan for each sprint made during a Sprint Planning Meeting
- The sprints are compiled in a Sprint Backlog
• Develoment Team undertake Sprint with assistance from Scrum Master/Product Owner
- Daily Scrum undertaken consistently every day
• A sprint review & retrospective after each sprint
What is a sprint roadmap?
The chart of required sprints towards the final product
Outline the Daily Scrum event
• To inspect progress toward sprint goal & adapt sprint backlog
• Held daily at consistent time & place
• 15min event for developers
• If Product Owner/Scrum Master are working on sprint backlog items - they participate as Developers
• Structure & techniques chosen by developers creating focus & improves
self-management.
• + communication, identity impediments, + quick decision making, eliminate need for further meetings
