Has your team made the transition from a traditional requirements document to user stories and backlog items? Or perhaps there are no requirements? Debating about the level of detail in a user story and acceptance criteria?
If your team is constantly debating what to document or struggling to explain to others why you are and are not documenting things you used to, this session is for you!

The big question many teams have is "What does need to be documented?"

This session will explore the various factors that go into why teams feel the need to document and not document. It all comes down to the value and purpose of the documentation and how well aligned to the agile values your team really is. Many times teams have a legitimate need to document more than another team if aspects of their team stretch the agile values of co-location, and work-in-progress. We will look at what agile values contribute to the documentation conundrum helping you make and facilitate better decisions about documentation.

Learning Objectives:

• Evaluate the drivers and context for documentation needs and its value to others
• Distinguish what team models and agile values influence documentation needs
• Look at common reasons teams document and dispel myths of documentation