The senior managers, those people responsible for the direction of the organisation, need to know when releases will happen. Commitments are made against releases – to customers, partners, and even to others within the business, so it is important that releases happen when agreed. The current release of an organisation is typically wrapped up in a project or program which is working towards delivery on a particular date.
But what about beyond the current project or program? In a non-agile organisation the portfolio tends to be a number of projects organised into time-slots according to the priority of the project to the business. In agile we can do things differently. We can think at feature level. Thus, instead of planning a set of projects, we can think about features, slot these features into iterations, and plan when the next release should happen based on this.
A lot of organisations these days are using agile to transform the way they develop products. The next logical step is to make the portfolio management process within these organisations more agile. But how can this be achieved?
I’m sure most of you have too many items in your portfolio than you’ll ever actually have the capability to deliver. Here is a simple agile portfolio planning exercise I’ve seen used which is very effective for rapidly realigning the portfolio to the business. It’s called “Hot Cup”.
Hot Cup is simple to use, great fun, and the best way I know to rapidly reorganise the portfolio. Here is how it works:
By creating diverse teams from different parts of the business, some interesting and fun debates should occur, and individuals will be exposed to opinions they don’t normally encounter in their day-to-day functional organisation, which can only be a good thing.
Once the group have had their hour to carry out the “Hot Cup” exercise, get one member from each team to walk everyone through their “Hot Cup” cards, and explain why they have chosen the priority they have for these cards.
Product Management can then use the results of this exercise to adjust the portfolio. From my experience of this exercise some surprising results often emerge, for example, that it may be better to make your current systems more reliable than to focus on new feature creation, or that one particular, simple to implement feature, is important to a large number of the stakeholders, which previously was low down on the priority list.
For the best results this exercise should be performed regularly (perhaps once every quarter). Keep the exercise fun, and remember to create diverse teams to give people from different functional teams the opportunity to meet each other.
How to Close a Project Successfully
Communication in Project Management
Change Request Template
Project Management Soft Skills
Project Status Report Template
How to Start a Project
Project Plan Example – How to Plan a Project
The Project Scope Statement