Tips for creating software project plans

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Software Project Management Advice on how to enter the software technology field Differentiating between Functional and Nonfunctional Requirements Where does quality assurance fit in agile development? Quality standards don't always mean fewer defects How to present a project to the management Project management charts: Beyond Gantt How to switch your team to Agile How to deal with a difficult team member Collaboration and communication tools for virtual meetings Project management: How to compose a project team Software project management methods and approaches Tasktop brings task management into the application lifecycle Software expert on Agile's rise, avoiding project management mistakes Ways software project managers can cope with recessionary trends James Bach interview: Dispelling software testing myths How to improve software project requirements estimates tutorial The QA team's role in application performance evaluation and management 5 ways to answer executives' unfair software test, QA questions Adaptation in project management through agile Expert shows seven ways to improve your project management abilities Accelerating businesses with agile development

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary collaboration diagram  (SearchSoftwareQuality.com) Gantt chart  (SearchSoftwareQuality.com) PERT chart  (SearchSoftwareQuality.com) rapid application development  (SearchSoftwareQuality.com) Software Process Improvement and Capability dEtermination  (SearchSoftwareQuality.com) work breakdown structure  (SearchSoftwareQuality.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

I sometimes think of planning and not moving as the same thing, at least if you stop moving in order to plan. I prefer to plan on my feet -- get things rolling, evaluate direction and adjust. Then roll along for a while and do it over, and keep repeating until the project is complete.

Does this approach make you nervous? I know firsthand it makes many managers nervous. They want to see a project plan from beginning to end, even if the plan you're showing them is based primarily on your imagination. Somehow the project plan that shows the whole road from initiation to close out just makes them feel warm and fuzzy inside. Not me. When I look down a project plan to the "horizon," I can almost see the probability of missing dates increasing the further out they are, like mountains rising over the desert in the distance. It's just too complicated.

Here's the simple truth about managing software projects: The probability of missing a date grows exponentially the further out the date is. Why? Because of all the factors that cause variability in a software project. The longer you are exposed to them, the more they accumulate.

So how can you deal with this? The answer is pretty simple: Don't build monolithic plans. Adjust the level of detail based on how far out you're looking. You should always have a very detailed plan for the next two to three weeks. It's a very reasonable thing to know exactly what's going to be done in that sort of timeframe. That's the range where you can make reasonable predictions about what will take place.

Activities that are more than three weeks out but fewer than three months away should be planned in a general sort of way and should seem more like goals. "Start UAT the week of August 1," for example, is one that you can shoot for. Pin it down to a more accurate date once it falls in the three-week range. Don't break it down into a detailed task list though, at least not until it comes close to the three-week window.

Anything more than three months away should have an extremely general timeframe with a fairly broad range associated with it (like "Go live sometime in October." I prefer to avoid putting dates on these at all; it makes more sense to me to just list them in the order we're going to do them and then get there as fast as we can. That is almost always impossible though, so give it a broad range instead. Once these activities fall in the three-month window, you should start to plan them.