New teams to Agile some times struggle with the idea of "conversation over documentation". Many rely on exact instructions written in a traditional waterfall project (usually known as Business Requirement documents or BRDs) that are rigid and allow no flexibility. As the video below illustrates, exact instructions and documentation lead to frustration, miscommunication and delivery of an incorrect product. While relying on documentation, time is wasted, money is wasted and we are left with a dissatisfied client. In Agile, conversation is much more important than anything documented; we must allow "change" built into our product development, even late in the Development Life Cycle. Our documents are far less important than designing the correct product with client feedback.
Father- team of workers/Scrum Team
Children- Client/Product Owner
Product- Peanut Butter and Jelly Sandwich
https://www.youtube.com/watch?v=Ct-lOOUqmyY&t=134s
Visual representation of "communication over documentation"...
Comentários