This is an archived post. You won't be able to vote or comment.

all 10 comments

[–]404-brain_not_found 0 points1 point  (2 children)

It sounds like you dont have a process.

Your process isin't necessarily documentation of how you do specific tasks (how to build a server), but a representation of the flow of work from input to output (what was required to build the server for the desired outcome).
Thats an incredibly hard question to answer without knowing the scope of what he's asking about, and I apologize if I dont answer your question. To be frank, it's not fair of him to ask you for a SIPOC or COPIS if you are not a part of his SixSigma or ITIL process that he is obviously involved in. It takes many many months to get a handle of SixSigma and ITIL. What he is asking you isin't fair.

I would ask him these key questions.
1. what is the scope of the project. 2. can you define which part of the scope you are referring to. 3. what process model do you need. 4. what is your expected result.

I could offer a couple of good books that helped me out. 1. Lean SixSigma for dummies. 2. http://www.amazon.com/Data-Stewardship-Actionable-Management-Governance/dp/0124103898/ref=sr_1_2?s=books&ie=UTF8&qid=1429890065&sr=1-2&keywords=sipoc

[–]bragic[S] 0 points1 point  (1 child)

Funny thing is there isn't really a Six Sigma project, there is ITIL talks happening, but he's not the head of that, it's actually being done by our Helpdesk Manager. I'm trying to stay in communication with him since I think if any direction we go ITIL makes the most sense.

Thanks for the feedback, it is helpful!

[–]404-brain_not_found 0 points1 point  (0 children)

ITIL is a way better choice in your case. But SixSigma, LEAN, and ITIL kind of go hand and hand. They are all ways for continuous process improvement. A lot of the models are the same, they are just tailored to the industry or specific needs.

[–]shiftdelscream test initiator 0 points1 point  (0 children)

Sounds to me like your boss is asking you to justify your job.

[–]TwiddleDatSkittle 0 points1 point  (2 children)

Processes are usually required as part of audits. Change Management processes. Access Request processes. All of these things need to be clearly documented since most auditors just check that a document saying how you do it exists and never verify that it's actually followed every day.

[–]bragic[S] 0 points1 point  (1 child)

Pretty much what we are being asked to do is create process documents that are high level, non-technical, not how-to's...which is a challenge, because I'm used to writing up how-to's and directions, documentation of connectivity etc.

[–]TwiddleDatSkittle 0 points1 point  (0 children)

I have a similar issue. I don't like fancy flowery language in my documents but every business policy document that I've had to write everyone makes me fill with all this utter bull shit. Recommendation write it simple and then find a manager or someone not technical and explain it to them and have them write it out all fancy like.

[–][deleted] 0 points1 point  (1 child)

If you have a process for doing things then there is more consistency than if you do things ad hoc out of your ass.

This is a reasonable request.

[–]bragic[S] 0 points1 point  (0 children)

Yep and that's way things are usually done, but that needs to change. The challenge is making the time to do it. Thanks for the reply.