iSixSigma

Project Schedule Quality

Six Sigma – iSixSigma Forums Industries Software/IT Project Schedule Quality

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #54945

    Mary
    Participant

    I am starting a Green belt project to measure and analyze IT project schedule quality. Are there any suggestions, or best practices anyone can share on what to measure, what to gather or how to gather data, or what to focus on? We do use MS Project as our scheduling tool. Thanks

    0
    #197806

    Gilberth
    Guest

    There are two ways, first laa: Establish milestones of controls to determine progress. The second: to establish fixed frequency of review of activities where the relationship is reviewed executed versus made

    0
    #197807

    Don Strayer
    Guest

    Another way, call it “schedule fidelity index” or whatever you please, is to divide the number of tasks (or milestones) completed on schedule by the total number planned to have been completed by that point in time. This gives a single number with 1.0 being ideal. Since you use MS-Project you can automate creation of this metric.

    Be aware that these are performance metrics, not quality metrics, and they will be used accordingly. The appropriate goal for a GB project would be to improve your organization’s capability to measure schedule fidelity. For that you need a different metric that tells you how well you currently measure schedule fidelity and how much better you do it after the improvement. Don’t get pulled down into the weeds of evaluating success of your project based on the improvement of teams to meet schedules. I’ve been there and it isn’t pretty.

    0
    #197812

    Shelby Jarvis
    Participant

    It is also important to meet with your stakeholders to get a better understanding of the voice of the business. If you simply ask for their input, you will may receive the simple answer of we want to know the quality of our process……I suggest digging deeper and get multiple stakeholders together if possible.

    Some will likely be solely focused on the outcome, some may also consider speed, yet others will identify the level of re-work, cost, etc. Take the time to capture their inputs then write your problem statement in a manner to deliver success in their eyes.

    I agree with Don, take care not to sign up for deliverables outside your scope.

    0
Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.