“How to manage Changes to Project Scope ?” The most common question asked by PM and Clients.

Change to the Project Scope is one of the most common issues at entire IT development industry. In spite of many standard

Change to the Project Scope is one of the most common issues at entire IT development industry. In spite of many standard methodology of project execution like Agile or

Change to the Project Scope is one of the most common issues at entire IT development industry. In spite of many standard methodology of project execution like Agile or Water fall model, Change to the Project Scope make entire flow disturbed with many uncertain issues.

Change to the Project Scope is one of the most common issues at entire IT development industry. In spite of many standard methodology of project execution like Agile or Water fall model, Change to the Project Scope make entire flow disturbed with many uncertain issues.

During the life cycle of project development, “changes to the project scope” affects internal as well external projects due to resource allocation issue. There are six main sources which affect the project scope.
Before we think upon how we should manage the changes to project scope, we need to know what possible key changes to Project Scope are.

Possible key changes to Project Scope:

A. Scope creep: Any change in project scope from client’s end or development’s end will be count as scope creep. For example client says now I want the entire site to be designed in wordpress instead of joomla due to user-friendly CMS. Then it’s called scope creep.

B. Staff changes: Change in staff from bottom to top level effect the project, As before starting the project every system hierarchy get understanding of client’s vision, concept and process flow for strategic execution. For example: If any of the project leader or project manager replaced due to other deadline urgency, then team will take some time to get adjust with resource, and project leader also take some time to get grass rout understanding for the client requirements.

C. Schedule changes: Schedule change has maximum impact on your resource balance. This part will be very hard to balance if it changes negatively by shorten the span of delivery. For example, If client decrease his deadline of delivery on e- commerce website due to Christmas festival. Then the team has to define action plan to manage this project with other pipeline and current projects.

D. Requested changes to project deliverable: As per SDLC life cycle, project delivery has different milestones base upon project type, coding structure and modules to install and integrate. Now if the deliverable get changed due to change to project scope then it will be one of the major road blocks for the project execution. For example, Client want to have beta release with core modules by 5th milestone of project, then PM and BA need to restructure the delivery milestones base upon change in project scope.

E. Changes to materials or technology: Change in technology is very painful for an IT company as they already invested time and efforts toward execution of the project with one technology. Now change in it means they need to start entire project from scratch again. For example, after designing static website client says, I want to have customized CMS to upload contents. Then entire site need to restart apart of HTML template of design.

F. Changes to policies and processes: This factor affect big size companies where policies use to be implemented on mass bases. If policy change affects working hours or work modules then project get procrastinated by this. Most common policy changes are as under:

– Change in Shift timings
– Change in holiday or leave calendar
– Change in daily schedule due to Training program
– Change in documentation due to ISO or CMM certification ETC.

….

Once you identify about the key changes at project after any or some of above characteristics, you can start working on how to improve the situation of changes in project scope. These are seven key steps, which need to be taken to execute project or balance project deliverable. [ View Image ]

Here are seven key steps to manage or Balance the change in project scope:

Step 1. Identify from the source about type and nature of the change:
Step 2. Analyze total impacts to the project resulting from the change
Step 3. Develop a response or action plan (strategy building)
Step 4. Get approval from project stakeholders to implement the change management strategy
Step 5. Implement the change plan with the core team
Step 6. Monitor the effects of change and result base approach
Step 7. Revise and adjust the plan for executing those changes

By these seven steps you can face and enhance entire project execution and also balance the resource allocation once you identify the amount of change in to the project scope.

Success,
Vision Raval