Skip to content

Go Crazy

Dec 1, 2014 - 2 minutes read

Objectivity Blog 416 306
Mr.Q
Quality Guild alter ego.
See all Mr.Q's posts
1553 Devops Whitepaper News Section 416X300 EN

Share

All organizations have policies, procedures and instructions that govern how work is done. Well written documentation increases organizational transparency. Even where policies and procedures are not written down they exist. Why do we need standardization? - you may ask. My answer is - Why are screw threads and heads always the same size, or why does every retailer use the same shoe sizing system?" Everybody needs a framework to direct them along the right direction and the customer needs assurance about the level of quality which they will receive. So when you consider to prepare your own procedure – go crazy.

The system documentation is a lot like a recipe. You are provided with some information about what you are making, directions on how to make it, and an example of the finished product. Yummy. A procedure specifies what will be done, when, and by whom and what records are to be kept.

Having well-written documentation supports organizational memory. Documentation control systems ensure that the most recent documents are the most relevant, and no one is working on older copies. That is like sending your old girlfriend's Valentine's card to your new girlfriend - with the old girlfriend's name on the inside. Not ideal, is it?

Be smart about the scope of documentation. Travel light. Someone trekking across the desert will benefit from a map, a hat, good boots, and good supply of water. They likely won't make it if they burden themselves with hundreds of gallons of water, a pack full of every piece of survival gear imaginable, and a collection of books about the desert.[i]

Control of documents and records procedure is defined by some basic rules which a documents or records creator needs to follow:

Documents must:

  1. Be approved
  2. Occasionally be reviewed and again approved. Blow the dust off, and all that.
  3. Make sure the documents are kept clean so people can read them. No coffee stains or smartass comments written in the margins. Let’s at least try to appear professional.

Records needs to:

  1. Be legible (no coffee stains)
  2. Identifiable (try naming each form something that distinguishes it)
  3. Retrievable – don’t store them over a pit of ravenous wolves.

For more details click the picture below. _sklep_02_flat - Copy    

[1] http://agilemodeling.com/principles.htm#TravelLight

1553 Devops Whitepaper News Section 416X300 EN
Mr.Q
Quality Guild alter ego.
See all Mr.Q's posts

Contact

Start your project with Objectivity

CTA Pattern - Contact - Middle

We use necessary cookies for the functionality of our website, as well as optional cookies for analytic, performance and/or marketing purposes. Collecting and reporting information via optional cookies helps us improve our website and reach out to you with information regarding our organisaton or offer. To read more or decline the use of some cookies please see our Cookie Settings.