Ten anonymous contributors
- Projects are run ad hoc with little to no standards.
- Lack of proper scoping at the beginning of the project leads to constant rescoping, rescheduling, and budget overruns.
- Project leads track progress in their own way, which makes it difficult for leadership to understand project process and identify what projects require assistance.
- Absent documentation means project leads are left to reinvent the wheel every time a new project is assigned.
- Unable to pinpoint the ultimate decision maker, the project lead works unnecessarily to meet everchanging expectations.
- Do not burden project managers with things they do not have time to do.
- Determine what a sustainable process means for your organization.
- Most formal project management methodologies are too comprehensive and rigorous for most IT projects.
- Make the most of your project manager’s time, and be judicious about the standard that is set.
Impact and Result
Start with the project management foundation and grow from there!
- Formalize what you are doing.
- Get specific about requirements.
- Keep stakeholders up to date.
- Tightly control changes.
- Learn from your mistakes.
- Define when the project is done.
This guided implementation is a nine call advisory process.
Guided Implementation #1 - Scoping
Call #1 - Scope requirements, objectives, and your specific challenges.
Guided Implementation #2 - Project Initiation and Planning
Call #1 - Introduce the best practice toolkit.
Call #2 - Assess the current project initiation and planning practices.
Call #3 - Review the Project Charter and Requirements Workbook for suitability.
Guided Implementation #3 - Project Execution
Call #1 - Discuss pain points with project execution.
Call #2 - Review the Status Report and Change Request templates and discuss customization.
Guided Implementation #4 - Project Closure