Question

It sounds strange, but that’s what I need. An effective way to document a Scrum project.

I agree that it’s a waste of time to produce User Stories and a Requirements Documents.

But sometimes we need to have the vision of how the software currently works.

How do you do that? Do you know some best practices or case scenarios on this?

Thanks

Answer 1

The short answer is this: you can write anything you want or need to about any project, Scrum or otherwise. Scrum doesn’t tell you how to document, but it doesn’t tell you not to. The way you document is in itself irrelevant to Scrum.

That said, if you need to understand how the software currently works, a document will not help you. Documentation often lies. If you’re trying to understand how the system works, a document will only tell you what people think or want to believe is the truth.

What you should consider, is to use executable specifications and Test Driven Development to prove that what you believe the software does is actually true. automated tests combine documentation, examples and regression tests all into one offer.