Project Manager PlanetIT Project Management Tools, Techniques and Tips Earthweb
Events Premium Services Media Kit Network Map E-mail Offers Vendor Solutions Webcasts
 SUBJECTS:
IT Management Webcasts:
The Role of Security in IT Service Management

Preparing for an IT Audit

More Webcasts


Search EarthWeb Network

internet.commerce
Be a Commerce Partner














ProjectManagerPlanet : Project Management Leadership: Don’t Do It All At Once




Related Articles
ITtoolbox
Association for Project Management
10 Warning Signs of Project Failure
Project Management for Big and Small
XML/RSS feeds

EarthWeb IT Management news and headlines
ITSM Watch headlines
See more EarthWeb Network RSS feeds
Datamation Definitions
data mining
ERP
extranet
grid computing
intranet
network appliance
outsourcing
storage
VPN
virus
FREE Tech Newsletters

Don’t Do It All At Once
July 25, 2007
By George Spafford

Good things come in small packages and small steps lead to larger successes, writes PM Planet columnist George Spafford of Pepperweed Consulting.

Some groups propose “big bang” projects where they try to change the world in one fell swoop. It comes along like a siren song: "Do this and all will be fixed." Groups looking at the IT Infrastructure Library often here this song and dangerously steer towards hidden rocks. Rather than risk all, teams need to take a step back and consider a phased implementation that aligns with the needs of the business.

The challenge management from a long-term, expensive project is the level of risk. This is both due to the amount of money required and the amount of time required before benefits are seen. As a result, some projects may not be approved.

A large process improvement project that is expected to take years to complete and cost millions of dollars will be viewed by many management teams as very risky because of the time, cost and potential risk of not attaining any real benefits. Even with a good business case, management must weigh investing much needed money and time on this project vs. other projects that may seem more likely to deliver the expected benefits in a shorter period of time.

A different approach is to break large projects into incremental phases that are discrete building blocks of investments, activities and deliverables. Take a large project and split it up so the first phase lays the initial foundation. Then the second phase builds on that and so on. In a sense, the large original project can be viewed as a program comprised of a number of smaller related projects that when combined will achieve the original objective(s).

By doing this, there is one vision ranging from inception to end state. It also reduces costs of each phase. Also, if the benefits do not prove out or corrections are needed then they can be made prior to the next project being finalized and funded.

Building on our earlier process improvement example, imagine that instead of trying to propose everything in one fell swoop the project sponsor keeps the large project definition as a roadmap to explain what needs to be done and why at a high level. Then, he or she identifies processes based on enabling and/or protecting organizational goals by selecting those most needed first, taking any dependencies into account of course.

The result can be a phased approach where each project has a focused scope, a relatively smaller budget and benefits can then be monitored at the end of each before moving ahead. This presents a much more palatable option for management as the expenditures are lower and if the concept doesn’t prove itself then the effort can be aborted by not approving the next project.

Go to page: 1  2  Next  

Tools:
Add www.projectmanagerplanet.com to your favorites
Add www.projectmanagerplanet.com to your browser search box
IE 7 | Firefox 2.0 | Firefox 1.5.x
Receive news via our XML/RSS feed

Project Management Leadership Archives

Back to Home