August 2009
Beginner
252 pages
6h 2m
English
Content preview from 97 Things Every Project Manager Should Know
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Chapter 39. Chart a Course for Change
NEW SOFTWARE CHANGES THE WAY IN WHICH PEOPLE WORK. This may be good for the organization, but the people who work there aren't always ready to embrace change. And let's face it, if people can't be convinced, cajoled, or commanded to use your new software, it's been a big waste of time and money.
When requiring people to change the ways in which they work, the carrot method (reward) is much better than the stick (punishment). Even if they're forced to adopt it, if your new software does not provide significant benefits that users can understand and master, they will find every way possible to avoid using it. Proper care must be taken to 1) understand the impact of this change on the people it touches, and 2) put in place change-management plans that help these people embrace the change.
Key to understanding the impact of the change is to understand how people currently work and exactly how the new software will change that process. This increases the chances that users will adopt the new system, and also improves the design of your end-product, as it ensures that it will fit user needs.
The importance of change management cannot be underestimated and should be a project manager's focus early on in the project. To determine the impact of the change on users, first document all current ("as is") processes that touch the software project. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.