I have read a couple of books and several articles about the agile development approach.  What was funny to me is that there was a necessity for entire books on this topic; as I understand it, this boils down into some simple concepts, and these are the ones which I can apply in my shop:

The objectives

  • Produce a quality product
  • Focus on the work that provides immediate and tangible benefits to business partner
  • Streamline project lifecycle

The methods

  • Structure a project team consisting of project manager, designers, software engineers, quality assurance and business partner.
  • Break the project down into small, independent functional components.
  • Create tools for testing these components in isolation (prototype).
  • Categorize project components into independently installable phases.
  • Schedule regular brief status meetings with the development and testing team to review bugs, identify obstacles, and establish action items to be addressed before the next meeting.

So why the proliferation of literature?  Why the rhetoric, the nomenclature, the rules, the standards?

Each project needs to be analyzed to determine how best it can be implemented.  The methods above are general; the specifics may include partnering developers, ice cream breaks, group offices, isolated cubicles, a combination of formal design followed by a prototype, a daily meeting, brainstorming meetings at Starbucks.  In other words, there is no single formula to follow.  Some of the terminology still sounds nuts to me – a scrum, for example, sounds vaguely pornographic (maybe that’s because there is a full moon tonight?) – and when dropt in conversation rather screams an elitist attitude lacking in substance.  However, I can respect the variety of Lean Software Development, eXtreme Programming, Test Driven Development and other specific agile approaches as potential methods to gain the road when it winds so precariously before me.


2 responses

  1. “brainstorming meetings at Starbucks” oh wows you serious? No ways! What heaven is that! Sometimes it all depends on the project, sometimes it all depends on the people in the team and then the company. Over complication just helps us lose sanity. … now dying for a starbucks. Wonder why they never made it to South Africa…

  2. Yeah, I have actually had a manager meeting at Starbucks. It was kind of a tight fit for the four of us around a table designed for 2, but it was worth it to get out of the office and let our hair down a bit.

    It’s important to me that projects are treated individually, not subjected to some sort of formula. What works for one will not work for another. We recently completed a very small change to a report, and if we had used Agile, it would have taken far longer and not had a bearing on the quality of the product.

    I am craving Starbucks too. Soon you will be in a land of Starbucks – hang in there!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: