As an agile writer, I like to write articles in multiple iterations. Feedback from readers…
In our company I am responsible for most of our process improvement activities. It's not that I can do everything myself. But I must make sure that there are plenty of initiatives, that they don't bite each other, and that they are moving the organization into the direction that I desire.
Some examples: new templates for standard documents, improving our testing methods, introducing new intranet and project environments, reorganizing teams into cross-functional ones, reorganizing job descriptions and levels, creating new training materials, coupling invoicing to time registration, improving the project estimation procedure, improving the recruitment process, etc…
Basically, my process improvement efforts come down to this:
It's a simple process, and it's a fine implementation of the Plan-Do-Check-Act cycle of Deming/Shewhart. It also happens to be a process that follows several agile principles.
Still, I'm having trouble getting things done. Why?
The Hardest Part: Implementation
Knowing what to do often isn't the hardest part. I know how to do process improvement, and I know how to use agile principles. The most difficult part is the actual implemention of these fine ideas. The world isn't perfect, and neither am I. But sometimes I cannot help dreaming of utopic environments that are a little more co-operative with my best efforts…
Subscribe to this blog with a reader or by email!
Latest, greatest and favoritest posts:
Agile Job Descriptions
Scope, Resources and Processes: Change Everything!
Getting Square with the Iron Triangle