effectively dealing with deadline pressure
play

EFFECTIVELY DEALING WITH DEADLINE PRESSURE DAVE MOORE 8TH LIGHT * - PowerPoint PPT Presentation

EFFECTIVELY DEALING WITH DEADLINE PRESSURE DAVE MOORE 8TH LIGHT * EFFECTIVELY DEALING WITH DEADLINE PRESSURE WHO IS INVOLVED? Stakeholders (managers, executives, etc.) Engineers (dev, qa, ops, sys, etc.) Users (internal users,


  1. EFFECTIVELY DEALING WITH DEADLINE PRESSURE DAVE MOORE 8TH LIGHT

  2. *

  3. EFFECTIVELY DEALING WITH DEADLINE PRESSURE WHO IS INVOLVED? ▸ Stakeholders (managers, executives, etc.) ▸ Engineers (dev, qa, ops, sys, etc.) ▸ Users (internal users, paying customers, etc.)

  4. ALL PARTIES INVOLVED WANT A QUALITY PRODUCT.

  5. WHY IS THERE A DISCONNECT THEN?

  6. EFFECTIVELY DEALING WITH DEADLINE PRESSURE LEVERS ▸ A lever is any action that someone can take to get the project closer to completion ▸ Levers get pulled every day ▸ Problematic when pulled without thinking through affects

  7. EFFECTIVELY DEALING WITH DEADLINE PRESSURE STAKEHOLDERS - LEVERS ▸ Promotion(s) ▸ Threaten budget cut ▸ Force extra hours ▸ Cut scope ▸ Extend deadline ▸ Hire additional team members ▸ Re-prioritize other team efforts to support your team ▸ Pull plug on project

  8. EFFECTIVELY DEALING WITH DEADLINE PRESSURE USERS - LEVERS ▸ Threaten/take legal action ▸ Stop using product ▸ Bash product on social media ▸ Invest their money ahead of time to see product hit market ▸ Message customer service agent

  9. EFFECTIVELY DEALING WITH DEADLINE PRESSURE ENGINEERS - LEVERS ▸ Skimp out on testing ▸ Not think about the proper abstraction, design, and/or architecture ▸ Skip review process ▸ Skip pairing ▸ Don’t spend time estimating/grooming ▸ Work more hours

  10. EFFECTIVELY DEALING WITH DEADLINE PRESSURE EFFECTS OF GOING “FAST” ▸ Code/Infrastructure that’s hard to maintain ▸ Unreadable ▸ Error prone ▸ Tightly coupled ▸ Future deadlines are harder to meet ▸ Morale plummets ▸ Bugs occur more frequently - customers complain

  11. EFFECTIVELY DEALING WITH DEADLINE PRESSURE COMMUNICATION WASTE ▸ Leverage the Agile Process ▸ Avoid status checks ▸ Define story thoroughly in card (include F.A.Q.) ▸ Favor direct communication for low level implementation questions

  12. EFFECTIVELY DEALING WITH DEADLINE PRESSURE THE NEGOTIATION ▸ Meeting with stakeholder, engineer, and user ▸ Purpose: level set & assess options/trade-offs at the story level ▸ Should happen regularly

  13. EFFECTIVELY DEALING WITH DEADLINE PRESSURE THE NEGOTIATION - SCOPE ▸ Scope is always negotiable ▸ Challenge stakeholders to think critically about importance of every single component ▸ Deliver MVP early on and deliver features each iteration

  14. EFFECTIVELY DEALING WITH DEADLINE PRESSURE THE NEGOTIATION - ASSESS VALUE ▸ Discuss consequences of missing the deadline ▸ Assess importance of deadline ▸ Stakeholders often overvalue importance of hitting deadline to detriment of project

  15. ESTIMATES ARE SUPPOSED TO HELP STAKEHOLDERS MANAGE PROJECT RISKS.

  16. EFFECTIVELY DEALING WITH DEADLINE PRESSURE THE NEGOTIATION - ESTIMATION ▸ No estimates ▸ Uniform estimates ▸ Complexity based ▸ Fibonacci ▸ T-Shirt size ▸ etc. ▸ Time based

  17. EFFECTIVELY DEALING WITH DEADLINE PRESSURE THE NEGOTIATION - ESTIMATION ▸ Date ranges ▸ Regularly revisit estimates ▸ Optimistic ▸ Create feedback loop ▸ Realistic ▸ Track actuals ▸ Pessimistic ▸ Retro on incorrect estimates ▸ Inception to deployed ▸ Avoid anchoring effect ▸ Estimate an hour as a pair hour ▸ Add bucket for scope creep ▸ Represent current snapshot of team’s understanding

  18. WHEN STAKEHOLDERS, ENGINEERS, AND USERS HAVE A SHARED CONTEXT, THE CORRECT LEVERS GET PULLED.

  19. THANKS

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend