Shoumik KahaliTechnical Manager| Yash TechnologiesIndore, M.P., India
During project selection|identification phase it is said that the project must align to the organizations goals and strategies.
Is there any process|practice|technique available where we can validate the project objectives along with the organizational goals and strategies? Saving Changes...
How are projects raised? For every idea proposed as a project, or within every business case for a new project, including a section on how the proposed change is expected to support organisational strategy and objectives can be a quick way to get early sight of this. Going forward, once the proposed project benefits have been deemed to support the organisation, then everything that takes place on the project just needs to track back to the project objectives as their link to the organisational goals has already been validated. Our team currently use a tool to capture these objectives and then link all high level requirements back to them. This "traceability" is then maintained throughout the rest of the project lifecycle. Saving Changes...
BUBU TRIPATHYPM I| Siemens Healthcare Inc. USAFrazer, Pa, United States
There are standard techniques for project selection such as Benefit measurement methods, Murder board, Peer review, Scoring models, Economic models, Benefit compared to Cost etc. However in many organizations, there are standard checklists and quality gates which lead to "Go/No Go" decisions during project acquisition.
A sample checklist is as below:
- Is the value proposition that we want to communicate to the customer in line with our strategy?
- Do we have sufficient know-how available concerning the customer's industry sector to be able to consult the customer ?
- Has our competitive positioning been clarified and are we able to estimate the likelihood of our success?
- Is the service/solution we want to offer based on our standard portfolio?
- Can we fulfill the customer‘s requirements by offering our standard
portfolio (portfolio fit)?
- How much customization to our standard offering would be needed to address the customer's requirements ? Saving Changes...
I would like to know who the "we" are in your question? It should be the executives that determine whether a project is strategically aligned as they are the ones responsible for the corporate strategy.
There are basically three types of project;
1 Strategic - needed to progress the Strategic Plan
2 Tactical - needed to address immediate business requirement ie response to changing market conditions, fix failed infrastructure, annual software upgrade etc
3 Externally mandated - usually a project to ensure compliance with new legislation, industry standards etc.
If the project is strategic then the executive responsible for the element in the corporate strategy has already indicated that this is a strategic project.
For tactical projects then the exec responsible for the business area must ensure that projects are aligned with corporate strategy or at least not counter to it.
... and mandatory, well the just have to happen but again how they are implemented must be within the corporate framework.
So the "we" in your question really needs to be the executives of the organisation who are responsible for the strategic plan. Saving Changes...
