Agileista

The process you go through during Agile software development serves to simplify and clarify the task at hand to the degree that you can almost forget about the process entirely and concentrate on the work. Sure it can be hard work, implementing Agile methodologies is not an easy task. Luckily understanding them is. The hard work is in the work itself, not in implementing some overbearing project framework. This is great because it frees up time to concentrate on the biggest single issue in application development. Building the right Software.

That's where, for want of a better phrase 'Agile engineering practices' come into play. Agile project management methodologies like SCRUM help you create the right environment for development and the engineering practices help you develop great code. It's probably easiest to understand how it all fits together if you look at the process of getting from requirements to product, or from soup to nuts as one ex-Accenture con put it. In future posts I'll talk about the processes we've been through stage by stage, what worked and what didn't and how each of the two layers of an Agile approach; engineering practices and management practices, work to support each other.