Specification By Awesomeness

If you make the tools easy to use, the process easy to follow and it helps get things done, then people will follow the process, they will use the tools and so you have a defacto standard. You have a standard that actually helps promote work and productivity.

Even if the tool is slow and unresponsive, provided it helps get things done, people will accept it. I have had this happen first hand with my WebMethods tools that I developed for the company I work for. The tool takes a few minutes to do anything (yes I know I need to optimize, but I don’t have the time – and I was taken off the product so that other team members can can know e source code), but it is hailed by my team for the simple reason that it can save hours of work even in its crippled state.

On the other hand, if you have a process designed to slow things down. Has long lead times. Tools that are difficult to use and basically hinders productivity and feedback, then you will find people complaining about the tool or the process. People start to get disgruntled. You have to force the standard and overall you will end up with a compliant workforce rather than a productive workforce.

In our news, I went and took a certified scrum master course and I am now certified. With my interest in DevOps, Lean etc, and given my experience in my first Agile project recently, it seemed like someone to do. I just hope that I can use my new found knowledge sooner rather than much later.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.