Scope
• Does project scope indicate boundaries among impacted processes, systems, and organizations?
• Is project scope defined clearly enough to show when scope creep is occurring?
• Have any external process or system interfaces that will be impacted by this project been identified?
• Has the process workflow between business units or business functions been properly considered?
• Have the organizational and geographic boundaries been clearly defined?
• Does project scope include related items that are out of scope?
• Does project scope include any other organizational or technology-based initiative that is needed to fully support the project objective?
• If project scope includes any requirements, have the requirements been properly validated?
• Have any and all project constraints been identified?
• Have any and all project assumptions been identified?
• Are there any known policies, regulations, or standards that apply to this project (such as procurement, quality, security, regulatory compliance, and so on)?
Stakeholders
• Has the project sponsor been identified and engaged?
• Is each affected business unit and business process step represented on the project team?
• Is each customer group represented on the project team?
• Are all stakeholders identified in a project organization chart?
• Are the reporting relationships indicated in the project organization chart?
• Are project roles described and assigned to each stakeholder?
• Have we identified which stakeholders form the core management steering committee?
• Have you identified which stakeholders need to review and approve any requested changes to the project definition?
Project Approach
• Does the recommended approach explain why it is selected over the alternatives?
• Are the proposed technologies, strategies, and methodologies documented?
Other
• Are the project definition elements documented?
• Is the Project Definition document under configuration management (version control)?
• Have high-level risks and planned responses been identified?
• Have the preliminary timeline and budget been stated? Are the supporting reasons and assumptions documented?
Acceptance
• Have all stakeholders reviewed, agreed upon, and approved the Project Definition document?
• Have the project and the project manager been officially authorized?
As with all project documents, make sure you have a way to control changes to the Project Definition document and that you have proper backups of it.
• Does project scope indicate boundaries among impacted processes, systems, and organizations?
• Is project scope defined clearly enough to show when scope creep is occurring?
• Have any external process or system interfaces that will be impacted by this project been identified?
• Has the process workflow between business units or business functions been properly considered?
• Have the organizational and geographic boundaries been clearly defined?
• Does project scope include related items that are out of scope?
• Does project scope include any other organizational or technology-based initiative that is needed to fully support the project objective?
• If project scope includes any requirements, have the requirements been properly validated?
• Have any and all project constraints been identified?
• Have any and all project assumptions been identified?
• Are there any known policies, regulations, or standards that apply to this project (such as procurement, quality, security, regulatory compliance, and so on)?
Stakeholders
• Has the project sponsor been identified and engaged?
• Is each affected business unit and business process step represented on the project team?
• Is each customer group represented on the project team?
• Are all stakeholders identified in a project organization chart?
• Are the reporting relationships indicated in the project organization chart?
• Are project roles described and assigned to each stakeholder?
• Have we identified which stakeholders form the core management steering committee?
• Have you identified which stakeholders need to review and approve any requested changes to the project definition?
Project Approach
• Does the recommended approach explain why it is selected over the alternatives?
• Are the proposed technologies, strategies, and methodologies documented?
Other
• Are the project definition elements documented?
• Is the Project Definition document under configuration management (version control)?
• Have high-level risks and planned responses been identified?
• Have the preliminary timeline and budget been stated? Are the supporting reasons and assumptions documented?
Acceptance
• Have all stakeholders reviewed, agreed upon, and approved the Project Definition document?
• Have the project and the project manager been officially authorized?
As with all project documents, make sure you have a way to control changes to the Project Definition document and that you have proper backups of it.
No comments:
Post a Comment