Re-reading the Agile Manifesto, Part Two

In my last post, I discussed a section of the Agile Manifesto that jumped out at me when I read it recently. I thought IÂ’d add another post on the Manifesto: ItÂ’s not a long document, but every word is carefully chosen to reinforce what agile stands for, so I think it merits some scrutiny.

Another line in the “Twelve Principles of Agile Software” section that spells out how agile leads to the delivery of the “right” product is:

     Â“Business people and developers must work together daily throughout the project.”

In the past, stakeholders and developers might never actually meet. Instead, a manager would relay vision to the development team, leaving plenty of room for misunderstanding. Clearly, conveying requirements becomes a game of telephone in this situation. But in the agile paradigm, business people and developers are asked to communicate not only at the outset of a project, but at every step along the way. The manifesto suggests they actually “work together daily.” With direct and continuous feedback from business people, there’s virtually no room for the team to misinterpret customer expectations or stray from that vision. In conclusion, agile helps build products customers truly want by getting stakeholders and developers to communicate directly and frequently.

Posted under Agile Methodology