Agile Portfolio Management can be that change agent we are looking for making the organisational transformation towards agile!
Do your organization make frequent project portfolio decisions based conformance to schedule and budget rather than value based decisions?
Project are blessed with a product backlog which we prioritized, but is the company portfolio divided into “small” independed projects (epics) and put onto a company backlog prioritized? Not in many companies, why not? Because it demands a change on the organisational way of thinking! Well this change can be the catalyze for transforming the organisation into a agile focused organisation.
At e-conomic we did have a portfolio backlog which was re-prioritized every 14 days by the Top Management of the company. This is an easy and extremely effective way to implement the organisational change from the traditional way of thinking in companies to a more agile organisation that support the rapid changes and demands from the customers.
Some basic rules must be established
- No project could be more that 3 months
- A project has a team with max 5 developer and 2 other roles on the team which define the size of 3 months projects.
- Criteria for priority has to be clear and transparent (and communicated)
- It’s important to have some common metrics of each item on the backlog like expected cost, ROI, dependencies, window of opportunities, where the item is in the workflow like is it being prototype ready for feedback soon? This data is placed nicely in a data sheet so it’s easy to view.
Please write comments or thought regarding
Agile Portfolio Management.