The traditional approach of having formal handoffs of work products (primarily documents) between different disciplines such as requirements, analysis, design, test, and development is a very poor way to transfer knowledge that creates bottlenecks and proves in practice to be a huge source of waste of both time and money. The waste results from the loss of effort to create interim documentation, the cost to review the documentation, and the costs associated with updating the documentation. Yes, some documentation will be required, but rarely as much as is promoted by traditional techniques. Handoffs between people provide opportunities for misunderstandings and injection of defects and are described in lean sof...
- Chapter 1. Disciplined Agile Delivery in a Nutshell
- from Disciplined Agile Delivery: A Practitioner’s Guide to Agile Software Delivery in the Enterprise
- Publisher: IBM Press
- Released: May 2012
Process Handoffs correspond to Lean internal clients.
Share this highlighthttp://www.safaribooksonline.com/a/disciplined-agile-delivery/1550597/