Projects sanity check
summary
Argues for a project sanity check by tracing requirement history, interviewing finance and stakeholders, and doing a cost-benefit spreadsheet that exposes weak assumptions. Finds the swag shop makes about $80k revenue while a single staffer costing $60k spends 10 hours weekly on cash processing, so estimated losses are only ~$20k. Delivers a two-page PowerPoint with three options, recommends stopping the unmanned PCI build, and the project is ceased.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:40About me
- 2:30Silent problem
- 6:07Project costs
- 6:33What is the problem
- 17:43Communication
- 22:01Conclusion
related talks
46mIt's the Empathy, Stupid!
45mReducing Toil in Your AppSec Program
27mHealth Check-ups on OSS Software Projects: Managing Risks While Promoting (Re)use
20mHow to keep everyone happy (on a shoestring)?
51mTaking Advantage of a Recession to Push a Program to World Class
46mBusinesses Run On Risk And Debt: Why Communicating Security Risk Is Hard
01h 54mOWASP Leaders Workshop AppSecUSA 2018 - Part 2
01h 04mShifting Security Everywhere