We’ve all seen (or heard of) projects that take 50% of the expected time to develop detailed plans and strategies then attempt to force fit the remaining 50% of the planned time into an implementation cycle that should probably have been allocated 150% more time for development.  The project plan is simply the start of a complex process, but not an isolated or an end goal in itself.  Likewise, the development cycle cannot stand alone without coordination with the planning and support aspects of the project. 

There is, however, a level of ADEQUATE planning that is both necessary and sufficient for project success.  And then there are levels of planning that are so far beyond what the minimum needs are that they can tend to take on a life of their own.  Obviously the appropriate plan is the one that works------and knowing what is appropriate is as much an art form these days than a science.  Conventional thinking has the “Planning” phase of efforts delivering a prescription containing SCOPE (Features, Functions), RESOURCES (Costs, Staffing), and SCHEDULE (Timelines, Phases).  Project Managers then have to develop, integrate and launch based on these initial plan documents……which we should all realize will morph over time as the project (and the stakeholder’s understanding of the project) develops.

The plan will ultimately drive the project, as it should---but the key to success however is to allow the project to modify the plan as required----and to build into the initial plan the process that allows for modifications over time as the project takes on a life of its own.

Web project planning never stops---it adapts to user and stakeholder changing preferences continuously.  As such, the underlying architecture and technology plan needs to be as flexible and far reaching as practical.  Not a simple balance to achieve---but the goal of every engagement we undertake.