A hybrid project plan combines project management methodologies. In this blog series, a hybrid project management plan is created using predictive and Agile methologies.
Table of Content
Project Methodologies
The strength of a predictive style project is its ability to control project cost by carefully planning out all project steps during project planning phase. By developing detailed work tasks, the project manager can then measure project progress and determine if the project is staying on budget and on time.
Projects that employ predictive methologies are typically creating a product that has been created before. For example, the steps to take to build a house are well defined and repeatable. Building permits must be obtained before equipment can start digging for the house foundation. The foundation must be poured and curred before the framing can be installed.
However, when building a product that has not been created before, project methologies such as Agile may be a better option. Agile’s strength is involvement of stakeholders early and often in the project execution phase. The software development’s objective is to deliver value to stakeholders, having stakeholders review incremental software improvements creates a collaborative relationship and improves the probability the project delivers value to the stakeholders.
When done well, combining aspects of both predictive and Agile methodologies can provide a project plan that has the cost control features of a predictive project when including the value delivery features of an Agile project.
Project Plan
The following is a summary of a hybrid project plan for Fashion Future, a victious company that want to develop a mobile application for its customers. The project plan uses three phases from predicative project methology: Project Charter, Integrated Project Plan (IPP), and Project or Phase closeout.
Agile is using during the execution and monitor and control phases. The mobile software development team will track feature requests in the Product Backlog. The team determines the sprint workload based on story points. Project retrospective will be held bi-weekly to engage stakeholders with mobile application changes and seek their input for future improvements and changes.
Documents
| Document | Link |
|---|---|
| Project Charter | https://blog.markormesher.ca/posts/project-charter/ |
| IPP | To be Determined |