Scrum master Pushback tips<br />Gil Nahmias, CSP<br />
How many times have you heard this…<br />We need these 5 features done by the end of July<br />But we can only finish 3 by...
Back home…<br />I’ve convinced them to do more! Yay! <br />This project is so failing... <br />Manager<br />Team<br />
What do you think is going to    happen, ultimately?<br />
What do you think is going to    happen, ultimately?<br /><ul><li>Team not delivering
Stress
Quality issues over stress
Rework = waste of money</li></li></ul><li>It’s a scale<br />Always “Yes”<br />Spineless<br />Pushback <br />Always “No”,<b...
It’s a scale<br />Bad surprises<br />Always “Yes”<br />Spineless<br />Pushback <br />Poor improvement driver<br />Always “...
Consider 4 different endings...<br />
different ending – using visibility<br />We need these 5 features done by the end of July<br />After estimating, it seems ...
Different ending – smaller bites<br />We need these 5 features done by the end of July<br />As it is, seems too big. Can y...
Different ending – there is more money than time<br />We need these 5 features done by the end of July<br />Looks like a l...
Different ending – negotiate<br />We need these 5 features done by the end of July<br />Looks like a lot of work. We need ...
Upcoming SlideShare
Loading in …5
×

Scrum Master Pushback Tips

2,180 views

Published on

PO wants too much? They try to shove requirements in the mid-sprint? Here are a few ideas on how to pushback correctly.

0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,180
On SlideShare
0
From Embeds
0
Number of Embeds
279
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide
  • Prod test bizFilter external noisemachine
  • Prod test bizFilter external noisemachine
  • Scrum Master Pushback Tips

    1. 1. Scrum master Pushback tips<br />Gil Nahmias, CSP<br />
    2. 2. How many times have you heard this…<br />We need these 5 features done by the end of July<br />But we can only finish 3 by July...<br />Try harder! Do Overtime!<br />Please prioritize for us<br />Manager<br />Team<br />It already is. All is must.<br />Ok we will do our best... <br />
    3. 3. Back home…<br />I’ve convinced them to do more! Yay! <br />This project is so failing... <br />Manager<br />Team<br />
    4. 4. What do you think is going to happen, ultimately?<br />
    5. 5. What do you think is going to happen, ultimately?<br /><ul><li>Team not delivering
    6. 6. Stress
    7. 7. Quality issues over stress
    8. 8. Rework = waste of money</li></li></ul><li>It’s a scale<br />Always “Yes”<br />Spineless<br />Pushback <br />Always “No”,<br />Comfort zone<br />
    9. 9. It’s a scale<br />Bad surprises<br />Always “Yes”<br />Spineless<br />Pushback <br />Poor improvement driver<br />Always “No”,<br />Comfort zone<br />
    10. 10. Consider 4 different endings...<br />
    11. 11. different ending – using visibility<br />We need these 5 features done by the end of July<br />After estimating, it seems like 3 first features will probably get done. 4th feature – maybe and last one will probably not get done by July.<br />But we need all of them! Deliver all the features!<br />Manager<br />Team<br />Well we can SAY we will deliver. That won’t change reality. However we promise to let you know once our prediction changes.<br />Ok. keep me in the loop.<br />
    12. 12. Different ending – smaller bites<br />We need these 5 features done by the end of July<br />As it is, seems too big. Can you chop them into smaller pieces?<br />How is that going to help?<br />This way we can identify sub-stories we can live without, or ones to give some other team with more capacity.<br />Manager<br />Team<br />Can you start working before breaking down?<br />In the coming 2 weeks – yes. Not later. Enough time to get ready on your end?<br />
    13. 13. Different ending – there is more money than time<br />We need these 5 features done by the end of July<br />Looks like a lot of work. Help?<br />I can extend the team<br />Too late to add people now (see: Brooks’s Law). <br />But we can use manpower in other ways<br />Manager<br />Team<br />I’m all ears<br />The new guys can help by taking easy and managerial tasks off our load so we can focus on the special things only we can do.<br />
    14. 14. Different ending – negotiate<br />We need these 5 features done by the end of July<br />Looks like a lot of work. We need your help<br />Doing what?<br /><ul><li>Filter external noise for us so we can focus better
    15. 15. Have the product guys test the business
    16. 16. And we need a faster build server</li></ul>Manager<br />Team<br />I can filter noise and talk to the product. Build server is out of reach now. What can you do with that?<br />
    17. 17. Remember: Pushback is an advanced scrum master skill!<br /> Use it wisely.<br />
    18. 18. Not sure? Ask me more!<br />gil@agilesparks.com<br />myagile.co.il<br />@gilnahmias<br />

    ×