Читать книгу Agile Auditing - Raven Catlin - Страница 26

Scrum Artifacts represent work value. Following are the three Artifacts, or documents, created in the Scrum framework (Sutherland and Sutherland 2014). Each of the three Scrum Artifacts has a corresponding commitment to drive focus and alignment. This commitment gives the teams a much better focus on the specific goals. The Artifacts are:

1 Product Backlog (see Chapter 8, Implementing Agile Auditing: The Audit Planning Process). The Product Backlog is a list of requirements and features for a project that is managed by the Product Owner in order of business priority. Product Backlogs include estimates on business value and development efforts. The commitment for Product Backlog is Product Goal.

2 Sprint Backlog (see Chapter 9, Implementing Agile Auditing: Planning Agile Audit Engagements). The Sprint Backlog is a specific, focused list of tasks the Delivery Team believes it can complete in a Sprint. It is created by the team members, using a pull approach to complete an increment. Contrasted with a push approach, where an input is pushed into a cycle in hopes that it can be used as it is pushed, or can wait until it is needed, a pull approach pulls inputs into the process or production line on demand, as needed. The push approach may result in excessive production and unused work, while the pull approach is quick and efficient. The commitment for Spring Backlog is Sprint Goal.

3 Increment. An increment is production output at the end of a timeboxed Sprint. The commitment for increment is the Definition of Done.

We acknowledge that some Scrum adaptations include up to six Artifacts, or documents. However, creating more Artifacts that do not add value or that are otherwise created simply for the sake of creating more Artifacts does not align with the Agile Manifesto value of “more working software, less documentation.”