Scrum introduction
Steve Zhang
What is Scrum?
An agile framework for
completing complex
projects.
– Scrum Alliance
Created by Jeff Sutherland
and Ken Sch...
Scrum Features






Self-organized
Cross-functional
Iterative/incremental
Time-boxed
Transparency/Visibility
Scrum Team Roles




Product Owner
ScrumMaster
Team members
Cross-functional Team





All team members are equal
No specific title/label for each member
No Special task for spec...
Self-organized team







No team lead
Can not assign specific task to specific team
member
Team choose the backlog ...
Sprint








Time-boxed: 2 weeks/1 month
PBIs (Product Backlog Item) are frozen during
each sprint
Can only be canc...
Product Backlog vs. Sprint backlog




Product Backlog
Independent
Ordered by ROI
Owned by PO





Sprint Backlog
Sp...
Daily Scrum




Organized by ScrumMaster
Standup meeting < 15 minutes
Each member answer 3 Questions:
Completed?
Will C...
ScrumMaster Role




Facilitate process improvements
Protect the team
Remove obstacles
Remove
 Move out
 Shield
 Tra...
Definition of “Done”




Team needs a shared definition of “Done”, to
ensure transparency.
The definition will expand t...
Scrum is/is NOT
IS a framework for delivering software,
NOT an SDLC or buffet of best practices
 IS good for new product ...
User Story – Product Backlog Item





An invitation to conversation
3 things
User – Who?
Story/function – What?
Benefi...
INVEST - validate a user story







Independent
Negotiable
Valuable
Estimatable
Small
Testable
Estimation - Planning poker
Estimate user story






Planning Poker
Estimate Value – by PO, stake holder
Estimate Effort - by team
ROI = value /...
Scrum board
Burndown Chart
The science behind Scrum





Software Development is a complex system
Defined process control – problem is predictable...
Cynefin Framework
Thoughts about Scrum






Scum is a meta process (framework)
 Each scrum team has to customize its own rules on top o...
Thoughts about Continuous
Improvement


At the end of each Sprint
Get the job done
 Improve the process
 Improve the co...
Organization change?





Restructure to cross-functional teams
From Command-and-Control to Self-organized
Scaling Scr...
Managers change?




From command-and-control to self-organized
From governance to servant leadership
New roles?
Provid...
Developers change?







Scrum assumes/requires professional developers
More authorities, more responsibilities
Need...
Think about…






How much did our company (team) adopt
Scrum so far?
Are we doing the “true” Scrum?
Is Scrum suitabl...
References





http://www.worldmindware.com/CertifiedScrumMa
http://agilemanifesto.org/
http://scrumalliance.org/
htt...
Thank you!
Scrum introduction
Scrum introduction
Scrum introduction
Upcoming SlideShare
Loading in...5
×

Scrum introduction

164

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
164
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • {}
  • Scrum introduction

    1. 1. Scrum introduction Steve Zhang
    2. 2. What is Scrum? An agile framework for completing complex projects. – Scrum Alliance Created by Jeff Sutherland and Ken Schwaber in 1995.
    3. 3. Scrum Features      Self-organized Cross-functional Iterative/incremental Time-boxed Transparency/Visibility
    4. 4. Scrum Team Roles    Product Owner ScrumMaster Team members
    5. 5. Cross-functional Team     All team members are equal No specific title/label for each member No Special task for special person Have multiple skill set
    6. 6. Self-organized team      No team lead Can not assign specific task to specific team member Team choose the backlog items – “Pull” based Each member is volunteer to choose task No individual performance tracking, team based performance
    7. 7. Sprint      Time-boxed: 2 weeks/1 month PBIs (Product Backlog Item) are frozen during each sprint Can only be cancelled by Product owner Produce potential shippable System after each sprint Defects are put into backlog top for the next sprint
    8. 8. Product Backlog vs. Sprint backlog    Product Backlog Independent Ordered by ROI Owned by PO    Sprint Backlog Split PBI into tasks Can be dependent Owned by team
    9. 9. Daily Scrum    Organized by ScrumMaster Standup meeting < 15 minutes Each member answer 3 Questions: Completed? Will Complete? Obstacles?
    10. 10. ScrumMaster Role    Facilitate process improvements Protect the team Remove obstacles Remove  Move out  Shield  Transform  Overpower  Go around 
    11. 11. Definition of “Done”    Team needs a shared definition of “Done”, to ensure transparency. The definition will expand to include more items for higher quality 4 techniques to “Done” Automation  Expand skills to team  Give team authority  Get rid of waste 
    12. 12. Scrum is/is NOT IS a framework for delivering software, NOT an SDLC or buffet of best practices  IS good for new product development NOT good for maintenance team  Covers on manager side only, NOT on developer side  Needs to adopt other practices  Has pressure, needs big changes in organization/Management/Developers  IS continuous improvement 
    13. 13. User Story – Product Backlog Item    An invitation to conversation 3 things User – Who? Story/function – What? Benefit – Why? User story template As a [user], I can [story/function], so that [benefit]
    14. 14. INVEST - validate a user story       Independent Negotiable Valuable Estimatable Small Testable
    15. 15. Estimation - Planning poker
    16. 16. Estimate user story      Planning Poker Estimate Value – by PO, stake holder Estimate Effort - by team ROI = value / effort Estimation is a relative value, NOT absolute value
    17. 17. Scrum board
    18. 18. Burndown Chart
    19. 19. The science behind Scrum    Software Development is a complex system Defined process control – problem is predictable, well understood Empirical process control – deal with unpredictable problems  Visibility  Inspection  Adaption - From “Agile project management with Scrum” by Ken Schwaber
    20. 20. Cynefin Framework
    21. 21. Thoughts about Scrum    Scum is a meta process (framework)  Each scrum team has to customize its own rules on top of Scrum  Not cover developers side, we need to adopt other practices  A process of continuous improvement Has a higher requirements  Organization  Management  Developer Relies on frequent feedback
    22. 22. Thoughts about Continuous Improvement  At the end of each Sprint Get the job done  Improve the process  Improve the code base  Improve the skills 
    23. 23. Organization change?     Restructure to cross-functional teams From Command-and-Control to Self-organized Scaling Scrum Need a new strategy for performance review Team based review vs. individual based  Intrinsic motivation vs. external motivation 
    24. 24. Managers change?    From command-and-control to self-organized From governance to servant leadership New roles? Provide an working environment to make developer use their full potential  Focus on the system level  Focus on long term improvement 
    25. 25. Developers change?      Scrum assumes/requires professional developers More authorities, more responsibilities Need to learn more skills – general specialist Need to pursue technical excellence, software craftsmanship Need to be more cooperative
    26. 26. Think about…     How much did our company (team) adopt Scrum so far? Are we doing the “true” Scrum? Is Scrum suitable for our company (team)? What do we need to improve to do Scrum?
    27. 27. References     http://www.worldmindware.com/CertifiedScrumMa http://agilemanifesto.org/ http://scrumalliance.org/ http://en.wikipedia.org/wiki/Cynefin
    28. 28. Thank you!
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×