9: Find the fire starters. When the system becomes established look at each and every exception and trace it back to the point at which it originated. Too much of our time is spent fighting fires so the most effective thing we can do stop them being started. Use the Process Change Process to refine the automation so that those kinds of errors cannot occur again. Track the exception counts as a KPI and drive them towards zero.
Tell us what you think
Click here to take a brief 7 question survey to help me improve my blog. Thanks.-
Recent Posts
- Should developers performance test their code before checking it in?
- What is the benefit of doing performance testing earlier in the application lifecycle?
- What is the value of Data?
- ALF, OSLC and SLI – enough of the soup, time for some meat
- Will we ever ‘just say “no”?’
- Testing times for system designers
- Thinking about focus
- From the Innovation Games Summit
- Upcoming presentations – see you there
- Cliff and the Shadows
Archives
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- October 2012
- September 2012
- August 2012
- July 2012
- May 2012
- April 2012
- March 2012
- December 2011
- November 2011
- October 2011
- August 2011
- July 2011
- June 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
Categories
Meta
Twitter Updates
- Home made raised bed, special vegetable friendly @Lyngso dirt, organic veg planted, waiting for crops ... Priceless http://t.co/Jof7MHgzDa about 3 weeks ago
- @TheTBTF: An offering from @kevinparkerusa , our speaker for the May IT Executive Council! bit.ly/11j8scz @SerenaSoftware about 3 weeks ago
- Just watched the Serena Change and Release Management demo for the 10th time at #sits13 ... it still wows me ... @SerenaSoftware @booth109 about 3 weeks ago