Category Archives: Release Planning

Release Planning

This is a short post to summarize my recommendations for Release Planning. First, release planning is what we do before we start Sprinting. It is where we plan the initial Product Roadmap and develop the initial ‘plan.’ It is pretty important. We do it just before we start doing Sprints. Some people believe one myth […]

Release Planning & the Early Warning System

Building complex innovative products is, of course, hard. In that context, what is the purpose of Release Planning in Scrum/Agile? I will not provide a complete explanation here, but will give a few key ideas. A consensus view of the ‘same’ elephant. I want all the team members to see the whole product and to […]

Against Central Planning

Do we like central planning?  No. In general, to some of us it seems simpler to have one central brain plan everything, to assume that that brain has it right and that “everything will work out for the best in this best of all possible worlds” if the central planner plans it for us rationally. […]

Defining Business Value // #1 Risk

I hear many people complain that it is hard to define Business Value, so they won’t do it. Or, they won’t try any harder to do it. That it is hard and always changing is true. That fact does not, though, give us sufficient reason not to work hard to get better. I won’t reiterate […]

Completing a Release

OK, so we have a known velocity in story points. And, having that, it is an exercise for a 6-year-old to figure out how many more Sprints until the release. Example: We have a velocity of 20 and the remaining stories in the backlog for this release have a total of 100 story points. So […]

Identify your multiple! What?!

Let’s discuss the last post from the skeptic’s point of view. Simon (the implementer) 1: “OK, I don’t want to get fired, but what’s this ‘multiple’ got to do with it?” The multiple is the relationship between the cost of the team and the NPV (net present value) of the benefits the team delivers. As […]

The Nokia Test (6): Estimates created by the team

Another installment on the Nokia Test. Before we begin, a quick mention that Jeff Sutherland has done an improved scoring on the Nokia Test. See here. So, the next item on the test says: “The Product Backlog has estimates created by the team.” Why is this important and what does it mean? Meaning first: So, […]

Agile Portfolio Management – 1

A few people have been asking about “Agile Portfolio Management,” or at least, “How do we manage this stuff?” What they mean is what I call Agile Portfolio Management. Agile Portfolio Management is of course distinct from Scrum, but for simplicity, I have assumed a Scrum context. First, Scrum is relatively silent on this subject, […]