Release Planning: Retiring the Term but not the Technique It may be time to retire the phrase release planning from the Scrum or agile vocabulary.
Agile Estimating Maybe you’ve heard about agile software development projects but aren’t sure if they allow for the …
Estimating a Full Backlog Based on a Sample of It How do we estimate how many hours it will take to deliver a given product backlog if we have no …
Distributed Teams: Build Trust through Early Progress Teams with subgroups formed around compatible skills, attitudes and approaches to work are less …
Using a One-Handed Clock to Convey Project Goals The One-Handed Clock is a useful visual metaphor that can be hung in a team room.
Why Do Release Planning? An agile team does release planning to avoid the same type of problems we avoid with a topographic …
Why There Should Not Be a “Release Backlog” We've already overloaded the word backlog with product backlog and sprint backlog. Why confuse …
Predicting Velocity When Teams Change Frequently As a measure of the amount of work completed in an iteration, velocity works extremely well when …
Visualizing a Large Product Backlog With a Treemap Treemaps are an excellent way of visualizing large product backlogs.
Improving On Traditional Release Burndown Charts By producing a single chart that shows both a team's rate of progress and the product backlog, we …
Why I Don’t Use Story Points for Sprint Planning I don't use story points for sprint planning because story points are a useful long-term measure. …
Sprint and release planning should be in different units In sprint planning the team should always talk of tasks and hours.