Assignment: Prioritizing Projects at D. D. Williamson (Case Study from Chapter 2)
Read the case titled: "Prioritizing Projects at D. D. Williamson" found in Chapter 2.
Write a six to eight page paper in which you:
• Analyze the prioritizing process at D. D. Williamson.
• Suggest two recommendations to improve the prioritizing process.
• Create a scenario where the implemented process at D. D. Williamson would not work.
• Project five years ahead and speculate whether or not D. D. Williamson will be using the same process. Justify your answer.
• Use at least four quality (peer-reviewed) resources in this assignment.
PROJECT MANAGEMENT IN ACTION: Prioritizing Projects at D. D. Williamson
One of the most difficult, yet most important, lessons we have learned at D. D. Williamson surrounds project prioritization. We took three years and two iterations of our prioritization process to finally settle on an approach that dramatically increased our success rate on critical projects (now called VIPs, or "Vision Impact Projects").
Knowing that one of the keys to project management success is key management support, our first approach at prioritization was a process where our entire senior management team worked through a set of criteria and resource estimations to select a maximum of two projects per senior management sponsor-16 projects in total. Additionally, we hired a continuous improvement manager to serve as both our project office and a key resource for project facilitation. This was a great move forward (the year before we had been attempting to monitor well over 60 continuous improvement projects of varying importance). Our success rate improved to over 60 percent of projects finishing close to the expected dates, financial investment, and results.
What was the problem? The projects that were not moving forward tended to be the most critical-the heavy-investment "game changing" projects. A review of our results the next year determined we left significant money in opportunity "on the table" with projects that were behind and over budget!
This diagnosis led us to seek an additional process change. While the criteria rating was sound, the number of projects for a company our size was still too many to track robustly at a senior level and have resources to push for completion. Hence, we elevated a subset of projects to highest status-our "VIPs." We simplified the criteria ratings-rating projects on the level of expected impact on corporate objectives, the cross-functional nature of the team, and the perceived likelihood that the project would encounter barriers which required senior level support to overcome.
The results? Much better success rates on the big projects, such as design and implementation of new equipment and expansion plans into new markets. But why?
The Global Operating Team (GOT) now has laser focus on the five VIPs, reviewing the project plans progress and next steps with our continuous improvement manager in every weekly meeting. If a project is going off plan, we see it quickly and can move to reallocate resources, provide negotiation help, or change priorities within and outside the organization to manage it back on track. Certainly, the unanticipated barriers still occur, but we can put the strength of the entire team toward removing them as soon as they happen.
A couple of fun side benefits-it is now a development opportunity for project managers to take on a VIP. With only four to six projects on the docket, they come with tremendous senior management interaction and focus. Additionally, we have moved our prioritization process into our functional groups, using matrices with criteria and resource estimations to prioritize customer and R&D projects with our sales, marketing, and science and innovation teams, as well as IT projects throughout the company. The prioritization process has become a foundation of our cross-functional success!
Following are excerpts from the spreadsheet D. D. Williamson used to select and prioritize our VIP projects last year. Exhibit 2.16 shows the five criteria used to prioritize the projects. Exhibit 2.17 shows how associate time when assigned to a project is not available for other projects. Note all executives agreed to spend up to 120 hours this quarter on projects and Brian is overallocated-meaning either he will need to do extra work, something needs to be assigned to another person, or one less project can be completed.
Attachment:- EXHIBITS.rar