PPM 101: For Comparison’s Sake | ||||||||||||
 |
|
|
|
|
|
|
|
|
|
|
|
|
 |
||||||||||||
 |
[ Login/Subscribe ] | |||||||||||
 |
||||||||||||
 |
 |
 |
 |
 |
 |
 |
|
 |
||||
 |
||||||||||||
Features
Departments
Opinion
Executive
Resources
|
Home > Departments > PMO/EPM
When prioritizing a portfolio of projects and other IT activities, you can improve the decision-making process by grouping work requests from various department and categorizing them according to general business needs and benefits. Here are some basic guidelines.
Done right, project portfolio management can do a lot of good for any organization. But it’s not easy, as many companies, large and small, have discovered. In PPM 101, an ongoing series by veteran project management consultant and author Tom Mochal, we focus on the fundamentals for organizations that are just getting started on the PPM path.
When you are prioritizing the potential work requests in your portfolio, you first prepare a short Value Proposition. Many work requests will get postponed or cancelled once the weak Value Proposition is written. You then create a more detailed Business Case for the remaining work to describe the high-level costs and benefits of the work.
Let’s assume you are prioritizing the work of the IT portfolio and that many business units are requesting work from IT.
Please login/register to read the entire article.
| |||||||||||||||||
|
Privacy Policy Contact Us User Agreement