Architecture &ITCamp 2012 sponsors                                                       Best Practices@   itcampro   # it...
SCRUM. Removing ImpedimentsDan Nicola | MAXCODE
What to expectAgile principles & ScrumTop 7 impedimentsHow good is your Scrum?
Individuals and interactions            over    processes and tools
Working software            overcomprehensive documentation
Customer collaboration         over contract negotiation
Responding to change        over  following a plan
Scrum Framework3 roles3 artifacts5 ceremonies
3 rolesProduct OwnerScrum MasterTeam
3 artifacts
5 ceremoniesProduct GroomingSprint PlanningDaily MeetingSprint ReviewSprint Retrospective
ImpedimentsKeep the team from being productiveTeam – communicateScrumMaster - remove
Lack of focus
No working software (not DONE)
Priorities and specifications (backlog issues)
Waterfall mindset
Interruptions
Technical debt
Dependency on key people
Removing impediments…                        …makes the difference!
Remember! Let the team do the work Rapid value creation is key! SCRUM makes it work,  The Team does the work SM enable...
ScrumBut...(ScrumBut)(Reason)(Workaround)
ScrumBut... TestAka the “Nokia Test”Goals:  Indicator where you are in your Scrum   practices  Collect data for a stat...
QuestionsIterationsTestingAgile SpecificationsProduct OwnerProduct BacklogEstimatesSprint Burndown ChartTeam Disru...
Questions Fixed iteration length 4 weeks or less Software is deployed Good user stories tied to specifications as  need...
Scrum SmellsLoss of RhythmTalking ChickensMissing PigsPersistent SignaturesScrum Master Assigns WorkThe Daily Scrum ...
ConclusionScrum is not going to solve your problems,it’s just going to make them in-your-faceobvious, every day. (Ken Schw...
Thank You!     I’d really appreciate your feedback!     DAN.NICOLA@MAXCODE.RO@   itcampro   # itcamp12      Premium confer...
ITCamp 2012 - Dan Nicola - Scrum v2
ITCamp 2012 - Dan Nicola - Scrum v2
Upcoming SlideShare
Loading in...5
×

ITCamp 2012 - Dan Nicola - Scrum v2

295

Published on

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

  • Be the first to like this

No Downloads
Views
Total Views
295
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

ITCamp 2012 - Dan Nicola - Scrum v2

  1. 1. Architecture &ITCamp 2012 sponsors Best Practices@ itcampro # itcamp12 Premium conference on Microsoft technologies
  2. 2. SCRUM. Removing ImpedimentsDan Nicola | MAXCODE
  3. 3. What to expectAgile principles & ScrumTop 7 impedimentsHow good is your Scrum?
  4. 4. Individuals and interactions over processes and tools
  5. 5. Working software overcomprehensive documentation
  6. 6. Customer collaboration over contract negotiation
  7. 7. Responding to change over following a plan
  8. 8. Scrum Framework3 roles3 artifacts5 ceremonies
  9. 9. 3 rolesProduct OwnerScrum MasterTeam
  10. 10. 3 artifacts
  11. 11. 5 ceremoniesProduct GroomingSprint PlanningDaily MeetingSprint ReviewSprint Retrospective
  12. 12. ImpedimentsKeep the team from being productiveTeam – communicateScrumMaster - remove
  13. 13. Lack of focus
  14. 14. No working software (not DONE)
  15. 15. Priorities and specifications (backlog issues)
  16. 16. Waterfall mindset
  17. 17. Interruptions
  18. 18. Technical debt
  19. 19. Dependency on key people
  20. 20. Removing impediments… …makes the difference!
  21. 21. Remember! Let the team do the work Rapid value creation is key! SCRUM makes it work, The Team does the work SM enables the process Protects, facilitates and coaches Ensures impediments are busted
  22. 22. ScrumBut...(ScrumBut)(Reason)(Workaround)
  23. 23. ScrumBut... TestAka the “Nokia Test”Goals:  Indicator where you are in your Scrum practices  Collect data for a statistical study9 Questions
  24. 24. QuestionsIterationsTestingAgile SpecificationsProduct OwnerProduct BacklogEstimatesSprint Burndown ChartTeam DisruptionsTeam
  25. 25. Questions Fixed iteration length 4 weeks or less Software is deployed Good user stories tied to specifications as needed Product Owner who motivates team Product Owner can measure ROI Estimates produced by planning poker by team Burndown chart burns down when story is done Noone disrupting team, only Scrum roles Team is in hyperproductive state
  26. 26. Scrum SmellsLoss of RhythmTalking ChickensMissing PigsPersistent SignaturesScrum Master Assigns WorkThe Daily Scrum is for the Scrum MasterSpecialized Job RolesSource: “Toward a Catalogue of Scrum Smells”, by MikeCohn
  27. 27. ConclusionScrum is not going to solve your problems,it’s just going to make them in-your-faceobvious, every day. (Ken Schwaber)
  28. 28. Thank You! I’d really appreciate your feedback! DAN.NICOLA@MAXCODE.RO@ itcampro # itcamp12 Premium conference on Microsoft technologies
  1. A particular slide catching your eye?

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

×