Top positive review
One person found this helpful
A succinct introduction
on 28 July 2014
I never heard of Agile or Scrum before, but after reading this quick and informative overview, it's an approach I've been using intuitively in my own software development. It makes sense. No need for complicated documents and dependency diagrams as in SSADM, yet rigorous enough to get things done and stick to the requirements (even if they tend to change during development as they inevitably do).
There's no discussion about the disadvantages and inherent pitfalls, but that's not necessary in this short treatise. I imagine it's something one would have to look into when working with Scrum in practice. Even for a large-scale project, it would probably be useful to break it down into smaller projects and use Scrum as a way to manage the development cycle.
What seems to be the most salient feature of Scrum is that developers work in small teams of around 7-9 people, with regular but highly focused planning and status meetings for each iteration of the product life cycle; and this keeps the communication tight and clear between members. And the client gets to see the progress milestones more frequently also, with real working results at each iteration.