New Product Development Driven by Choosing Bad Practices and Failing Forward
summary
A four-person fully remote team built a pharmacy SaaS MVP (April–October) using no estimates and by starting implementation early rather than waiting for full readiness. They mapped about 60 user stories in a two-dimensional prioritization map, added infrastructure tasks, and implemented infrastructure with Terraform on AWS, containers, and a TypeScript backend. The early start cut infrastructure time from an estimated 2–3 months to about one month but caused 2–3 rewrites, a 1.5-month reschedule, and a late production-only bug discovered during final checks.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 5:44Skipping estimates
- 13:42Engineering manager's vision
- 24:21Bad practices in action
- 32:13Rescheduling and focus
- 39:00Summary
- 43:20Q&A
related talks
22mEvolving DevOps Teams and Flexible Organizational Culture
37mProduct to the European Market in 5 Months! Scientific Not-Science-Fiction
25mMoving from Project to Product
25mBringing Product thinking to DevOps
30mProduction › Prototype: How a Small Team Replaced a Core Platform in 90 Days
01h 01mMicroservices Gone Wrong
39mMinimal Viable Architecture
40mA Developer’s Tour in 360 Days