These people look pretty agile, no?
I hate corporate buzzwords more than anyone, so when my company decided to implement the agile workflow for our development team a couple of months ago I was naturally dubious. My main objection to it however was that our team was already very agile. In fact let’s have a quick look at the agile manifesto from the Wiki page:
Individuals and interactions over Processes and tools
Working software over Comprehensive documentation
Customer collaboration over Contract negotiation
Responding to change over Following a plan
To me this sums up what our team was already doing, so why the hell we decided we need to piss everyone off by introducing idiotic terms such as:
- Sprint – Basically just a 1 or 2 week chunk of work, usually followed by a code release. We were already doing this!!!
- Stories – This just refers to a bug fix or particular project or part of a project you have to work on. In other words “a bit of work”. I don’t really know how any team would work if they didn’t already have some version of this!?
- Scrums – Simply refers to teams (e.g. real and meaningful terms like “backend team” and “frontend team” now become meaningless, infantilised names like “red scrum” and “blue scrum” …*pukes in mouth*… and so on). Luckily no one has tried calling any of our teams a scrum yet, if they do it might tip me over the edge