Leadership optimize

10 tips for meeting IT project deadlines


Erratic and poorly estimated timelines, scope creep, unexpected staff illnesses, and supplier failures are just a few of the things that could (and probably will) go wrong with your project. And because time is today the most common metric to measure efficiency, the schedule delays caused by these events can end up costing you a fair amount of money (in addition to a possible damaged reputation). Here are some tips to help you plan your next project and ensure that it comes in on time, under budget, and at a high quality level.

Note: This information, which is based on the article "Take proactive measures with these ten tips for meeting IT project deadlines," is also available as a PDF download.

#1: Analyze the requirements in detail

Understand exactly what the project involves, down to the smallest details. Ask questions to clarify ambiguous areas. Finally, hire professionals to clearly document the business requirements, the functional specification, and the design requirements. Watch out for scope creep; it can single-handedly destroy all the work you've done. If the need arises, take aggressive steps to reduce the scope of the project or to avoid adding unplanned new features that require significant integration time.

#2: Map available resources

Map available resources with requirements to ensure that there are enough personnel on site to complete the job. Identify all relevant infrastructure -- hardware, software, human resources, tools, documents -- required to execute the project well before the project development starts.

#3: Perform training and knowledge transfer

Include training, if any, as part of the project timeline. Don't treat training as something team members do on their own time, but account for it in the project schedule and budget.

#4: Identify risks

Identify the potential risks and create contingency plans to deal with them. Develop a backup plan to meet the project deadline in case of unexpected process or personnel failures. This "plan B" acts are your support system when things don't go as expected.

#5: Estimate and allocate

Assign roles and responsibilities to team members and ensure that each task has a clear owner. Use project management tools and Gantt charts to record who does what and identify start and end dates for each activity. Failure to assign clear responsibilities for each task can lead to overlapping responsibilities, duplication of efforts, excessive time spent on activities, and inferior product quality.

#6: Modularize work

Break down main activities into sub-activities, until each activity is complete on its own and independent of other activities. Arrange them in logical order and then start executing the smallest activity in the order of occurrence.

#7: Avoid too many meetings

Plan meetings to discuss the status of the project or on an as-needed basis to address immediate problems. Long, unending meetings with no clear agenda and hence no clear outcome only waste time.

#8: Write things down

Document the failures and successes of the project. This is important; it acts as historical information for similar activities in other projects. Use a project dashboard to obtain a visual, high-level overview of the project and to measure the progress of project activities. Take stock of the project at each milestone and update the project dashboard each time.

#9: Beware of follow-the-sun development

If there is a follow-the-sun development model (a continuous engineering environment with development happening 24/7 across the globe), ensure clear communications to avoid misunderstanding between co-located or cross-country-located team members. Coordinate well and regularly so that nothing falls through the cracks.

#10: Escalate issues

Escalate issues to management as they occur and brainstorm on solutions to problems. Trying to remedy problems after they've deteriorated beyond recovery is the last thing you need.

2 comments
Tony Hopkinson
Tony Hopkinson

1. Establish when it has to be done for 2. Guess what is required. 3. Estimate how long it will take. 4. Throw hands up in air. 5. Abandon all hope of quality. 6. Use up plenty of time delaying starting, whining about 1 - 5. 7. Change your mind on what several times, preferably after it's been started. So you can procrastinate about how. 8. Do lots of reports to show control 9. Fail again. 10. Blame somebody else. No project plan survives contact with reality. My experience of Project Management. I loved number 1 by the way, we don't have that here on earth.

rand.wrobel
rand.wrobel

As far as a quick Top 10 List for meeting project deadlines, its a reasonable list, except for #1: "Analyze Requirements in Detail": Yeah, if you are doing a waterfall-style project AND have the luxury of setting your deadline AFTER you have "Analyzed the Req's in Detail". Requirements gathering can be a significant fraction of the project timeline, and in some cases spin out of control itself. That's why the waterfall approach is being superceded by more rapid and flexible approaches where the detailed requirements are refined during prototyping and even development. Such approaches do introduce additional risk, and management should be prepared to truncate requirements and balance timeliness with functionality.