| Keeping your Schedules off the Fiction "Best Seller" List |
|
|||||||||||||||||||||||||||||||||||
Dear Jeff, When constructing a design schedule do you find your best efforts at planning, estimating and building the ideal schedule later leave you feeling like you have created a great piece of fiction material? This repeats itself project after project and any chance of schedule credibility goes out the window. I have been there many times and have since developed enhancements to the scheduling process that have provided relief from the fictitious schedule syndrome. This newsletter will share principals and techniques that have helped pave a path to more realistic schedules for my design projects. Jeff Jorvig
The most important aspect in creating a schedule that does not make the fiction “best seller” list is to ensure that it is thorough in content and predecessor expectations. A schedule that does not include everything that will occur, or must occur, will never be factual. We all know this; the challenge is routinely attaining the necessary level of detail that will produce predictable design projects. Following are my three favorite solutions to schedule inaccuracies. Make no Assumptions Say what you Need Find what you do not know
The least predictable project will come from a schedule developed through a task breakdown done by an individual. An incremental improvement is gained through a review of that schedule by the team. Schedules that produce the highest level of predictability are produced when the entire design team participates in the task breakdown using a brainstorming type environment. Brainstorming of the tasks facilitates the “Make no assumptions”, “Say what you need” and “Find what you do not know” principals that I introduced in the last section. This is the time to get everyone’s needs out on the table, find what flow development work is in order and begin to address where some of the unknown or unmanaged activities exist. Attendees of the brainstorming task breakdown activity must include all of the design and layout team that are likely to be involved in the project. A representative of CAD, who has authority to commit resources, should also participate. I have typically also included program management, test and product engineering since they will be receivers and definers of certain design deliverables they will need for their success. During the task brainstorming you are identifying tasks, committing resources, identifying predecessors and gaining task commitment. Pay close attention to the discussion that takes place within the team as you break the project down. There will be points brought up that should trigger your “assumptions” and “unknown” detective thinking. Once triggered, make sure you get to the root of why they came up. There is little doubt there is something to be addressed and you need to identify what it is and ensure task(s) are created to close on any assumptions or unknowns that surfaced.
If you have any specific design process questions that you would like an opinion on (my opinion) please email them to me and I will address it here. I will maintain your anonymity, unless you indicate otherwise. Go ahead and throw me to the wolves - give me something that you have been struggling with for a while. Also, please let me know of any general design process topics that you would like to see covered in future newsletters.
|
|||||||||||||||||||||||||||||||||||