Ads by TechWords

See your link here
Receive the latest technology news and information.
IT Management
Computerworld Daily News (First Look and Wrap-Up)
Computerworld Blogs Newsletter
The Weekly Top 10
Cloud Computing
View all newsletters




Privacy Policy
 

Get ready, get set, go! Getting to the project finish line

April 15, 2009 12:00 PM ET

Computerworld - Every race to the finish line begins with similar instructions: “Get ready, get set, go!” Every race, that is, except the race to the deadline assigned at work. In business, the starting gun is sometimes shot without any heads up ("get ready" or any project planning ("get set"). People seem to run with it, but not successfully.

But if you take just an hour out of your schedule to "get ready" and "set," you'll get to the finish line faster and without stumbling. Before starting a project, you must first gather all of the information so you can assess what needs to take place.

Outlining deliverables and acceptance criteria

First, you must identify the high-level deliverable for each main subset of the project. A deliverable is something concrete (defined by a noun) that you need in order to progress to the next stage of the project.

You must also deliver the acceptance criteria. These are the measurable characteristics of what makes the final and interim deliverable acceptable. This is often defined by what the client is expecting. If you don't know the answers, then you need to ask more questions and learn more about the goal of your project.

There are two approaches you can take when defining the interim deliverables. These steps are a means of discovery and discussion for the project team. The team learns more from each other by laying out the project this way than if one person creates the whole thing and then shares it with other team members.

If you know the high-level breakout of deliverables to create your final deliverable, then use the Top-Down Deliverables and Acceptance Criteria. This means beginning with the ultimate output of the project and then working down into the details of the project to see how they will create that output.

If you are unsure, then try the Bottom-Up Deliverables and Acceptance Criteria technique. This begins by brainstorming and identifying all the aspects of the project that must be completed in order to create the final deliverable. These aspects are then grouped into logical order to create the final deliverable. This approach can be spearheaded by the team leader through a technique called affinity diagramming.

With your team, group the related items near each other. Try to create no more than five main groups. This should take your team about five to 15 minutes. If you think an item belongs in more than one group, make a note of it. Develop titles for your groups, and then break them out into subgroups (also with titles). Now you can see your high-level deliverables, your interim deliverables and your acceptance criteria. Next, identify who will be responsible for each high-level deliverable.



Jump to comments

deliverables

Additional Resources

Xerox
By using solid ink technology only from Xerox, you could save up to 65% by printing color for the cost of black and white. Enter for a chance to WIN a PhaserTM 8860 network color printer!
Microsoft
Save time and mitigate security risk. Deploy it now.
Sybase
In this white paper, IDC analyzes the role of next-generation mobile enterprise platforms as organizations seek a more strategic deployment of mobile solutions.

Learn the important issues you must consider before starting your next mobility initiative. Get your mobility white paper from IDC now, compliments of Sybase.

What People Are Saying

 

Putting the Right Model in Place to Better Balance IT Supply and Business Demand
IT leaders manage business demands and IT resources in many ways, but which methods are most effective? Tom Welsh, senior consultant of Cutter Consortium, compares two approaches and outlines their pros and cons in this Compuware-commissioned white paper. Get objective appraisals and real-world examples for both.

Download this white paper 
CIO best practices: Optimizing your Project Portfolio Management solution for greater business value
A Project Portfolio Management discipline goes beyond ordinary project management to link IT with the business and help IT leaders better understand the benefits, cost, risks and value of all projects. Download this Compuware white paper and learn how to boost the business value of your IT organization.

Download this white paper 
Exclusive eBook: Six Project Metrics Every CIO Should Know for Application Delivery Success
Most IT organizations spend their time measuring whether projects are on time or on budget. Read this IT executive guide to learn what key data tells you the degree of quality, client satisfaction and how well requirements were met. Make these metrics part of your overall application delivery management process - and your software can't fail.

Download this eBook 
IT Planning and Control: Unveiling the Interrelationships between ALM and PPM
Listen in as Gartner Analyst Matt Light discusses two hot topics-- Project Portfolio Management and Application Life-cycle Management--and how you can bring these disciplines together to improve application quality and delivery. Get recommendations on merging the two methods and learn what type of results you can expect.

Download this podcast