This document summarizes a presentation about removing impediments in Scrum. It discusses the key principles of Scrum, including roles, artifacts, and ceremonies. It identifies the top 7 impediments as lack of focus, no working software, priorities/specification issues, waterfall mindset, interruptions, technical debt, and dependency on key people. It emphasizes that the Scrum Master's role is to remove impediments to allow the team to work productively. It also includes a "ScrumBut" test to assess how well an organization adheres to Scrum practices and identifies common "Scrum smells" that indicate issues.

1. Architecture &
ITCamp 2012 sponsors Best Practices
@ itcampro # itcamp12 Premium conference on Microsoft technologies

2. SCRUM. Removing Impediments
Dan Nicola | MAXCODE

3. What to expect
Agile principles & Scrum
Top 7 impediments
How good is your Scrum?

4. Individuals and interactions
over
processes and tools

5. Working software
over
comprehensive documentation

6. Customer collaboration
over
contract negotiation

7. Responding to change
over
following a plan

8. Scrum Framework
3 roles
3 artifacts
5 ceremonies

9. 3 roles
Product Owner
Scrum Master
Team

10. 3 artifacts

11. 5 ceremonies
Product Grooming
Sprint Planning
Daily Meeting
Sprint Review
Sprint Retrospective

12. Impediments
Keep the team from being productive
Team – communicate
ScrumMaster - remove

13. Lack of focus

14. No working software (not DONE)

15. Priorities and specifications (backlog issues)

16. Waterfall mindset

17. Interruptions

18. Technical debt

19. Dependency on key people

20. Removing impediments…
…makes the difference!

22. 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

23. ScrumBut...
(ScrumBut)(Reason)(Workaround)

24. ScrumBut... Test
Aka the “Nokia Test”
Goals:
 Indicator where you are in your Scrum
practices
 Collect data for a statistical study
9 Questions

25. Questions
Iterations
Testing
Agile Specifications
Product Owner
Product Backlog
Estimates
Sprint Burndown Chart
Team Disruptions
Team

26. 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

27. 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 Roles
Source: “Toward a Catalogue of Scrum Smells”, by Mike
Cohn

29. Conclusion
Scrum is not going to solve your problems,
it’s just going to make them in-your-face
obvious, every day. (Ken Schwaber)

30. Thank You!
I’d really appreciate your feedback!
DAN.NICOLA@MAXCODE.RO
@ itcampro # itcamp12 Premium conference on Microsoft technologies