Automation, humility and templates

There is a very amusing (and amazing as well) post about the seven capital sins of using automation for testing. In my yesterday’s post, automation had a huge importance. Therefore, the indications suggested by Colin, are to be taken with the utmost care.

In essence, the best solution against mistakes remains a good dose of humility.

It is not an easy recipe. Being accountable means to be respected, self esteem is not an optional; moreover, leaders have to be inspirational – humility sounds on another wave. However, it can be mustered through an honest and intense activity of listening and showing appreciation to the others. “Sometimes being responsible means piss other people off” (citing Collin Powell) doing it with a bit of tact (and a lot of energy) could be a powerful form of humility. By the way, this word comes from Latin and means soil; just feeling the physical ground under our feet could help us in finding the force to be less rude in pissing off people who deserve it.

Templates available

Today:

Risk Management Strategy.

This document encompasses the “Risk section”, that includes:

  1. Issue Report
  2. Issue Management Register
  3. Impact Analysis Report
  4. Impact Analysis Register
  5. Risk Management Register
  6. Exception Report
  7. List of Risks

The complexity of the topic has required to conceive three different type of documents:

1)      Strategy – covering the structural elements and covering all aspects mostly from organizational viewpoint

2)      Report – where the communication is punctual on the single fact that is presented in its natural scenario (e.g. trend)

3)      Register – a more technical document (residing in a DB) where all the data are collected with few formal rules to check their validity. This allows both completing and updating the information in different times. The most important reason for this strategy (DB on web) is due to these factors:

  1. Easy to be accessed by the “right” person with no physical constraints
  2. Meshing information that could be pooled and inserted in a document (report)

Leave a Reply

 

 

 

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Before you submit form:
Human test by Not Captcha