Scrum Training Course

AstroTech.ioMATT HARASYMCZUK / Professional SCRUM Master I
AGILE Bootcamp
MATT HARASYMCZUK

SDLC - Waterfall

Software Development Life Cycle
A.K.A. Waterfall
• Client satisfaction
• Delays
• Delivering product suited for requirements

Software Development Life Cycle
A.K.A. Waterfall
- Problem: Scope Changes
• Problem: Requirement Optimizations
• Problem: No transparency
• But it’s not always black and white…

Manifesto for agile software development
• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

Manifesto for agile software development

Agile is Dead - Pragmatic Dave Thomas
https://www.youtube.com/watch?v=a-BOSpxYJ9M

Business and IT working together

What is Agile?
• Agile, Lean, Kanban, Scrum, XP?!

What is Scrum?
• Scrum rules and foundations
• Timeboxes
• Use Cases and Scrum
• Scrum and U.S. Department of Defence

Scrum

Pillars of Scrum

Scrum Pilars - Transparency
• How do you benefit from transparency?
• Product Demos
• Transparent Backlog

Scrum Pilats - Inspection
• Frequent check-ups
• At least once a month
• Once a week is a desired practise

Scrum Pillars – Adaptation
• Continuous Improvement
• Kaizen
• Retrospectives
• Empirical process, based on experience

Scrum in a nutshell
• Make a TODO list
• The higher place on a list, the more important
• Make fixed length iterations
• Repeat

The Scrum
• Easy to understand, hard to implement
• Small, 6 plus minus 3 people teams
• Cross functional multidisciplinary teams

Scrum Roles

Where is management?

Scrum Roles
• Team Member
• Scrum Master
• Product Owner
• Development team vs Stakeholders
• Scrum Master vs Scrum process

Scrum Master
• Servant Leader
• Facilitator
• Responsible for sprint backlog
• Prevents scope change
• Remove impediments

Scrum Master
• Sprint Termination
• How to choose Scrum Master
• Make sure everyone is present

Types of Scrum Masters
• Team Member and Scrum Master
• Full Time Scrum Master
• Shared scrum master between teams

Product Owner
• Owns product (big picture)
• Represents client and stakeholders
• Understanding client needs
• Creates and prioritize backlog
• Product Owner Checklist
https://scrumwell.files.wordpress.com/2013/09/product-
owner-checklist-november-2013.pdf

Product Owner
• Represents stakeholder interests
• Decisional (has power to make decisions)
• Disposable (available for the owner's use as
required)
• Accepts or rejects increment

Product Owner
• External
• Internal

Stakeholders

Team Member
• Determines with Product Owner sprint scope
• Completes sprint tasks according with
Definition of Done
• Abides timeboxes and scope

Team Member
• Collective Code Ownership
• Self regulating team
• Multidisciplinary team
• Has all knowledge to deliver sprint scope

Team
• Remove grey zone
• Capacity
• Velocity (7 sprints)
• Members self assign tasks (why?)
• Off-site once a quarter
• Team exhaustion (1 free sprint every quarter)

Stakeholder
- What is stakeholder role in the process?
- How to work with Product Owner?
- Demo and Reviews
- Backlog refinement

Artifacts
• Product Backlog
• Sprint Backlog
• Product Increment
• Sprint Burndown Chart
• Release Burndown Chart
• Product Burndown Chart

Artifacts
• Velocity
• Capacity
• Retrospective summary
• Team constitution

Artifacts
• Control Chart
• Cumulative Flow Chart
• Burnup Chart
• Velocity Chart
• Version Report
• Epic Report
• Release Burndown

Artifacts
• Definition of Done
• Acceptance Criteria
• AC vs DoD
• Sprint Goal
• Roadmap
• (Custom field in Jira “As a”, “I can”, “so that”,
“acceptance criteria”)

Sprint Goal
• Potentially releaseable sprint objective
• Sprint Goal Roadmap
• Portfolio

Backlog
• Decomposition
• Prioritization: MoSCoW
• Epic -> Story -> Sub-Task
• Story Points / Business Value / Time Estimate
• Adding issues by members
• Reprioritizing issues
• Global backlog

Sprint Backlog
• Tasks
• Assignment
• Prioritization
• Impediments
• Taskboard (Kanban board)
• Adding issues during sprint
• Adding not estimated issues - spikes
• Re-estimating during the sprints
• Adding issues, you know you can deliver

Definition of Done
• Responsible: Scrum Master + Team
• Why: common understanding what is done
• What tests are required?
• Do code need to be packaged and prepared
for release?
• What quality goals has to be achieved?

Definition of Done
• Potentially releasable increment
• Product Owner decide on release
• Release vs Deployment

Task estimation
• Estimation scale
• Fibonacci
• Power of 2
• T-shirt scale - S,M,L
• Planning Poker
• SML columns with cards (and dots)
• #NoEstimates

Team is responsible for delivery
• Team member roles
• Communication
• Iteration increment verification

Sprint – increment unit
• What is the best length?
• Priority strategy during sprint?
• Sprint increments
• Abnormal sprint termination
• Closing Sprint - Demo

Scrum meetings
• What kind of meetings are there in Scrum?
• Product artifacts
• Timeboxes

PLAN
MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY
PLANNING
1h
DAILY 15m DAILY 15m DAILY 15m DAILY 15m DAILY 15m
REFINEMENT
1h
REVIEW
1h
RETROSPECTIVE
1h

Feedforward NOT Feedback
PLANNING
1h
REFINEMENT
1h
REVIEW
1h
RETROSPECTIVE
1h

DO
PLANNING
1h
REFINEMENT
1h
REVIEW
1h
RETROSPECTIVE
1h

PREPARE
PLANNING
1h
REFINEMENT
2h
REVIEW
1h
RETROSPECTIVE
1h

CHECK
PLANNING
1h
REFINEMENT
2h
REVIEW
1h
RETROSPECTIVE
1h

SHOWTIME
PLANNING
1h
REFINEMENT
2h
REVIEW
1h
RETROSPECTIVE
1h

ACT
PLANNING
1h
REFINEMENT
2h
REVIEW
1h
RETROSPECTIVE
1h

ONE week iterations!
PLANNING
1h DAILY 15m DAILY 15m DAILY 15m DAILY 15m
REFINEMENT
1h
REVIEW
1h
RETROSPECTIVE
1h

REVIEW
1h DAILY 15m DAILY 15m DAILY 15m DAILY 15m
REFINEMENT
1h
PLANNING
1h
RETROSPECTIVE
1h

REVIEW
1h
RETROSPECTIVE
1h
REFINEMENT
1h
PLANNING
1h

CONTINUOUS Backlog Refinement
REVIEW
15 min
DAILY 5 min DAILY 5 min DAILY 5 min DAILY 5 min
RETROSPECTIVE
30 min
PLANNING
15 min

Metrics

Andon - Process Dashboard

Sprint Goal

PORTFOLIO

Release and Value Stream => Roadmap

Documentation -> Backlog

Value - Epic mapping

Backlog Decomposition and Acceptance Criteria

Scrum/Kanban Boards

Daily

SCRUM of Scrums (full scale)
P
O
S
M

DEPARTMENT Oriented Organization
Business QA DEV UX Infra
Project A
Project B
Project C

PROJECT Oriented Structure
Project A
Project B
Project C

PROJECT Oriented Organization
Project A
Project B
Project C

Planning
• Sprint tasks decomposition and planning
• Story requirements and acceptance criteria
• Review of the sprint scope
• Task estimation

User Stories
• How to create User Stories
• Epic / User Story / Sub-Task
• As a ...., I want .... So that ....

User Stories
• User Stories vs Tasks
• User Stories vs Epics
• User Stories vs Sub-Tasks
• User Stories vs Use Cases
• Epics should be deliverable

User Stories
• All team members can write user stories
• Where to put User Stories?
• User Stories can be added to project through the
all lifecycle
• Product Owner is responsible for priorities
• Creating user stories is less important than a
discussion about them

User Stories most common mistakes
• User Stories as a cards
• No clear Acceptance Criteria
• Product Owner bottleneck

User Stories mistakes
• Abusing “as a…” template
• Too much technical information
• Not enough discussion

How to add User Stories?
• Where to put them in the Backlog?
• How to inform Product Owner?
• Who can add User Stories?
• How to filter in Jira newly added User Stories?

Strategies for prioritization
• Quick Win
• Hard-first
• Hybrid: Quick Win -> Hard -> Quick Win
• Sprint Goal delivery first, then other
• MoSCoW
• Business Value
• MVP

How to define sprint goal
• Define before from roadmap
• Define from majority of issues

Strategies for prioritization
- Sprint Log
- Backlog

Daily
• Sprint Goal oriented
• Three questions
• Feedforward not Feedback
• Problem: Daily confessions…
• JIRA Filter + Flagged

Retrospectives
• What are retrospectives?
• How to conduct retrospective?
• How often?
• Retrospectives results
• Retrospective action items
• Alternative retrospectives artifacts
• Team constitution
• Experiments

Scaling Scrum
• How to Scale Scrum
• Scaled Scrum vs Effectivity
• Product Structure
(https://www.youtube.com/watch?v=X2xuROuGBUk)
• LeSS (https://less.works/)
• SAFe (http://www.scaledagileframework.com/)

Agile Portfolio
• Milestone and Versions
• Epics Kanban
• Road Map
• Timeline
• Release Stream
• Value Stream

Scrum and Kanban
• Product Development
• Product Maintenance
• Graveyard shift (one person sacrifice for the others)
• FIFO with Priority Queuing
• Knowledge exchange
• Collective Ownership
• Domain competence

Delivering Tasks in Scrum
• Unfinished sprints
• What to do with unfinished tasks?
• How to prevent having unfinished tasks?

Scrum and Risk Management
• Scrum Master and Risk Management on a
team level
• Technological Debt

Electronic Tools
• Atlassian JIRA Software
• ThoughtWorks Mingle
• http://www.mountaingoatsoftware.com
• http://www.planningpoker.com
• Kunagi
• Redmine
• Asana (Kanban), Trello (Kanban)

Scrum Training Course

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Scrum Training Course

Similaire à Scrum Training Course (20)

Plus de Astro Tech

Plus de Astro Tech (8)

Dernier

Dernier (20)

Scrum Training Course