Skip to Content
Software Architect's Handbook
book

Software Architect's Handbook

by Joseph Ingeno
August 2018
Beginner
594 pages
22h 33m
English
Packt Publishing
Content preview from Software Architect's Handbook

Using a backlog to track the architecture design progress

A product backlog contains a complete list of the features and bugs of the product. You should consider creating a product backlog that is specific to the software architecture of the project, which is separate from the other product backlog. An architecture product backlog would contain items, design issues, design decisions that need to be made, and ideas that are specific to the architecture design.

Prior to each sprint, sprint planning takes place. The team selects items from the product backlog that they will work on and complete during the upcoming sprint. Once tasks can be created for the product backlog items, they can be assigned to a resource and then tracked for progress. ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

Solutions Architect's Handbook

Solutions Architect's Handbook

Saurabh Shrivastava, Neelanjali Srivastav
Solutions Architect's Handbook - Second Edition

Solutions Architect's Handbook - Second Edition

Saurabh Shrivastava, Neelanjali Srivastav
Software Architecture in Practice, 4th Edition

Software Architecture in Practice, 4th Edition

Len Bass, Paul Clements, Rick Kazman
Solutions Architect's Handbook - Third Edition

Solutions Architect's Handbook - Third Edition

Saurabh Shrivastava, Neelanjali Srivastav

Publisher Resources

ISBN: 9781788624060Other