In the previous blogs of this series we’ve looked at the importance of establishing a MUST HAVE payload and also being aware of the dependencies that your teams/features may have with other teams/products. Of course, the more teams and the more complex the payload then the more difficult it will be to determine what needs […]

So we can envisage a release with multiple features and we can (and should) prioritise them so that in the event of a change to scope or team priorities it’s clear what are the essential features that constitute the MUST HAVE payload forming the Minimum Marketable Features (MMF). With a single team this should be […]

On Weds 7th March I went to the Project Challenge Expo ( in Kensington Olympia in London. Here’s my summary of three presentations that I attended – Agile Project Management: why has it become so popular and how can you get the most from it! (Keith Richards, agileKRC) Entertaining and compelling presentation by Keith Richards […]

Let’s assume we’ve got a product release scheduled and associated with this release there are several features – what is on the critical path? With the pressures to release on-time coupled with the natural reluctance to de-prioritise we could easily get the feeling that all of the features are as important as each other. But is […]

One aspect of Agile Project Management that I’ve thought about for several years is the idea of the Agile Critical Path. Critical Paths are something that Project Managers very quickly learn can have a significant impact – I recall in pre-agile days examining in detail a Gantt chart trying to work out how the critical […]

The next Project Challenge will be on 6th and 7th March at London Olympia. It’s free and a great way to see interesting presentations on all aspects of Project Management and to network with other professionals. See here for more details –

I’d highly recommend reading “Kanban and Scrum – making the most of both” by Henrik Kniberg and Mattias Skarin. It’s got some great examples and points about the differences and similarities between Scrum and Kanban – for example “Scrum is more prescriptive than Kanban” where on a scale that has “Do Whatever” as “0” and RUP as […]