Posts Tagged ‘agile’

Kanban Book Review

November 22nd, 2011 Leave a comment
Kanban Book Review

Book Author: David J. Anderson As a techie, I have always freely admitted that my skills lay more in the nitty-gritty of system administration and software development. I’m vastly more comfortable setting up a Linux box or throwing up a quick Python script for management than I am actually being management; when it comes to complex development processes and control of varied workflows, I’m more lost than a bat in the sunlight. That said, David Anderson’s book Kanban: Successful Evolutionary Change for Your Technology Business was a welcome addition to my bookshelf. It really slims down the overbearing ideas of software development… View full post »

Agile Retrospectives Book Review

January 31st, 2011 Leave a comment
Agile Retrospectives Book Review

Software development is, unfortunately, very often viewed less as a methodology and more as an improv show; managers and sales reps throw in features, programmers throw in functions, and the code base spirals into mediocrity as programmers are more concerned with new functionality than they are with stable development and bug-squashing. This is, in part, what the Agile method of software development is intended to address; by breaking the process into iterative release cycles, development teams are better able to adapt to a rapidly changing set of conditions and feature creep. The problem with this is that occasionally, in such a… View full post »

Changing Requirements in Software Development

March 23rd, 2010 (Guest Blogger)Leave a comment
Changing Requirements in Software Development

It was at one of my previous jobs, when I had to witness an unpleasant relationship between engineering and business folks. Company’s main product was a network optimization software that would enhance standard internet routing protocols. Team was small and we were pretty much following a traditional development model, where requirements were fully understood and signed off by customers and business analysts before the engineers would start working on the product. In the early life of the product company was targeting the ISP business, however as time went by and product was not selling well, company decided to market the… View full post »

Agile Methodology: Software Over Documentation

March 22nd, 2010 (Guest Blogger)Leave a comment
Agile Methodology: Software Over Documentation

One of the other main values in software development using Agile Methodology is choosing a working software over a complete documentation. Reading Scott Ambler on Agile Modeling: Like it or not, the primary goal is not to produce extraneous documentation, extraneous management artifacts, or even to produce models. Creating extraneous documentation can be comforting because you can fool yourself into believing that you are making progress when in fact you’re not. Instead, you’re actually avoiding a difficult task, likely writing and testing code that may show that your chosen approach isn’t working as well as you thought it… View full post »

Agile Methodology: Individuals over Processes

March 18th, 2010 (Guest Blogger)Leave a comment
Agile Methodology: Individuals over Processes

In my previous blog, Software Development Using Agile Methodology, I wrote about main key values of Agile Methodology, one of which prefers people over processes in software development. While reading Martin Fowler’s article “The New Methodology”, this paragraph has caught my attention: One of the aims of traditional methodologies is to develop a process where the people involved are replaceable parts. With such a process you can treat people as resources who are available in various types. You have an analyst, some coders, some testers, a manager. The individuals aren’t so important, only the roles are important. That way if… View full post »

Software Development Using Agile Methodology

March 15th, 2010 Leave a comment
Software Development Using Agile Methodology

We all have lived through the nightmare of a project lacking the process to guide it. The lack of a process usually leads to unpredictability, lots of repeated error, and wasted effort. We end up having disappointed customers who are not happy with growing budgets, slipping delivery schedules and poor software quality. At the same time developers are disheartened by working ever longer hours to produce ever poorer software. Once we have experienced such a fiasco, we become afraid of repeating this experience again which becomes stressful and no longer fun that we thought software development… View full post »