Date post: | 17-Jan-2015 |
Category: |
Education |
Upload: | agile-vietnam |
View: | 1,126 times |
Download: | 2 times |
Improving the Profession of So2ware Development © 1993-‐2011 Scrum.org, All Rights Reserved
Ken Schwaber
Agile Vietnam May 28, 2012
© 1993-‐2011 Scrum.org, All Rights Reserved
2
Scrum
Professional Scrum Master
A man who carries a cat by the tail learns something he can learn in no other way.
-‐ Mark Twain
© 1993-‐2011 Scrum.org, All Rights Reserved
3
3 Types of Content in Scrum
Roles • Product
Owner • Development
Team • Scrum Master
Artifacts • Increment • Product
Backlog • Sprint
Backlog
Events • Sprint • Sprint
Planning • Daily Scrum • Sprint Review • Retrospective
© 1993-‐2011 Scrum.org, All Rights Reserved
4
Scrum in acIon
© 1993-‐2011 Scrum.org, All Rights Reserved
5
• Something required in soLware. • What, not how. • Not implemenIng a database or a infrastructure.
• Describes something a customer can directly experience.
• May be contained in a Sprint, Release, Roadmap, Goal, Strategy.
What Is A Requirement?
© 1993-‐2011 Scrum.org, All Rights Reserved
6
Product Backlog Product Backlog
Cost: 13
Cost: 20
Cost: 1
Cost: 3
Cost: 5
Cost: 8
Cost: 3 A
Cost: 20
Cost: 13
Cost: 100
Cost: 13
• Inventory of things to be done
• Desirements • Ordered based on • Transparent • Minimal but
sufficient • Managed by
Product Owner
© 1993-‐2011 Scrum.org, All Rights Reserved
7
Views or OrientaIon into Product Backlog
Product Backlog
Cost: 13
Cost: 20
Cost: 1
Cost: 3
Cost: 5
Cost: 8
Cost: 3 A
Cost: 20
Cost: 13
Cost: 100
Cost: 13
Business System • Work flow • Process • AcIvity • FuncIon
System • Architecture • Layer • Subsystem,
module, components
Business Process • Workflow • AcIvity • Task
Persona
New capability
© 1993-‐2011 Scrum.org, All Rights Reserved
8
Major League Baseball (MLB) Vision
Be the in the heart of sports fans worldwide.
• Expand worldwide • OpImize revenues • Reach down and up in age
• Be a role model
Vision Strategies
Vision Strategy TacIcs Release
© 1993-‐2011 Scrum.org, All Rights Reserved
9
MLB Strategies
• OpImize Revenues • Increase adverIsing revenues
• Increase adendance • Increase number of leagues and teams worldwide
• Capture more of “aLer box office purchase” revenues
Strategy TacIcs
Vision Strategy TacIcs Release
© 1993-‐2011 Scrum.org, All Rights Reserved
10
MLB TacIcal Roadmap
• Capture more of “aLer box office purchase” revenues
• Ensure all aLer box office revenues are legally MLB’s
• Put up facility for trading these Ickets
• Enforce the law • Increase funcIonality to increase revenue capture
TacIc Roadmap
Vision Strategy TacIcs Release
© 1993-‐2011 Scrum.org, All Rights Reserved
11
Roadmap Item – MLB Tickets (MLBTix)
• Put up facility for trading these Ickets
• Increase funcIonality to increase revenue capture
• Establish fixed-‐price Icket exchange prior to opening day
• Establish aucIoning by mid-‐season
• Establish social media capabiliIes
MLBTix The Plan
Vision Strategy TacIcs Release
© 1993-‐2011 Scrum.org, All Rights Reserved
12
Requirements oLen have three components
Developed by Development Team
• The “consumer” of the requirement Consumer
• What the user will consume Requirement
• “…so that…” spells out boundaries of requirement and acceptance tests . How to know if a requirement is saIsfied.
Acceptance Criteria
© 1993-‐2011 Scrum.org, All Rights Reserved
13
Sprint 1 Forecast
© 1993-‐2011 Scrum.org, All Rights Reserved
14
Sprint 2 Forecast
© 1993-‐2011 Scrum.org, All Rights Reserved
15
Acceptance Tests
© 1993-‐2011 Scrum.org, All Rights Reserved
16
Acceptance Tests
© 1993-‐2011 Scrum.org, All Rights Reserved
17
PBI Linked to System and Business Processes
BP1
BP2
BP3
BP5
BP4
BP6
BP7
Capability Packages, Use Scenarios & Stories (Backlog
Items)
CP1
US1
US2
STORY1
STORY2
STORY3
STORY6
STORY5
STORY4
CCA1
CCA2
CCA3
CCA5
CCA4
CCA6
CCA7
CCA8
Business and Admin Process Hierarchies
(Feature Groups)
Common Architectural Feature
(Feature Groups)
US3
STORY7
STORY6
STORY5
STORY4
CP2
© 1993-‐2011 Scrum.org, All Rights Reserved
18
Sprint Planning MeeIng Flow
Dev. Team Capacity
Product Backlog
Analyze, evaluate and select Product Backlog for Sprint
Establish Goal and forecast work
Figure out how to do work; decompose it into
actionable work plan
Sprint Backlog
DefiniIon Of Done
Standards, ConvenIons Guidelines
© 1993-‐2011 Scrum.org, All Rights Reserved
19
• How do you know how much Product Backlog to select in the Sprint Planning meeIng?
• If the definiIon of “done” isn’t in place, how would you know how much to select?
• What is the value of knowing the definiIon of “done” when you are creaIng the product backlog?
SelecIng Product Backlog 5 MINS
© 1993-‐2011 Scrum.org, All Rights Reserved
20
Form Sprint Backlog
Product Backlog
Cost: 13
Cost: 20
Cost: 1
Cost: 3
Cost: 5
Cost: 8
Cost: 3 A
Cost: 20
Cost: 13
Cost: 100
Cost: 13
Sprint Backlog
Cost: 20
Cost: 20
Cost: 13
Sprint Backlog
Cost: 20
Cost: 0
Cost: 0
Cost: 2
Cost3
Cost: 5
Cost: 3
Cost10
Cost:10
© 1993-‐2011 Scrum.org, All Rights Reserved
21
Lane 1 2 3 4 5
What 1 Develop Acceptance tests for PBIs
Detailed Design
Automate all tests
Test soLware and doc.
Fix and repeat 4 unIl all works
Who 1 Whole team Whole team
QA, Analyst Whole team Whole team
What 2 Write unit tests and code
Who 2 Designers, programmers
What 3 Write documentaIon
Who 3 Tech writers
Test First Development Kanban Training Wheels
© 1993-‐2011 Scrum.org, All Rights Reserved
22
Sample Sprint Backlog Board
© 1993-‐2011 Scrum.org, All Rights Reserved
23
Backlog Grooming
• Grooming means – Planning the PBL to an acIonable level of detail – Maintaining a Rolling Backlog ProjecIon
• Plan 10% of each Sprint to be spent grooming the Product Backlog
• Top ordered Product Backlog items are well understood and easily selected in Sprint Planning
• Never allow the Product Owner to go into the Sprint Planning meeIng with an un-‐groomed Product Backlog.
© 1993-‐2011 Scrum.org, All Rights Reserved
24
Sprint Review
Sprint Review
Increment
Sprint Analysis
Product Backlog
Restore unfinished product backlog to PB
Reformulate development team
Rearrange PB for new opportuniIes
Release one or more increments of funcIonality
Stop SprinIng Add more Scrum Teams
CollaboraAve working session of Scrum Team and key stakeholders
© 1993-‐2011 Scrum.org, All Rights Reserved
25
Sprint Review
Sprint RetrospecIves
• Scrum Team inspects how the last Sprint went
• Scrum Team selects several improvements
• Scrum Team implements improvements for next Sprint(s) Sprint
Time line of Events in Sprint
© 1993-‐2011 Scrum.org, All Rights Reserved
26
Sprint RetrospecIve Books
© 1993-‐2011 Scrum.org, All Rights Reserved
27
Wiley, April 2012 Ken Schwaber & Jeff Sutherland “We hold these truths to be self-‐evident, that all men are created equal, that they are endowed by their Creator with certain unalienable Rights, that among these Life, Liberty and the pursuit of Happiness and SoLware in 30 Days.”
SoLware in 30 Days
© 1993-‐2011 Scrum.org, All Rights Reserved
28
Next Steps
Join the Yahoo! discussion group where you can tap into the collecIve knowledge of Scrum users around the world. hdp://groups.yahoo.com/group/scrumdevelopment/
If you achieve PSM cerIficaIon you are eligible to join the LinkedIn group to conInue the conversaIons with the people you’ve met in this class, and start new ones with other PSMs.
Engage
Stay Connected Subscribe to our RSS feed to receive the latest updates on Scrum.org programs, training, and cerIficaIons. hdp://www.scrum.org/news/rss.xml
Follow us on Twider at @scrumdotorg
© 1993-‐2011 Scrum.org, All Rights Reserved
29
Thank You!