How to Plan Effectively in the Face of Uncertainty

In a recent post, I explained why weโ€™re inherently bad at estimating, which is a major reason software projects often run late. But that doesnโ€™t mean we canโ€™t plan ahead for the longer term and manage expectations. Here are some techniques Iโ€™ve found effective for longer-term planning, even in the face of uncertainty:

๐—ฃ๐—ฟ๐—ผ๐˜ƒ๐—ถ๐—ฑ๐—ฒ ๐—ฅ๐—ฎ๐—ป๐—ด๐—ฒ๐—ฑ ๐—™๐—ผ๐—ฟ๐—ฒ๐—ฐ๐—ฎ๐˜€๐˜๐˜€ ๐ŸŒฆ, ๐—ก๐—ผ๐˜ ๐—™๐—ถ๐˜…๐—ฒ๐—ฑ ๐—˜๐˜€๐˜๐—ถ๐—บ๐—ฎ๐˜๐—ฒ๐˜€

Over any reasonable period of time, providing likely delivery dates as a range rather than a fixed date is better. Doing so embraces the inherent variability and help stakeholders better appreciate uncertainty. Giving a fixed date, even when you all know itโ€™s just an estimate, sets false expectations.

๐——๐—ผ๐—ปโ€™๐˜ ๐—ท๐˜‚๐˜€๐˜ ๐—ฒ๐˜€๐˜๐—ถ๐—บ๐—ฎ๐˜๐—ฒ ๐˜๐—ถ๐—บ๐—ฒ โฑ, ๐—ฒ๐˜€๐˜๐—ถ๐—บ๐—ฎ๐˜๐—ฒ ๐—ฐ๐—ผ๐—ป๐—ณ๐—ถ๐—ฑ๐—ฒ๐—ป๐—ฐ๐—ฒ ๐Ÿ’ช

Along with estimating how long a task might take, assess how confident you are in that estimate. Is it something weโ€™ve done before and know well? High confidence. Is it new, complex, or something weโ€™ve never tackled before? Medium or Low confidence.Multiply time by confidence. For example, a โ€œSmallโ€ task (e.g. 1-3 days) with “Low” confidence can be re-forecast as 1-7 days.

๐—Ÿ๐—ผ๐—ป๐—ด๐—ฒ๐—ฟ ๐—ง๐—ฒ๐—ฟ๐—บ ๐—ฃ๐—น๐—ฎ๐—ป๐—ป๐—ถ๐—ป๐—ด ๐—ฎ๐˜€ ๐—ฅ๐—ถ๐˜€๐—ธ ๐— ๐—ฎ๐—ป๐—ฎ๐—ด๐—ฒ๐—บ๐—ฒ๐—ป๐˜ ๐Ÿšจ

Effective planning isnโ€™t just about setting expectations on delivery, but managing risks over the project lifecycle. All those estimates which have come in as Large or with Medium-Low confidence? Those are your biggest risks and represent the most uncertainty. Identify risks early, identify potential mitigations, highlight those risks to stakeholders.

๐—”๐—ฐ๐—ฐ๐—ผ๐˜‚๐—ป๐˜ ๐—ณ๐—ผ๐—ฟ ๐—ข๐—ฝ๐˜๐—ถ๐—บ๐—ถ๐˜€๐—บ ๐—•๐—ถ๐—ฎ๐˜€ ๐ŸŒˆ

Whilst you canโ€™t completely mitigate against this, there are things you can do to be a bit less vulnerable. Involve the entire team in estimates, account for full end to end delivery (not just developer time) and factor in holidays, sickness and other factors that could impact delivery.Also, those ranged forecasts which provide a cumulative lowest range for all the work? Highly unlikely due to optimism bias! Itโ€™s probably best not to present the most optimistic forecast for this reason.

๐—ก๐—ผ ๐—ฆ๐—ถ๐—น๐˜ƒ๐—ฒ๐—ฟ ๐—•๐˜‚๐—น๐—น๐—ฒ๐˜, ๐—•๐˜‚๐˜ ๐—ฎ ๐—•๐—ฒ๐˜๐˜๐—ฒ๐—ฟ ๐—”๐—ฝ๐—ฝ๐—ฟ๐—ผ๐—ฎ๐—ฐ๐—ต

These practices wonโ€™t eliminate uncertainty or guarantee perfect outcomes – there’s no silver bullet in longer term planning. However, Iโ€™ve found they help organisations plan more realistically, reducing the stress and frustration that often come with missed deadlines, and enabling more effective, adaptable strategies in the face of uncertainty.

Leave a Reply

Your email address will not be published. Required fields are marked *