The PM Process is modelled on SCRUM – an agile software development methodology. It is adopted when the client is not very clear on the requirements for the project. The probability of changes in requirements is very high and hence the PM process is best suited for small to medium sized projects.
Process
Project Planning
A product backlog pertaining to the project is created during this phase. Features requiring the highest priority are selected for Sprint 1. During the planning session, the details of the Sprint 1 are laid out and estimates prepared accordingly. The interval between each Sprint is specified and the project gets underway.
Development
In the development process, the designing and coding for the features listed in Sprint 1 begins. The progress of development and issues that arise during it are discussed daily. The problems faced are flagged earlier on and appropriate changes are made in the scope and schedule. Re-estimation of the project is also done if required.
Sprint
The Sprint which is the interval required to deliver a working part of the system is tracked and managed with respect to the daily meetings. At the end of each Sprint, a working model of the project is demonstrated to the client. New features and suggestions from the client are incorporated into the product backlog. Accordingly, the features for next Sprint are prioritized and its schedule planned.
Project Closure
When all the features mentioned in the product backlog are implemented and each feature demonstrated to the client, the project is considered for deployment and closure. Maintenance activities and version upgrades are carried out when deemed required. |
