Perhaps the most important facet of agile software development is its innate ability to satisfy user requirements better, more accurately, more consistently, than what is considered ‘traditional’ software development. Where ‘traditional’ software development begs the user for all necessary information upfront and then reluctantly for feedback at the end of a project, agile development never lets the user out of sight.

This one differentiation separates traditional and nontraditional, slow and fast, waterfall and agile, 50% requirements satisfied and 100% requirements satisfied. The iterative nature of agile development forces engineers to go back to the user regularly, but more importantly, forces them to think of the user continuously. This interaction, and its psychological properties, is at the discretion of the platform employed.

While there are thousands of sales people that will graciously explain why one platform is more worthy than another, I will for once stay software agnostic and comment solely on the significance of the decision. As with any methodology, one platform may lend itself more appropriately to agile development (and the notion of continuous user involvement).