Travelling light – The pros and perils of lean documentation

Have you ever been on a long haul overseas trip, where you loaded your hand luggage with items like laptops, books and electronic devices – just to make sure that you weren’t bored on the flight? Only to be left trudging around airport duty free shops while waiting for a connecting flight, wondering why you feel like you packed bricks in your backpack…

Projects carry a lot of baggage too… documentation. Someone has to create it, someone has to read it, someone has to sign it, someone has to (or is meant to) maintain it, and eventually someone needs to figure out if it is still valuable. That’s a lot of work for something we might not even use!

Agile approaches value working software over comprehensive documentation. But what does that really mean?

Join me as we explore:
- The principles of lightweight documentation
- The difference between short-lived, low fidelity documents and long-lived, high fidelity documents
- When do we produce documents on an agile project?
- How much is enough?

1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

- An incredibly brief history of why people write things down.

- Why so much documentation was needed in Waterfall/ traditional approaches. And why Agile is different.

- How to ensure that your document is correct, will be read, is understood, will be followed (without "throwing something over the fence"), and trusted by your readers.

- The difference between short lived (low fidelity) and long lived (high fidelity) documentation - and knowing when to use which type.

- How to write a document using an Agile approach (using the Madman, Architect, Carpenter and Judge - a process proposed by Betty Flowers). 

- 10 tips for writing great short lived and long lived documents! 

Learning Outcome

- Learn the principles of lightweight documentation

- Learn how to identify which documents are important, and which ones may be wasteful

- Learn how to identify when enough is enough 

Target Audience

Agile Business Analysts, Product Owners, Scrum Masters, anyone interested in Lightweight Documentation

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal