Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Practical Change Management for IT Projects
  • Table Of Contents Toc
  • Feedback & Rating feedback
Practical Change Management for IT Projects

Practical Change Management for IT Projects

By : Emily Carr
4.5 (8)
Buy this Book
close
close
Practical Change Management for IT Projects

Practical Change Management for IT Projects

4.5 (8)
By: Emily Carr
Buy this Book

Overview of this book

Table of Contents (12 chapters)
close
close
close
Practical Change Management for IT Projects
Icon
Practical Change Management for IT Projects
Credits
Icon
Credits
About the Author
Icon
About the Author
About the Reviewers
Icon
About the Reviewers
Preface
Icon
Preface
Lock Free Chapter
1
What is Change Management?
Icon
What is Change Management?
Icon
Exercise – defining success
Icon
The Pillars of Change
Icon
Why Change Management is important to project success
Icon
Change Management and the project team
Icon
Exercise – team integration
Icon
Exercise – supporting Change Management
Icon
Summary
2
Establishing the Framework for Change
Icon
Establishing the Framework for Change
Icon
Remembering the emotional side of change
Icon
Integrating beyond your project team
Icon
Organization design
Icon
Who is your Human Resources partner?
Icon
Are job descriptions going to change?
Icon
Exercise – updating job descriptions
Icon
Sample solution
Icon
Do you have the right number of people with the skills of the future?
Icon
How will your run team be structured?
Icon
What will your support organization look like?
Icon
Summary
3
Building Sponsorship for the Change
Icon
Building Sponsorship for the Change
Icon
Why do we need a change network?
Icon
Steering committee
Icon
Executive sponsors
Icon
Change Agents
Icon
Super users
Icon
A final note on sponsors
Icon
Summary
4
Managing Your Stakeholders
Icon
Managing Your Stakeholders
Icon
Conducting a stakeholder analysis
Icon
The change curve
Icon
Understanding the stages of change
Icon
Surviving the Valley of Despair
Icon
Conducting a change impact assessment
Icon
Including end users in the change process
Icon
Working with the project team
Icon
Summary
5
Communicating the Change
chevron up
Icon
Communicating the Change
Icon
The importance of two-way communication
Icon
Push versus pull communication
Icon
Breaking through the noise
Icon
Conducting an audience analysis
Icon
Conducting a vehicle analysis
Icon
Communication messages by project phase
Icon
Gathering feedback
Icon
Creating the communication plan
Icon
Writing good communication
Icon
Summary
6
Using Training to Prepare Your Stakeholders
Icon
Using Training to Prepare Your Stakeholders
Icon
The importance of training
Icon
Building knowledge through blended learning
Icon
Identifying your training audience
Icon
Gathering training input
Icon
Planning for training development
Icon
Planning for training delivery
Icon
Evaluating participants
Icon
Building continuous improvement into training
Icon
Developing a sustainable training program
Icon
Summary
7
Ready, Set, Change
Icon
Ready, Set, Change
Icon
Putting it all together – consolidating your templates
Icon
Top tips by chapter
Icon
Spreading the word about Change Management
Icon
Summary

Gathering feedback

As we discussed earlier, it is important for communication to be a two-way dialog between you and your audience. You can increase the chance that your stakeholders will communicate with you by purposely setting up feedback channels. Make sure these channels are easy for the audience to use and are monitored by someone on the project team on a regular basis.

Feedback methods

There are dozens of ways to gather feedback. Here are a few ideas to get you started.

Dedicated e-mail address

One of the first things I do when I join a project is set up a dedicated e-mail address (). I use this e-mail address to send official project communication. I also put this e-mail address at the bottom of every project communication and form, and ask people to use it for all questions and comments. This serves three purposes. First, by having a dedicated e-mail address, there is less chance that questions about the project will get lost among my other work e-mails...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Practical Change Management for IT Projects
End of Section 5
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon