Agile software development gave me hope that I could finally bring something to the teams that I fully believed would make their lives, teams and projects better.
That’s nice, but I think we should look at Agile.
In 2005, as an SQA Manager, I had just given a presentation to the CIO and my manager (an IT VP) on what needed to be “upgraded” in our current waterfall SDLC to bring us up to CMMI level 2. This was something that had been a company priority for a few years and it had somehow made its way to my plate. I was never a huge fan of implementing CMMI for CMMI’s sake but had taken a rather pragmatic approach to how this initiative could be accomplished within our company, based on business needs.
After the presentation, the CIO looked at me and said, “That’s nice, but I think we should spend time looking at Agile Development practices”. I was floored. I did not have any idea what Agile was….much less create a plan for how we would implement! So I began researching and reading everything I could find about Agile. I remember saying to myself….“This all makes so much sense. Why haven’t I stumbled into this sooner?” In all honesty, I had been working in the Process Quality end of things for five years and was tired of the development teams complaining about process. Endless whining about how traditional waterfall practices just did not work. Project audits that were painful. Customers complaining about how long it took to prepare and review copious documentation. I often felt like I was swimming upstream.
Agile software development gave me hope that I could finally bring something to the teams that I fully believed would make their lives, teams and projects better. I was really excited and found others to share my enthusiasm. The first pilot teams to try this out beat all project benchmarks!! This gave us enough momentum to keep going and going and going. My life has never been the same since and I no longer feel like I am fighting the masses. It has been a truly enjoyable journey and it ain’t over yet!