$Account.OrganizationName
Keeping your Schedules off the Fiction "Best Seller" List )
Issue #18 June 2006
in this issue
  • Some Basic Principals in Building Schedules
  • Design Task Breakdown Must be a Brainstorming Session
  • Ask Me
  • 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

    Some Basic Principals in Building Schedules
    Error Sources

    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
    As soon as assumptions creep into the task breakdown process, tasks that should be managed to closure become non-issues and fall off the list. One of the largest offenders for misplaced assumptions are tasks related to the design tools themselves. If tool and flow development or validation tasks are not part of the project they will not be properly managed, and if they are not managed they will not be in place when the project needs them. When identifying tool activities for a project consider model gaps (temp, voltage, mismatch), newer flow steps, new device structures and new top level validation methods. In addition to tools keep an eye out for other areas where an invalid assumption about the status of a required deliverable to the project will jeopardize your schedule accuracy.

    Say what you Need
    The primary consideration when building a schedule is that every owner of a task is clear about what they need. One of my simple rules of engineering management is “Leave no room for ambiguity or interpretation in your requirements for success. Say what you need”. When applied to a task in a schedule it means the task owner must be clear and concise about what they need for optimal success on the task, the success factors. Anything less and the upstream tasks or predecessors will not be defined to produce the required deliverables, leaving the current task without its required success factors.

    Find what you do not know
    Finding what you don’t know is about making sure you have identified all the activities that must be included to produce a predictable workflow. All the essential tasks to accomplish this are not necessarily obvious to the team as a whole, dictating the need for some background work to bring them up to the surface. The process of finding the unknowns in your design workflow can be reviewed in one of our earlier newsletters that discusses formal discovery. Leaving out quality time to find what you don’t know, prior to schedule building, will be certain to add a level of unpredictability to your project .

    Design Task Breakdown Must be a Brainstorming Session

    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.

    Ask Me

    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.

    On Site Seminar: Excellence in Managing Design Execution
    Seminar Objectives
    Many IC design project teams find themselves struggling with unexpected delays to their production plan. Intense time to market pressures demands an environment that prescribes improvement to both the predictability and length of design timelines. This seminar specifically targets those essential improvements through several thought provoking concepts that will enhance the predictable nature of IC design teams by expanding the scope of the design management landscape.

    Emphasis will be on enriching the IC design process a team uses by means of a revitalizing design management perspective. Participants should have an open mind, be willing to listen and talk, share design experiences and frustrations and participate in discussing ideas about doing things differently. The seminar takes a refreshing journey beyond the routine CAD and tool flow activities of design thus opening the door to possibilities for change in the way a design project is managed.

    Upon completion participants will be armed with concepts to develop comprehensive plans, tools to improve the design workflow and an expanded vision of managing design in a predictable manner.

    Ready for a Quote: Please contact us about a seminar at your site!

    More about the One Day Seminar

    Quick Links...
  • Register Now
  • Newsletter Archives
  • More About Us
  • Custom Training Solution
  • What we do
  • Contact Us

  • phone: 480-895-0478