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… Click to view full post.
Archive for the ‘agile’ category
Agile Methodology: Software Over Documentation
March 22nd, 2010 Leave a commentOne 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… Click to view full post.
Agile Methodology: Individuals over Processes
March 18th, 2010 Leave a commentIn 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… Click to view full post.
Software Development Using Agile Methodology
March 15th, 2010 Leave a commentWe 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… Click to view full post.
