Defining the scope of the project

Created on Wednesday, 18 January 2012

You have just been handed over a HMIS implementation project. Elated, you ask about the scope of the project. Mostly, you get a straight forward answer. But drill down to the details and sometimes people do not have a clue what will the project include (or does not include).

 

Srishti with a 100% implementation success record have been in situations like this. So, we asked our Project Managers for their insights on what to expect, how to prepare for the worst case scenarios and do’s and don’ts. The first gyan that comes from our senior project managers is define the scope of the project in the pre implementation phase. Spend more time discussing the details of the projects, get multiple expectations right before the start of project, prioritize the modules based on business requirements and as far as possible document these. Identifying the scope of the project includes defining:

Product specifications: Here, the client and the manger decide on the modules to be implemented according to the requirements, customizations, and other details. For instance, when we implemented in Prashant Memorial Charitable Hospital and Trust, we were told that the hospital needed assistance in better patient tracking and finance management. Our project managers studied their requirements and have implemented the relevant modules.

Project specifications: Under project specifications the client and the Vendor have to decide boundaries such as the project timeline, dependencies on the client, involvement of user champions, user training, and feedback. For instance, the project specifications and scope in RGCI was defined in advance for various modules. But based on our product readiness the scope was changed and we were asked to deliver the Lab and Blood Bank module. We implemented well within time at RGCI. This kind of opportunity can be foreseen in other Implementations as well.

Project Assumptions: The manager should also define what assumptions in advance before taking up the project to cover for any miscommunication that might happen in future. 

© 2015 Srishti Software Applications Pvt. Ltd.