There comes a time in every IT project when things don't go as planned.

If you're lucky, you can quickly and effortlessly get through these hurdles with proper planning and execution. In many cases though, it isn't that simple. Your team may get caught up in a tidal wave of confusion and turmoil as you try to make sense of all the information.

I've been the project manager on chaotic projects, and I've learned that communication is the key to having better control of the situation. Here are a few steps that you can take during the project, as well as a tip for how to prevent a future project from spinning out of control.

1:1 Communication

In many cases, increasing the level communication is one of the greatest areas of opportunity for a chaotic project team.

One-on-one meetings

If possible, spend time with each team member at least once a week in an effort to keep up to date on tasks and issues. These meetings are also a time to proactively communicate any changes as they occur.

Daily/weekly team updates

I find that getting everyone on the project team together on a regular basis helps keep team dynamics and priorities aligned. When things get hectic, I like to have a 15-minute meeting every morning to regroup on what occurred the prior day; we also ensure everyone is in sync about which tasks need to be completed that day. In addition, it's an open forum for the team to express any concerns they are feeling about the project or to reach out for help in a particular area if necessary.

Status reports

Project sponsors and the key stakeholder will likely be very interested to know what's going on, and they'll look to you for timely updates on your project's progress. While it's common to have a weekly check in during the course of the project, you may be asked for a daily update on key issues. Try coming up with a standard template they can follow that outlines any key performance indicators of the project, as well as any of the critical path items that will most likely impact your project. Daily status reports allow project sponsors and the key stakeholder to be in the loop on your progress without inundating them with all the details. These reports ensure that everyone is on the same page throughout the project.

Post mortem

When the project is finally over and you start to feel a tremendous weight being lifted off your shoulder, it's time to regroup with the team and review what went awry. Be careful that the process doesn't turn into a finger-pointing exercise as team members try to deflect blame. At this point, you should try to identify solutions to put in place so that future projects do not succumb to the same issues that you encountered.

Summary

When you need to manage a crisis, you also have to juggle the responsibility of keeping team members focused on the tasks at hand; if you don't, it is amazing how hectic things can get. If you take the time to focus on these key areas of communication during your project, it will help you "right the ship" in most storms and hopefully leave you in a better position for next time.

Additional resources about managing project chaos

|> Solid best practices can thwart tech project chaos
|> Managing chaos can turn negative into positive
|> Putting them away

Gameplan This was published in Gameplan, check every Wednesday for more stories

Related links

Leave a comment

You must read and type the 6 chars within 0..9 and A..F

* indicates mandatory fields.

Log in


Sign up | Forgot your password?

  • Staff Share a keyboard and mouse with Synergy

    Even in the era of virtualization, many IT pros (including myself) have a small army of computers sitting on, under, and around their desks. Read more »

    -- posted by Staff

  • Staff Android devs less than gruntled

    Yet more discouraging news on the Android front. Having hacked off its developer community by releasing updated SDKs to just a small group of chosen devs, Google has now given the brush-off to a petition that called for more to be given to the wider community. Read more »

    -- posted by Staff

  • Staff VMware shows how not to do it

    As a developer there will be a time when you ship a bug -- be it a stub that you left in, or a flaming, crashtastic segfault. The next time this happens and your bosses come baying for blood, point them in the direction of VMware, who this week gave the developer world a great example of how to ship a showstopper bug. Read more »

    -- posted by Staff

What's on?

  • Club Builder: Captain Obvious vs the Crackpots

    In the case of the bleeding obvious, IBM says open source needs good designers; a claim is made that China can activate your phone to snoop on you; and we take a look at the Defcon conference.