Agile Software Development: Practice and Analytics
summary
Starts projects with a facilitated discovery workshop that includes business and technical stakeholders, captures requirements plus explicit acceptance criteria, and creates JIRA epics and story points to measure velocity. Use TDD/BDD, peer reviews, unit and regression tests, single-branch workflow and feature toggles to deploy in shadow mode; deploy only Mon–Wed and reserve 20–30% contingency of sprint capacity. Plan sprints with 100/75/50 percent certainty across upcoming sprints, double early estimates, run standups around 10:00, and keep retrospectives short.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 6:58Agile principles today
- 13:22Discovery and requirements
- 21:35Sprint planning strategies
- 27:07Deployment and risk management
- 33:40Estimation and team dynamics
- 37:22Retrospectives and sprint types
- 39:54Q&A and wrap-up
related talks
20mAgile development application for live ops
11mLeading Agile Teams to Success: Lessons from the Trenches
35mGo Big with Supercharged Agile
49mBaking Boards: Tweak the Recipe for Agile Development
39mAgile Scrum Overview
48mHow to Win and Start Contract Development Projects That Leverage Agile Values
35mAgile Scrum Overview
39mScrum at Scale