iSixSigma

Looking for Ideas in IT for a BB Project

Six Sigma – iSixSigma Forums Industries Software/IT Looking for Ideas in IT for a BB Project

This topic contains 7 replies, has 6 voices, and was last updated by  MBBinWI 2 years, 10 months ago.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #55407

    SIKANDAR ARORA
    Participant

    Hi,

    I work as an IT Professional ,hold a Green Belt and want to get certified as a Black belt
    Was searching for key Pain Areas in the IT domain that I can work upon as a new Six Sigma Project
    Please help in identifying projects that I can start working upon to achieve Black belt

    Thanks
    Sikandar

    0
    #199887

    Strayer
    Participant

    I’ve seen many IT Six Sigma projects fail, including some that I led, because an improvement had already been assumed. For instance, adopt agile methods, ensure bi-directional requirements traceability, enforce secure coding practices, implement service level agreements, and so on. We may know that these are good things to do but the solution is not a starting point.

    I’ve seen others fail because a problem was evident but there was too little information to write a specific problem statement. Such things as recurring complaints about the help desk or slow system response. There’s one or more SS project here but you need to do some preliminary work to narrow down and measure the problem before you tackle it.

    And finally, your question is off the mark. No one can really help you by telling you about typical pain points or projects that have been done in other companies. You need to start by looking at the problems in your own company. Otherwise you’re doing what I first advised against. The solution is not a starting point. Resist this temptation.

    0
    #199892

    Mike Carnell
    Participant

    @sika83 Let me ask you this. If you are logging onto a website and asking complete strangers for idea for projects on a process they have never seen doesn’t that set off some kind of alarm in your head? You probably didn’t cover a lot in your GB training about project select or at least you should not have for a very simple reason. It should not be your job to go out and find a project. The people running your deployment and management should be deciding where they want to expend resources on projects. That is what they do in every other department but if you are a belt you need to find your own work? that is nonsense. I am guessing you are on one of those misguided deployments where someone believes if they just throw a bunch of BB’s out there everything will magically get fixed. you may also have those completely worthless MBB’s that want you to present your project at a toll gate so they can be a big shot and urinate all over your work like a drunken alley cat – mostly because they don’t know what they are doing.

    Bottom line if you have to go find your own project just walk away until they fix the deployment otherwise you are just crawling up on the alter and handing them a knife (a little drama).

    Just my opinion

    0
    #199917

    SIKANDAR ARORA
    Participant

    Thanks @mike-carnell and @Straydog for the advice
    Huh ! this gives me indication for some more ground work to be done before aspiring to be a BB
    Identifying Problem areas ,I found is the most difficult part of this journey ,I would need to consult with my management to suggest their problem areas not sure will be granted though

    0
    #199936

    Don Turnblade
    Participant

    Drive storage arrays such as RAID stacks have large numbers of disks running in parallel that can fail and automated procedures that spin up hot swappable drives to replace these exist. But predicting purchase rates when cheaper drives fail faster versus purchase and failure rates when more expensive drives take longer to fail leads to a cost of quality problem in operation. Initially, it might be a time dependent binomial or Poisson statistical problem. First cut models that I used at the time searched for the peak probability of failure and a confidence interval for hot swappable drive inventory management. But, quality of drive factors can improve this.

    0
    #199937

    Don Turnblade
    Participant

    Information Security vulnerability patching queues is a rather hot topic. Consider the time in queue of a critical vulnerability unpatched vs the mean time to exploit that vulnerability and harm the firm. Then, there is the cost of more staff to set up patching jobs, QA test them before releasing them to production. Is a faster team more expensive? Should there be more parallel teams? Lot splitting of jobs? Are some areas of the network more sensitive to external versus internal attack. What about patching plans that are 95% confident to always complete before a compliance deadline. PCI DSS requires that critical vulnerability patches be resolved in 30 days, High vulnerability patches in 90 days. Internet facing systems need to patch even Medium vulnerability patches. What about Whitehat statistics suggesting that 80% of websites were vulnerable to one or more critical vulnerability all year in 2015? Coding standards to prevent, discover and remediate both Internet and Intranet facing vulnerabilities have lots of factors to create reliable processes. Cost effective change. Lean processes. Reliable patching to meet or exceed compliance objectives.

    0
    #200480

    Boyan Angelov
    Participant

    An idea is to focus on knowledge creation. In case you are in the Support industry, it is a very valuable tool that can deflect high number of Support cases, thus lowering the overall support costs and customer satisfaction.

    0
    #200484

    MBBinWI
    Participant

    @sika83 – If it is difficult to identify where your pain areas are, then I humbly suggest that you don’t have good objectives and metrics around those objectives. That is where you should start. Just my humble opinion.

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

You must be logged in to reply to this topic.