Frequent Feedback

Having “working software” on an almost daily basis enables frequent feedback (virtually continuous feedback if wanted). Any feedback received that requires rework should keep the amount of rework small and manageable and, thus, more likely to actually be acted upon. Conversely, if overwhelming feedback is received late in the project, teams may delay responding to the feedback until a subsequent release—or even ignore it altogether. Working software, with frequent feedback, aligns with another agile principle: “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”5

5. Taken from the “Principles Behind the Agile Manifesto”: http://agilemanifesto.org/principles.html. See also ...

Get Being Agile: Eleven Breakthrough Techniques to Keep You from “Waterfalling Backward” now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.