Using change management to scope my project

I continue to write the new book on how project management needs to take the lead in managing change if projects are ever to realise their benefits. This week I am putting together a series of Mini Workshop Guides to help project managers address the key issues of change management including:

1. Understanding the context for the change i.e. seeing the bigger picture by asking how the change will contribute to strategic objectives, who is driving the change that the project will support, who are the likely winners and losers from these changes, how time sensitive is the delivery of the benefits from the change

2. Understanding the detailed changes that the project is supposed to bring about including changes to information used for a process, the process itself, the outputs including information used for the next process, the decisions that need to be taken, the reports that are produced etc, changes in the size and make up of the teams involved in the process, changes in the level of authority and reporting line for each team member

3. Understanding the communication that is required to ensure everyone is informed about the proposed changes and has a chance to comment on them and engage with them prior to the changes taking place

I am interested in how these 3 areas fit with the scoping and the requirements gathering that project managers are responsible for at the start of the programme, but also how this information needs to be reviewed and updated as the project progresses and how this can lead to requests for change.

What are the most important questions you ask before getting started on a project – do you ask about the bigger picture, do you get to know the winners and the likely losers before you plan the project? As ever, all comments and emails welcome.