From the course: Agile at Work: Planning with Agile User Stories

Unlock the full course today

Join today to access over 22,400 courses taught by industry experts or purchase this course individually.

Producing acceptable documentation

Producing acceptable documentation

From the course: Agile at Work: Planning with Agile User Stories

Start my 1-month free trial

Producing acceptable documentation

- One of the sticking points with new Agile teams is deciding what is considered acceptable documentation. Remember from the manifesto that Agile projects prioritize working software. That doesn't mean that Agile projects produce no documentation. Instead, it should produce just enough documentation. After the Agile Alliance wrote their manifesto, they created a list of agile principles. Principle seven says, "Working software "is the primary measure of progress." Principle one says that you should "satisfy the customer through early "and continuous delivery of valuable software." You should think of this principle as really saying, "Don't deliver documentation "as a measure of progress." If you think about it, this makes a lot of sense. Try to image you're working on a large software project. So we start our projects the way most traditional projects start. We'll gather all of our requirements. A business analyst will work with the project stakeholders to create a comprehensive…

Contents