Kharkiv Project Management Day Сергій Журавель “Documentation is not for Agile! Really?”

1. Documentation is not for Agile! Really?
Sergiy Zhuravel
Business Analyst at SoftServe
PMP, CSP, CSPO, PSPO

2. 1. Some cases
2. Why do we hate to create any documentation
3. MVP for documentation
4. Tips and tricks
Agenda

3. Working Software over comprehensive documentation
Good documentation is useful in helping people to
understand how the software is built and how to use it, but
the main point of development is to create software, not
documentation.
Agile seeks to minimize waste, so taken to its logical extreme,
all documentation is waste.
Some Agile…

4. I do not need any
documentation. I’m Agile.
Some Agile…

5. Some Agile…
Documentation
Discussion

6. Case 1 – Demo day

7. Who are you?
Where is my team?
Who is my manger?
What should I do?
What should I read?
What is a CID and NDC11?
A pushed my task into the default, cool?
How to setup the environment?
Case 2 - Newcomer
What is my project about?

9. Why do we hate to create any documentation?
What the … have you written?

10. To document this – Neeever!
Why do we hate to create any documentation?

11. I’ll write the documentation –
you will fire me
Why do we hate to create any documentation?

13. Some really shot documents list you must have
Why do we hate to create any documentation

14. Why do we hate to create any documentation?
I'll waste my time for
something useless
nobody cares

15. Why do we hate to create any documentation?
I often find processes with no consumers. Pure waste! Literally nobody uses the
output, but the producer doesn't realize it.
Michael Nygard

16. 1. Who is the consumer of the documentation?
2. What do they need?
3. How do you deliver it to them?
4. How do you know when they're ready for it?
5. How do you produce it?
6. What inputs do you need to produce it?
Questions before any action about documentation

17. 1. Communication plan
2. Vision
3. Newcomers guide
4. Glossary
5. (Budgeting and planning)
6. What Scrum/Kanban etc. do we have?
MVP for documentation

18. 1. Communication plan (who, how, when, what is a result?)
1. Perform a situation analysis;
2. Define your objectives;
3. Define your key audiences;
4. Identify media channels (meeting notes etc.);
5. Establish a timetable;
6. Evaluate the results (reports).
Tips and tricks

19. 2. Vision
Tips and tricks

20. 3. Newcomers guide
1. Start point for all basic documentation
2. Who are all these people? (name, photo, birthday,
contact etc.)
3. Some info about roles
4. …
Tips and tricks

21. 4. Glossary
1. Common project and processes terminology
2. Updated by newcomers as a part of adaptation period
3. Use links to web
Tips and tricks

22. 6. What Scrum/Kanban etc. do we have?
1. Do you really have Scrum? Really?
2. Define Scrum BUT part
3. Draw requirements -> feature workflow
Tips and tricks

23. Q&A

24. We really do not like to write useless docs.
Make it valuable for your and the team.
Sergiy Zhuravel
www.linkedin.com/in/zhuravels
www.facebook.com/sezhuravel