Lightning Talks
summary
A set of short experiences argues that padded estimates in a travel project consistently eat the buffer and push work buffers 2–3× beyond planned time so switching to no estimates plus doing work in small steps and measuring actual cycle time would have reduced customer cost. Hands-on changes suggested are adopting Terraform and Chef earlier to treat infrastructure as code and converting Jenkins into a Jenkins pipeline 2.3 with dev→test→deploy stages to surface integration bugs sooner.
AI-written summary · about
related talks
29mLightning Talks
48mRespect estimates
05mLightning talks – Katarzyna Mydło
06mLightning Talk: Undefined Behavior - Toolkit to Improve Communication With Clients
47mContinuous Deprovement will eat your product for breakfast
07mLightning talks – Konrad Gniazdowski
34mHow to effectively communicate to Developers/PMs - A guide for developers and project managers
51mRespect estimates