Posted by: SJC
Paragraph 3 of the “Agile Manifesto” states this principle:
“Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale”
Living up to this principle is no trivial task, not even for a team of developers! I wonder how many really do, and what kind of project are they working on? Doesn’t it seem like there are always new issues to deal with? What about getting time to keep up with the latest and greatest available tools of our trade? When does this happen?
For many of us I believe that things like learning the “latest and greatest” occurs off-hours, if at all. This off-hours “work” is frought with danger of course – danger of burning out, danger of destroying relationships — to name just a couple. Yet, in the IT software development field, knowledge of current and developing trends in development tools can be critical.
Choosing the right tools for a job very often becomes not really a choice, but rather a continuing well-worn journey down the path often traveled, almost by rote. We are fortunate to be working IT software development at this time. New tools are coming along constantly, and being updated along the way. I must admit, I’ve been known to get frustrated because (it seems) I just get comfortable with my development tool of choice, and here comes a “new” version — and there are always “things” to learn — but I get over it.
As for being “Agile” and delivering frequently — I firmly believe that what allows us to even think about living up to that principle is the toolset that we choose for development. Remember Cobol and how long even some of the most simple things took to create? We’ve come a long way — and choosing the development toolset for your application is critical in your quest to be “Agile”.