# data[].attributes.headline
Documentation trought the Software Development Life Cycle (Document Late Strategy)

# data[].attributes.subject
Documentation trought the Software Development Life Cycle (Document Late Strategy)

# data[].attributes.body
Agile vs. Traditional development documentation through the SDLC

# data[].attributes.body
Agile Development Methodology: To Document or Not to Document? (nuclino.com)

Traditional Vs AGILE documentation

Agile/Lean

Documentation: Strategies for Agile Software Development

# data[].attributes.body
While Agile development methodology was created as an alternative to this documentation-driven development process, it did not set out to eliminate internal documentation completely. It simply placed more value on working software than on comprehensive documentation because of the dynamic nature of software development.

# data[].attributes.headline
Documentation in Waterfall (and others) 

# data[].attributes.subject
Documentation in Waterfall (and others) 

# data[].attributes.body
Project charter;

Vision statement;

Business Requirement Document (BRD);

Functional requirements;

Non-functional requirements:

Project plan;

Architecture & design;

Wireframes;

Test plan;

Deployment and maintenance plan;

# data[].attributes.body
Light documentation;

Evolving document;

Document communicates:

Documentation throughout the cycle;

User manuals:

Document ownership:

# data[].attributes.body
https://agilemanifesto.org/

# data[].attributes.body
Documentation should be “just barely good enough” (JBGE). Too much or overly comprehensive documentation would be a waste of time, and developers rarely trust detailed documentation anyway because it's usually out of sync with the actual code. On the other hand, experience shows that too little documentation is always a source of problems with communication, learning, and knowledge sharing.

# data[].attributes.body
Make sure it's always “just barely good enough”(JBGE). Keep in mind that any document you create you will have to maintain later on. If the documentation is light, uncomplicated, and not too detailed, it will be easier to comprehend and update.

Write it “just in time” (JIT). Wait before documenting – it's the best way to avoid accumulating false and outdated information. Produce documentation when it is needed, not before.

Keep it in one place and make it accessible. If documentation is only useful if it's accessible. Store your product documentation in a place where you and your team members can easily find it.

Collaborate with your team. Maintaining documentation in Agile teams is a collaborative process, and every team member should be encouraged to contribute.

# data[].attributes.headline
Agile adoption rates by Forrester Research in 2009

# data[].attributes.subject
Agile adoption rates by Forrester Research in 2009

# data[].attributes.headline
Documentation trought the Software Development Life Cycle (Document Continuuously Strategy)

# data[].attributes.subject
Documentation trought the Software Development Life Cycle (Document Continuuously Strategy)