• Manjunath
    Implementing a full-blown Six Sigma program takes organizational commitment from the top.  It also takes a lot of guidance, especially in the software business.  If you are especially looking for quick wins, and it sounds like you are, then the approach is highly dependent on your particular shop, thus, it is even more important that y[Read more]

  • McD replied to the topic i want a project in the forum Software/IT 14 years, 9 months ago

    A really good project would be to figure out a way to balance those without enough projects with those who have too many!

  • You don’t have to do VOC by showing customers a prototype or mockup.  Ask the questions, especially the penetrating questions.  Take a look on this site for KJ.
    QFD is a wonderful tool for larger projects. Be careful with it though, it is easy to spend a terrific amount of time.
    But in any case, the time to do these things was long ago.

  • In addition, the Six Sigma Advantage web site contains a fairly lengthy list of papers on application of Six Sigma to I/T, including a number of case studies.

  • As for measuring reviewer effectiveness, it sounds like you have to do a Gage R&R.
    I’d be a little careful on this.  When you have something like a document that is quite unique, and more importantly, recognizable as an indivdual, it is pretty impractical to do a Gage R&R.  This does not mean, however, that you shouldn’t ask the questions.  It…[Read more]

  • In addition, a lot of companies consider their Six Sigma program part of their “competitive advantage”, and only release very limited information.

  • McD replied to the topic Question in the forum General 15 years ago

    TC is absolutely correct with his “it depends” answer, but depending on context, one thing you should be aware of.  To many managers, schedule is a more reliable estimate of cost than cost estimates, so managers will sometimes behave as if schedule is more important.
    But from a SS perspective, TC’s “ask your customer” is the right answer!

  • Ovidu has it right, you really need to understand what is behind the lean equations.
    The manufacturing stuff is actually pretty applicable; you just need to open your mind up to apply the same thinking to the I/T space.  Understand the 7 wastes, map your process, and then go after eliminating those wastes.
    In Six Sigma, we tend to go after the…[Read more]

  • A year is a pretty good realization period.  A quarterly or monthly session between the BB and the process owner should generally keep things on track, then a serious review of the financials by the controller’s department at the end of the realization period.
    I think most places aren’t likely to keep quite a close a watch on Green Belt[Read more]

  • This is a common problem in I/T, but rarely is it as serious as perceived.  If you want to improve your score card for validation testing, clearly you have an existing process that you want to improve.  Until you have determined that the current process is so badly broken it has to be thrown out, then you have a DMAIC.
    In Define you will put a s…[Read more]

  • McD replied to the topic need suggestion in the forum Software/IT 15 years, 3 months ago

    If you step back a bit and think about the “Six Sigma approach”, it really is not much more than a somewhat systematized view of engineering common sense.  Smaller projects are improvement projects, and the Six Sigma improvement process, DMAIC, when viewed at a high enough level, is nothing more than a classical engineer would do:

    Define -…[Read more]

  • McD replied to the topic MGPP Template in the forum General 15 years, 3 months ago

    SEH — funny you should ask.  I actually wrote the paper I spoke of, and it hung around while I waited for a few people to review it.  After a frantic January, I am now coming up for air and trying to decide whether it goes on my web site, or I try to figure out how to put it on this site.
    I never did come up with a template, and frankly, I’m n…[Read more]

  • I think far too many people focus on Six Sigma tools, and overlook the underlying methodology and philosophies.
    Clearly, many tools regularly used in development have their place in a Six Sigma effort, and indeed, thinking about the objectives may well lead you to rely more heavily on tools that you may have used less frequently in the past.
    In…[Read more]

  • You might also consider grazing the papers on Six Sigma Advantage’s web site.  They focus on teaching SS as applied to software.  Many of their papers are also on this website.

  • McD replied to the topic Six Sigma for Services in the forum Software/IT 15 years, 3 months ago

    > Reducing defects is appropriate even for a service industry.
    I would say especially for a service industry

  • DPMO for software is a kind of a tough nut.  Generally, you would like the “opportunity” to be defined in some meaningful way, but also in a way that leads to credible values.  You also want a metric that is reasonably reproduceable and realistic to produce.
    Defining a line of code as an opportunity will lead to very high sigma values.  Since so…[Read more]

  • McD replied to the topic Lean Certification in the forum Software/IT 15 years, 4 months ago

    The most effective Black Belt certification programs generally require some sort of validated savings from the Belt before certification.  I would suggest something similar for Lean (although I personally prefer the approach of includint Lean training in the BB program).
    The operative word is validated. Get your controller’s department involved…[Read more]

  • McD replied to the topic e-learning in the forum General 15 years, 6 months ago

    One process I have seen work quite well:
    1. An online intro to Six Sigma that everyone takes – pretty short, an hour or two
    2. An online Green Belt overview that each Green Belt takes just before starting the first project – a little more in depth, perhaps 10-20 hours
    3. A slide deck for each tool that the Black Belt delivers to the Green Belt,…[Read more]

  • Ryan
    A large part of the questions is how low is low.
    When a Black Belt undertakes a project in a low maturity organization, getting measurements tends to be the big problem.  Software organizations in particular tend to resist measurement, so the culture of the organization can be a large barrier.
    SS is also very process oriented. In many low…[Read more]

  • Will,
    You realize you are replying to a two year old posting?
    Dave Hallowell (who happens to work with Bruce) did post a pretty decent article on KJ in the library on this site:
    Hope this helps

  • Load More