Appendix D. Example: determining process and document needs for a project
Throughout the book we have mentioned the need for the project team to determine the documentation and processes required for each project. In the example below we show an example from a real team. This team worked in a regulated environment and had to provide requirements traceability. Note that they revisited this matrix at the start of each project to reach agreement on what the deliverables would be. This matrix was originally one spreadsheet, but we have broken it into two pages to make it easier to view within the book.
Also note some unique terms used by this team: BRQs (Business Requirements), FRQs (Functional Requirements), FS (Functional Specification), and Ux (User ...
Get Becoming Agile now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
