We’re pleased to welcome Joe Woods as a guest post today who will share with us his thoughts on agile software development principles patterns and practices. He who will be sharing his thoughts with us on what he likes about Agile Software Development, Part 1. In Part 2, he’ll share with us his thoughts on what he doesn’t like about Agile Software Development.
The Agile movement in software development is heavily influenced by Lean and the Toyota Production System – often times called Lean for Software. As you read this – especially if you’re not a software guy – be careful to look for applications of Lean in how software is developed.
Enjoy the post.
This is my view of the agile software development process from an outsiderâ€™s perspective.Â Now Iâ€™m no agile expert, far from it actually.Â I was always told that weâ€™re an agile shop or that we use waterfall (cringe). Ok, thatâ€™s fair enough.Â All that meant to me was that we do releases every couple weeks or weekly and I have to go to a bunch of team meetings.Â I also would have to write these things called stories and they couldnâ€™t be too broad and being too narrow meant I missed some functionality.Â It always seems to be the case that the last place I worked did it wrong, so I always had to learn another way to write a story, how to assign points, and what I had to do to accept or reject a story. Not a big deal once you learn whatâ€™s expected.
Now, Iâ€™ve been in the internet marketing space for about 10 years now and have had the opportunity to work for many different companies from small start-ups to Fortune 100â€™s.Â Iâ€™ve had to wear many different hats in this time.Â Sometimes I was the marketing jack-of-all trades, other times I was the SEO guy, and more recently the consultant/project manager/product manager, slash this or that.Â Basically, Iâ€™ve always been a stakeholder in agile terms.Â Iâ€™ve worked in agile shops, waterfall shops and shops where there is no process.Â My job success has always been measured by how far I can take the business from points A, B, C and D.Â Itâ€™s vitally important that I get some quick wins starting out to prove my worth and then continue to move the ball or move the needle or get to the next level. Speed and buy-in are always a factor, results are a must, and time is of the essence.
Waterfall versus Agile
Working in a waterfall shop usually meant that I had to spell out all requirements for a typical request, bug, or functionality in great detail.Â All requirements had to be included and every detail accounted for.Â I find breaking it down to a very basic level seems to work best here without insulting anyone.Â Drawing a picture and placing arrows seem to work best to get the point across.Â Then everything had to go through a vetting process and get signed off multiple times.Â Waterfall releases were always planned months in advance and pretty much set in stone.Â This meant that if I started with a company right at the beginning of the new cycle, which always seemed to be the case, then I had months of waiting to get anything done.Â Even the simplest change took an act of God to make happen, if it were to happen mid-cycle or in the next release.Â Well, thatâ€™s never a good thing as mentioned above and I always knew it was a matter of time before I was gone.Â Later, I would watch my requests get worked in and the site become successful as a result.Â This is more of an issue with impatient management and managing expectations on my part than the process itself, but I think it points out the inefficiencies with Waterfall project management.
Fast forward to agile development success.Â I have to say that I really like agile much better.Â The reason I like it better is simple: speed.Â We have more releases which mean I can effect marketing changes and web changes much faster.Â Sprints can be planned out months in advance as well, but most times they are only planned a release or two ahead.Â There is also some flexibility in adding additional stories to the queue.Â So for me, getting a couple stories placed in a sprint or added if the points are available is always a good thing.Â Marketing things get done faster, numbers come in faster and everyone is happy.Â More importantly, I get to keep my job.Â However, agile isnâ€™t without its quirks either.
About Joe Woods
Joe Woods is one of the top SEO and Internet Marketing Specialists in the Southeast US and has worked with Agile and Scrum since 2007. Joe currently works with Version One and many of the industryâ€™s leading Agile coaches to help IT teams and practitioners evangelize the many different process from Agile, Scrum, XP and Kanban.