XP2019 has ended
Back To Schedule
Thursday, May 23 • 3:30pm - 5:00pm
The Art of Agile Documentation (David Sabine)

Sign up or log in to save this to your schedule, view media, leave feedback and see who's attending!

A Sense-making workshop to simplify valuable documentation & reduce wasteful documentation.
Myth: "Agile teams don't document."
Truth: Agile teams produce excellent and valuable documentation.
Agile Engineering practices have revolutionized the ways in which documentation is treated and produced. In high-stakes environments with heavy compliance and audit requirements, a tendency toward exhaustive documentation is dangerously common. This workshop provides direct guidance and simple tools to help a document-heavy workplace think differently about documentation.
I have developed this workshop to help an organization reframe their understanding of documentation with respect to knowledge work in complex environments so that they may eliminate unnecessary artifacts and simplify/automate others.

Learning Outcomes:
  • Attendees will:
  • 1. Reframe their understanding of documentation with respect to knowledge work in complex environments. (Documents are not truth. They are snapshots of current understanding. If not treated carefully, they create fiction not transparency.)
  • 2. Reframe their understanding of 'implementation' — when does it occur in product development? (Hints: it isn't a phase or project milestone; it is every moment in which a decision is codified in *the product*.)
  • 3. Compare the purpose of artifacts/documents produce pre and post implementation. (Documents pre-implementation do not represent decisions; they represent, at best, incomplete information. Documents create at or after the point of implementation are obsolete the moment they are produced.)
  • 4. Appraise commonly-used documents with respect to customer-value -- in contrast to perceived business/process 'importance'. (Documents are often produced because someone demanded they be done; but many documents are not the artifacts that any customer is willing to pay for. How might we focus on documentation which has actual value?)
  • 5. Consider and describe ways each artifact may be eliminated or simplified. (Like eliminating a Business Requirements Document in favour of a flexible/dynamic Product Backlog, how might an Agile team simplify the design and production of necessary artifacts/documents.)

avatar for David Sabine

David Sabine

Professional Scrum Trainer
David, as Professional Scrum Trainer with Scrum.org, works to improve the profession of software delivery. He helps organizations deliver products of the highest possible quality and value. His career highlights the intersection of business, technology, fine art, and education. With... Read More →

Thursday May 23, 2019 3:30pm - 5:00pm EDT
E-4025 (4th Floor)