1. Documents
1.1. Product documentation
1.1.1. Product requirement document
1.1.1.1. Roles and responsibilities
1.1.1.2. Team goals and business objective
1.1.1.3. Background and strategic fit.
1.1.1.4. Assumptions
1.1.1.5. User Stories
1.1.1.6. Acceptance criteria
1.1.1.7. User interaction and design.
1.1.1.8. Questions
1.1.1.9. Not doing
1.1.2. User experience design documentation
1.1.2.1. User personas
1.1.2.2. User scenario
1.1.2.3. Scenario maps
1.1.2.4. User story map
1.1.2.5. UX style guide
1.1.2.5.1. Site maps
1.1.2.5.2. User flow / user journey schemes
1.1.2.5.3. Wireframes
1.1.2.5.4. Mock-up
1.1.2.5.5. Prototype
1.1.2.5.6. Usability testing reports
1.1.3. Software architecture document
1.1.3.1. Architecture & Design Principles
1.1.3.2. User Story description.
1.1.3.3. Solution details
1.1.3.4. Diagrammatic representation of the solution
1.1.4. Source code document
1.1.4.1. Example chapters
1.1.4.1.1. HTML generation framework and other frameworks applied
1.1.4.1.2. Type of data binding
1.1.4.1.3. Design pattern with examples (e.g. model-view-controller)
1.1.4.1.4. Security measures
1.1.4.1.5. Other patterns and principles
1.1.5. Quality assurance documentation
1.1.5.1. There are different types of testing documents in agile. We have outlined the most common:
1.1.5.1.1. Quality management plan
1.1.5.1.2. Test strategy
1.1.5.1.3. Test plan
1.1.5.1.4. Test case specifications
1.1.5.1.5. Test checklists
1.1.6. Maintenance and help guide
1.1.7. API documentation
1.2. Process documentation
1.2.1. Common types of process documentation:
1.2.1.1. Plans, estimates, and schedules.
1.2.1.2. Reports and metrics.
1.2.1.3. Working papers.
1.2.1.4. Standards
1.2.2. Agile product roadmaps
1.2.2.1. Strategic roadmap
1.2.2.2. Technology or IT roadmap
1.2.2.3. Release plan