Search Results

Estimate Delivery Milestones from Throughput You have half a solution already. While your scheduling process isn't particularly agile, you can extend what you're already doing by calculating cycle ti …

Continuous Delivery and Scrum Scrum is about time-boxing. Continuous delivery is about rolling releases and (to some extent) automated continuous integration and deployment. They are not completely o …

Stakeholder Management is Mostly the Product Owner The Scrum Guide is largely silent on issues of stakeholder management per se, although the Product Owner's role of managing the Product Backlog stro …

TL;DR Some frameworks have a distinct name for the type of work you're asking about, but some don't. To understand why, a short preface is in order. Work is work. While it's sometimes necessary to d …

Refer to the Definition of Done (DoD) and Working Agreements In [S]crum, when do developers typically check their [S]print code into production? There is no prescriptive answer within the Scrum fram …

TL;DR Release planning is an estimated management target, generally based on level-of-effort estimates of large themes or epics. Sprint Planning is a team commitment based on iteration-sized user sto …

TL;DR In any agile framework, if you want to estimate based on fixed scope, your estimated release dates will vary. If you opt instead for a fixed release date or routine release cadence, then it's s …

Both Developers and Executives Broke the Agile Contract It was due for a release tomorrow but, as a result of a review by management, needs reworking. This will undoubtedly add a lot of time onto …

TL; DR Agile release planning is based on fixed-length, normed-capacity cycles that operate on dynamically-planned and dynamically-scoped features. In Scrum, fixed-date release planning must be handl …