My organization is going through a transition period and we really need to figure out how to better rate projects upon request for acceptance. We recently have been accepting all projects and rating them after the fact, which has led to many PMs and resources feeling overwhelmed. Does anybody have a good template for how you rate a project on request you can share with me? Saving Changes...
Sort By:
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Each request for a project should have an associated and approved business case and justification. Along with that would be a priority based on value return to the organization or cost of delay, etc. Additionally, with regards to the capability, platform, etc. for the implementation, an open dialogue with the big three; Enterprise Architecture, Risk & Compliance, and Vendor Management to ensure the chosen path forward fits within the organizations model, environment and is sustainable and scalable for the long-term.
The difficult part to this is that everyone needs it now, is in a hurry, or doesn't want the overhead of going through the right channels/process or the vetting process. It's important to place decisions with the right groups/people; that there is clear chain of events on the path for beginning the effort. Saving Changes...
This is less about a template or scoring model and more about the behavior of those making & those evaluating requests. If the behaviors won't change, the scoring model won't help. One way to get there is to ensure there is transparency into available capacity as well as what folks are working on. Without that, there's an implicit assumption of infinite capacity...
