Working Software over Comprehensive Documentation. Does this mean there is no need to generate any document while delivering a project using Agile? Not really, here’s the list of document that should be generated while delivering a project using Agile,
Vision Statement defines the ultimate goals of a project and the why. Why we’re building this project
Project Overview summarizes critical information about a project such as the Vision, Technologies used and Operating processes. It should be just a few pages long
Requirements Documentation are helpful and even essential to have. Product requirements may be documented in many different forms, including for example the Product Backlog
Acceptance Testing Documents are also helpful. Acceptance criteria is used by testers to determine whether the requirement has been met. Acceptance Testing Documents specify those acceptance criteria, and they help tell developers whether their work is done. Remember definition of done?
Support Documentation is designed for those who will be responsible for supporting the product once it’s released. It may include Problem Escalation Procedures, a list of Important Contacts and a Troubleshooting Guide.
User Documentation may include Training Manuals, User Manuals and Quick Reference Cards. It’s designed to equip users to use a product and to find answers to their FAQs without having to call support staff
ALL THINGS AGILE
Do Agile projects work without Requirements Specifications or Spec?
Definition of Done in Scrum
SHOP FOR PMP AT AMAZON INDIA
CONTRIBUTE TO PMC LOUNGE