Everyone loves good software, technical, product, project, or user documentation, but no one likes writing them. This deck makes a case for making the creation and maintenance of such documents a shared activity, not the sole responsibility of a single team member. It also includes ideas that you can use to streamline your documentation projects and tasks.

1. AGILE
DOCUMENTATION

2. Is facing an identity crisis
2

3. In the age of agile
3

4. Agile + Docs = ?
4

5. Traditional vs agile: what to doc?
5

6. Traditional vs agile: when to doc?
6

7. Doc the right things at the right time
7

8. Everyone <3 good docs...
but no one wants to write them
8

9. Everyone <3 good docs
Docs are necessary to:
▷ Foster understanding
▷ Facilitate quick onboarding
▷ Future-proof changes
9

10. It’s ok to...
create as little as needed
10

11. It’s ok to...
▷ Follow the 80/20 rule and doc essentials
▷ Make WIP docs available for peer review
▷ Crowdsource the docs
Creating and maintaining docs should be a shared
activity; not the sole responsibility of a single team
member (like the business analyst)
11

12. Doc it or it didn’t happen
12

13. What should we doc?
▷ Context for the problem you’re trying to solve
▷ Overview of the change you’re making
▷ Decisions made
▷ Consequences of actions
▷ Parts of the system with lots of history
▷ Things that will hurt in the future if forgotten
13

14. Credits
▷ Presentation template by SlidesCarnival
▷ Slide 2 image
▷ Slide 3 image
▷ Slide 5 image
▷ Slides 6 & 7 image
14

15. Thanks for your time!
Have questions, comments or feedback?
Please feel free reach out to me on LinkedIn.
15