This can be necessary for Agile Project Management as a result of once we have a look at large enterprise projects this is often most typically the reason for failure. We tend to have a stellar project manager, we tend to have a superstar team of developers, a highly astute cluster of business analysts, and a core team of wizard architects, yet the project was still seen as a failure. Why?
Because the foremost proficient project delivery team and the most refined whiz bang technology does not modification the fundamentals of human nature, and one among the fundamentals of human nature is that individuals are resistant to change. OCM may be a discipline that studies change in a corporation (easy, right.)
Let me state it again: Individuals hate change. When an engineer in 2010 appearance at the DOS program that Mary has been using for the last 15 years to enter orders, then sees her print out the manifest, take it to Bob, who pulls the order from the shelf, writes the date, time and release on a bit of paper, then takes it over to Ned who gets it prepared for shipping, he sees a Rube Goldberg machine that if properly digitized, optimized, and streamlined could unlock all kinds of price for an organization! Excelsior!
Not therefore quick Sparky. Mary is aware of how to try to to her job. Bob knows how to try to to his job, and Ned is aware of how to try to to his job. They need ingrained patterns of behavior that provide them a bound level of comfort with this system, warts and all. If you come in with a customized automatic digital sign-off and order routing system, the whole order to money ecosystem could terribly well come back to a screeching halt.
As Agile project managers and technologists, we cannot continue to appear at software development and packaged software implementations during a bubble. We would like to recognize that the cause of 'perceived' failure for many a project is the lack of understanding and respect for the way and why individuals are prompted to change.
I have checked out many technology project plans and have seen no provisions for guiding the organization through the amendment curve. Zero understanding or respect paid to coaching the users (what does one mean, I'm a UI GURU.... IT'S INTUITIVE!!!). Try telling that to Mary when she says, "It just does not work!" What she very means that is "It simply does not work FOR ME. I didn't get into the thought, I wasn't ready, I wasn't trained and dammit I don't like it!"
The subsequent time you're envisioning a project, do not simply think regarding the developers, DBAs, architects, testers, and business analysts. Suppose concerning a communication arrange (early and often). Think concerning how you'll be able to get govt leadership to require a visible role in enabling amendment in the organization. Assume about how you'll be able to expose the organization to the project progress, goals, and value. In brief, suppose regarding your customer.
Author Resource:-
Link :
Clara Brooks has been writing articles online for nearly 2 years now. Not only does this author specialize in Change Management, you can also check out his latest website about:
![[Valid RSS feed]](http://article2008.com/images/feed-icon.png "XML Feed For RSS"){kind=icon}
![[Valid RSS feed]](http://article2008.com/images/icon_Rss.png "XML Feed For RSS"){kind=icon}
Category Rss Feed
Print This Article
Add To Favorites