Exercise – backlog management in GitHub

In Chapter 1, we learned about why it is essential to track our activities, user stories, change requests, and bug fixes on any code base. Let’s recall the key takeaways:

• We want to plan our developer work in every sprint ahead to laser-focus on the most critical features, bugs, and defects. The entire sprint planning process is based on a healthy product backlog that every developer and product owner needs to maintain.
• Healthy backlog management allows only source code changes that are planned to avoid gold plating (developers adding extra features that are not part of the activity) and scope creeping (when a project team works on features that are requested by the customer without adjusting the project’s cost or timeline).
• Backlog management provides backward traceability as well as the ability to trace back from the application running in production to the source code that produced the binaries of the application...