iSixSigma

How Long to Close Green Belt Projects?

Six Sigma – iSixSigma Forums General Forums Training How Long to Close Green Belt Projects?

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #55002

    Jeff Parks
    Guest

    I am trying to gather some real-life data on what the experience is on how long it takes to close GB projects.

    My experience at other companies have been as I recall, 8-10 months.

    The current company I am working with is experiencing >12 months.

    question: what are other people/companies seeing?

    This company wants more than just my memory and anecdotal experiences to compare

    Thanks to all who can contribute

    0
    #198165

    JB
    Participant

    Part of it might depend on what you define as “closed”. Some companies require longer data collection after implementation to prove that the process controls are effective. One company I worked for required 3 months of post implementation data collection before the project was officially closed. In that case, it was normally 9-12 months to close the project. But, our average is 6.8 months from Define Gate Review to Control Gate Review.

    0
    #198167

    Ram
    Participant

    In my current organisation, it is generally about 6-8 months. The main driving factor behind is because of how we narrow the scope of the green belt/black belt project upfront. I cannot reveal all factors but some of them are – Is it a functional or cross-functional issue?, How big is the performance issue with the existing process? etc.

    The time taken is mostly driven by the data requirements and the need to collect data in the absence of any other external influencing factors. I will be very inquisitive if it takes more than 6 months for a green belt project if there are no data issues or any other external issues.

    Regards,
    Ram

    0
    #198292

    Norbert Feher
    Participant

    Hello,

    It depends on the type of the project but never try to “boil the ocean”!

    Try to break down the problem into smaller parts and look for projects where feedback is very fast.

    This is especially valid for the 1st training project…

    Many people lost their interest in Six Sigma training during a “never ending” project.

    0
    #198355

    Amit Kumar Ojha
    Participant

    Hi,

    As per my expereince the time it takes to complete a six sigma project mostly depends upon the following factors:
    1. The calrity of scope.
    2. Top Management commitment – Whether top management is ready to invest the time and resources in the project and if yes, then to what extent. Much of it also depends on the criticality of the project.
    3. Urgency to fix it now. If there is no urgency, top management may provide limited resources leading to delay in the closure.
    4. Availability of Data.
    5. Mentor Support.
    6. Involvement of cross functinal teams and overall attitude towards continuous improvement and operational excellence.

    Going be my experience, I would say that it generally takes 6-8 months on an average to complete a green belt (considering 2 months or pre and post data for analysis) and 12-16 months for a black belt project.
    PI projects of other methodologies such as Lean / PDCA gets closed in reletively shorter duration (2-3 months on an average).

    0
    #199093

    Alberto Burgos
    Participant

    In my experience I would say 6-8 months. It also depends on what type of work you are in as well. I just transitioned to a financial institution and we have noticed an increase in the amount of time it takes to close GB projects. Like it was stated above we have been trying to create an umbrella affect and break them down into smaller projects so that we can focus on certain aspects sooner while still trying to work on the over-arching project.

    0
    #199096

    Chris Seider
    Participant

    @jwparks407

    The cycle time is purely a function of A) alignment of projects with key business needs, B) management/mentoring of teams by the mentoring belts and probably too widely defined scopes C).

    I’ve managed my GB’s who didn’t even report to me dotted line and they would get projects completed in 4 – 5 months INCLUDING the training period. I even did this for my clients…in a consulting role as mentor/trainer/project manager.

    0
    #199269

    Arun sathish RS
    Participant

    Best time Frame is 3 months for the Green Belt

    Black Belt is 5 months ti 6 Months

    This is without training

    iF training includes one month that is 25 days

    0
    #199293

    Joanne Wilkinson
    Participant

    Hi,

    When we started, we weren’t particularly good at defining appropriately sized projects so the timescale was well over 12 months. Some of the projects that we have run more recently, especially ones that are being mentored and supported are running in 7 or 8 months.
    If you are looking for whys to go with the measure, have you got any data on how long it is between stage gates at your company? Is there a particular problem with one section?
    Our projects tend to spend a long time in define – not because people are defining a really great project, but because they are putting off using the soft tools.

    Good luck!

    0
    #199304

    Arun sathish RS
    Participant

    What we mention is the Standard for the GB project. For any project At the time of a define phase itself we need to identify scope of the project. With a proper review and Monitoring by the six sigma coordinator’s and the steering committee ( then fix a proper Time Frame to complete the project. Otherwise partially close this project and handover to the process owner with the help of PTAP

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

You must be logged in to reply to this topic.