I’ve been talking to a variety of potential clients about their project portfolios. One of the big problems is how to see all the work. Some of these folks have multiple kinds of projects, so they want to show their work in a variety of ways.
What do you do when you have a few big projects and a ton of small projects, such as several clients of mine have? I have an IT client and a couple of R&D clients with this problem. I’ll take an R&D client as an example.
They have big projects that they want to show in a calendar-like fashion so their management can see how the majority of their time is spent, just as in the image to the left. In this case, the project rank is implicit. And, they have many small projects that come into their group by email, by conversation, by randomness.
I suggested they need to visualize the work, so someone can rank the work. One of these clients is an engineering firm, who has a electrical engineering group, a software group, and a mechanical engineering group. We think a kanban board is a good first step, so this is what we set up.
This board would be great if they had someone to rank the backlog. They don’t right now. The people who keep asking R&D to do these small projects are all over the organization: Sales, Marketing, Support, Senior management, Training. There is no one person who is willing to take on the role of ranking the backlog.
These folks are not alone. The good news is that more and more people are coming to me, wanting help with their project portfolios. The bad news is that their organizations are not yet willing to make the strategic decisions about which projects to do and not do.
Visualizing the work is a necessary first step. Once you see that there is more work than an Engineering or R&D group can do, you see the need to make the decisions. Then you can ask the zeroth question, “Should we do this project all?” If the answer is yes, go ask the qualitative questions and quantitative questions.
If you don’t collect the work, you can’t see the work. If you can’t see the work, you can’t rank the work. You can’t make good project portfolio decisions if you don’t collect the work.
BTW, my participants at the workshop in Sao Paulo will be the first to hear everything about how to integrate the two kinds of boards, calendar and kanban in their organizations. I bet you wish you would be there…
Here is a promotion of the work I did last year that was all about visualizing the portfolio. (I may have taken the picture.)
http://pinnacle-strategies.com/blog/2012/08/visual-project-management/
Great post!
I find this time and time again to be a huge source of problems between the business and the development organization. Often the development organization becomes a whipping post and even allows itself to be put into this position by not pushing back and forcing the business to make portfolio decisions.
Visualizing the backlog is a huge first step to help the business realize it is their responsibility to negotiate and make trade offs, not the development organization. It is interesting to see the changes that happen once the business no longer throws things over the wall and have to make rational decisions about where to invest development capabilities.
And notice for all of you folks who want tools, that Jack and his folks started with stickies. Gotta start with stickies or cards, because that’s how you stimulate the discussions.
Pingback: Blog AdaptWorks » Blog Archive » Por que devo aprender Gestão de Portfólio com a Johanna Rothman?
Portfolio transparency (“what’s in it”) is really a key enabler for the organization to understand the amount of parallel work and the work queuing up. I’ve recently shown a Cumulative Flow Diagram of several of product lines with lead time analysis etc.
My experiences on what I call “Business Kanban” apply Kanban method to the fullest on business-level and it has been suprising how fitting the concept is on more abstract level of work.
More about it here on my blog:
http://improvementstory.net/2012/08/25/business-kanban/
I totally agree that visualization is a way to go when it comes to project portfolio. It seems a natural next step to adopt kanban board to deal with project portfolio. However, it becomes more and more tricky, as projects have different mechanics than work items — they aren’t updated that often, it is difficult to name specific stages, etc.
I actually documented my story with project portfolio kanban here (http://blog.brodzinski.com/2011/11/project-portfolio-kanban.html). It includes a standard kanban board design and goes further — to a complete redesign of the board.
Pawel, in _Manage Your Project Portfolio_, I discuss how to do this for projects, not just for the small projects that drive people crazy. My experience is still that many organizations need a calendar view of expected project duration, even if that is total fiction.