Team contract

The developed product is defined by numerous milestones/requirements. Each milestone is composed of multiple issues/user stories, which in turn contain specifications and concrete boundaries pertaining to the associated code-implementation. The picture below illustrates the defined guidelines for the grouping of milestones, issues and code:

Milestones - Grouping of functionalities/requirements

• Each milestone has a header Functionalities where the contained requirements are disclosed

Issues - Agreed convention/path of completing fractions of milestones

• Each issue has two headlines with the following content:

• Requirement --> A user story uncovering a persona's desires related to the system in the format as a < persona >, I want to < goal > so that < reason >. If an issue is dependent on functionality originating from other issues, it is also mentioned in this section

• Acceptance criteria --> A functionality-breakdown of the aforementioned user story that serves the purpose of eliminating ambiguouty in the questioning of whether or not the newly implemented feature satisfies the user story to its fullest extent or not

Lastly, upon creation of an issue, the following actions must be done:

• Set due date serving as a final deadline to complete it
• Assign labels defining current state, purpose and priority of it

Labels - Agreed convention of structuring issues

The foundational system for distinguishing the importance of the existing issues in conjunction with the predetermined plan possesses 4 distinct categories and 14 unique tags:

Commits

TODO

Merge requests

TODO

Closing issues

TODO

Branches

TODO

Kanban board

TODO

Code

• Each issue has a code-implementation