Management & scrum: some comments

2,365 views

Published on

Some comments on Scrum and management.

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

No Downloads
Views
Total views
2,365
On SlideShare
0
From Embeds
0
Number of Embeds
596
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Management & scrum: some comments

    1. 1. Scrum & Management: some comments
    2. 2. Only three roles exist in Scrum:‣ Scrum Master‣ Product Owner‣ Team Member
    3. 3. So, which role do you think is the most importantwhile doing a Scrum implementation?
    4. 4. Wrong.
    5. 5. It’s ... the manager!
    6. 6. Why?
    7. 7. Manager can make a Scrum implementation by:‣ following the process, too‣ giving the team space to self organise‣ reinforcing Scrum principles and values
    8. 8. ... or break it by:‣ not applying the rules to himself‣ thinking a Scrum implementation only effects the development team
    9. 9. Now let’s get practical!
    10. 10. How can you, as a manager, best support yourScrum implementation?
    11. 11. Here’s 10 things you can start doing right now...
    12. 12. Do not disrupt sprints
    13. 13. Need something? Work with the PO andScrum master, not the team
    14. 14. Looking for an update? Listen in on thestand up, read the board
    15. 15. Learn to read a burndown
    16. 16. Always attend the demo
    17. 17. Know the outcome of the retrospectives
    18. 18. Pick up impediments that team cannot fix
    19. 19. Do not challenge estimations and timelines
    20. 20. Put your requests in the product backlog
    21. 21. Give PO full authority on backlog andpriorities
    22. 22. Stop moving people moving between teams
    23. 23. 1) Do not disrupt sprints2) Need something? Work with the PO and Scrum master, not the team3) Looking for update? Listen in on the stand up, read the board4) Learn to read a burndown4) Always attend the demo5) Know the outcome of retrospectives6) Pick up impediments that the teams cannot fix7) Do not challenge estimations and timelines8) Put your requests in the product backlog9) Give the PO full authority on backlog and priorities10) Stop moving people between teams
    24. 24. I
am
Jasper
Verdooren,
founder
 of
Sygmoid.
Find
me
at:
 www.sygmoid.nl about.me/jasperverdooren www.slideshare.com/jasperverdooren www.linkedin.com/in/jasperverdooren jasper.verdooren@sygmoid.nl
    25. 25. ‣ Scrum Master ‣Team lead PO Founded Sygmoid‣ Product Owner ‣ Scrum trainer ‣Consultancy‣ Team lead PO ‣Training & coaching‣ Scrum trainer 2007‐2010 2010‐2011 2011
    26. 26. Thank you for your attention!Questions? Comments? Let me know!

    ×