4.10 Conclusion

 < Day Day Up > 



4.10 Conclusion

If you think I got a headache as a result of figuring out that project, imagine what would have happened if I tried to schedule the tasks without having some ideas as to where we were headed and how we intended to get there. This particular project had a very unfortunate cast of characters from a communications standpoint, so my job of keeping everyone on the same page was extremely difficult and, at times, impossible. Quite happily, few projects are quite that extreme in this regard. It was this project that proved to me, once and for all, that getting agreement on an implementation strategy is a must before going forward with detailed planning. The latter should be pretty easy once everyone agrees on the approach.

Hopefully, the examples used in this chapter fully illuminate the value of developing as complete an implementation strategy as possible. It should be documented and circulated for review and critique because, although your story may originate as fiction, you want to make sure that it ends up as fact, with a happy ending to boot.



 < 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