Does Agile Development Mean That No Documents Are Written

If it is understood that no documentation is needed after agile development, it is a great misunderstanding of agile development.

The focus of agile development is light documentation rather than documentation.

And this kind of light I also said, for new system development, it is best to start with a general plan or architecture.

For how to understand light documents, I suggest you look at product backlog and sprint backlog in scrum.

Note that this is a form of documentation, and this document includes requirements, business scenarios, implementation ideas, validation and test methods, estimation, and so on, which are traced back to user story.

Instead of dividing it into multiple documents according to traditional software engineering thinking.

Agile development focuses on communication and documentation.

The document must be moderate, which can neither be a burden to the project team, but also need to be examined when there is controversy.

First, the requirement document is divided into two parts.

Of

This document does not need to be too meticulous, because product managers organize language to write documents, develop documents, and understand documents. They consume a lot of time, preferably in a general way. They develop frequent communication with product personnel when designing requirements, and eventually form a complete document together. This intermediate developer and tester have a great contribution to document rigour, and do not require product managers to write all the boundary details.

On the other hand, as a good

Habit, any communication conclusion should be archived! Mail is a good form.

At the end of each meeting, do you ask a conclusion? Who does the minutes? It's not that the documents are not important. Instead, it is through meeting and communicating that we need to reach a consensus on the details that need to be described in the document.

The detailed design is based on the logic of difficulty and size.

Logic complex projects, summary design as a means to help develop and understand needs.

For large projects, detailed design is inevitable.

In a word, the demand for scale should be done at will.

All of these must be communicated in person. The premise is that the project members should not be too rigid, but also have some running in and strong abilities.