Reply to comment

David Wright
,
posted 13 weeks 6 days ago

the 'requirements' document

It is the dreaded 'requirements document' that agile approaches value less than working software. The other examples are about the formalities needed when spending lots of money to acquire a solution, doesn't matter if it is buy, rent, or build. The one artefact that is missing is project scope, so you can evaluate potential stories as being relevant or not to the objectives of a solution.

Reply

Shopping cart

There are no products in your shopping cart.

0 Items