Let’s talk shop about top-down project management. Khwaja Moinuddin writing for Scrum Alliance explains why high level conceptualization of a series of projects (a program or megaproject) is necessary for proper governance and risk management. Below we’ll run through the common phases of the project that transcend the individual methodologies listed in bullet points.
- Lean Principles
Common PM Phases
- Change Management
- Project Input
- Project Output
- Project Closure
To Run DMAIC is Tricky?
1. The common thread that unites all project initiation phases is the voice of the customer, or VOC, wherein customer needs are transformed to products, improvements, or requirements that can be measured and delivered in a given time frame. This phase also partakes in strategic documentation, or initiation documentation to kick off the project.
2. Immediately, one must recognize the human element of the project as well. This aspect of helping employees and stakeholders adjust must be maintained throughout the project.
3. At the end of each input phase, a go or no-go decision is made to justify further progress or to cancel a project that lacks merit. This is the point at which barriers to project implementation will emerge to make or break the project. For instance, in DMAIC this is known as a “tollgate review.”
4. Depending on which project methodology you’re running, the project output phase will involve some form of measurement or analysis to define whether criteria have been met, work packages are being delivered, tools and phases are being improved upon, hypothesis testing, regression…you get the point.
5. The closing phase is highly contingent upon which project method you’re using. Some common tasks at this leg of the journey include finalized documentation, calculated savings, system or structural changes, client sign-off, and disbursement of certifications or rewards.
To read the full post, visit: https://www.scrumalliance.org/community/articles/2014/august/linking-project-management-methods-frameworks