2.16 Mapping Requirements to the Project Plan

 < Day Day Up > 



2.16 Mapping Requirements to the Project Plan

One of the worst duties of a project manager on these big initiatives is to create detailed project plans that are both accurate and relevant. Whereas this is the subject matter of Chapter 6, it deserves a word here. Having detailed requirements and subsequently derived specifications makes planning and risk avoidance far easier when it is time for those activities to kick off. Why is that? Because generating the appropriate level of detail and discussion on deliverables now will concurrently surface most of the sequences, dependencies, and risk that you will need to run through the planning process later. These latter bits of data are the natural offshoot of the requirements development process and can be swept right off the floor into the planning hopper when the time is right. By the way, this is just around the corner from where we are right now.



 < Day Day Up > 



Complex IT project management(c) 16 steps to success
Complex IT Project Management: 16 Steps to Success
ISBN: 0849319323
EAN: 2147483647
Year: 2004
Pages: 231
Authors: Peter Schulte

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net