Artefacts

Team Mission

Content of a Mission The mission covers the areas of responsibility (the What) and the culture and standards of behavior (the How). The mission clarifies the following points: What is our self-image. What is the purpose of the team? How does the team position itself within the cluster and the organization? What are the responsibilities…

Team Tasks

Team Tasks are activities and actions that a Working Team plans and carries out in order to achieve Team Goals . Team tasks are not part of the Team-Backlog, but part of the Team-Iteration Backlog and are usually created and planned in the Team Planning event. . Further suitable links: Events Roles Groups Artifacts Team…

Team Goals

Team Goals are the most used elements of the Team Backlog . They describe the goals and (interim) results of the team regarding a Feature, a Module or a Service , depending on the type and responsibility of the Team . Generally speaking, the Working Team turns Team Goals into Inspectable Results. Within an Iteration…

Technical Reviews

When can the Team get technical feedback? Problem: Within the relative short Iteration Review it is potentially not possible for the Stakeholders to give profound technical feedback. So, how can the Team get technical feed from the Stakeholders, discuss and decide with them as fast as possible? Technical Reviews during the same Iteration Review directly…

test_c

Mid-level artefact C. Inherited (included): Highest level artefact A. Highest level artefact b.

test_d

Low-level artefact D. Inherited (included): Mid-level artefact C. Inherited (included): Highest level artefact A. Highest level artefact b.

Use Case

Use Cases are used to describe scenarios in which users and other stakeholders interact with the system. Use Cases are a good method for describing functional requirements and dynamic behavior of the system. Many non-functional requirements can also be discovered during the analysis. In order not to forget any essential Use Cases during the requirements…