TimMo-dev / P7

1 stars 0 forks source link

Declare a way of working #12

Closed CHSten closed 4 weeks ago

CHSten commented 1 month ago

Description: Define the workprocess for the group. E.g. issue lifecycles, PR standards, scrum practices, etc. This should also be included in the report.

User Story: "As a AAU Software student i want to define the groups work process so we can process issues more systematically"

Acceptance Criteria:

Solution: A document named "samarbejdshåndsbog" describing our way of working has been made and been put in the files tab in P7 teams channel.

JakobTopholt commented 1 month ago

An agile approach is planned, with sprint, daily stand ups. Utilization of epic, artifacts and other such "rituals" are not planned. Sprint reviews and sprint retrospectives are planned to be merged into one reflection.

Sprints should be 2-3 weeks long.

Pair programming should be used as a tool to solve blockers.

Test driven development should be attempted, but discarded if not achieving the desired effect.

Planning poker will be attempted, and if deemed too time consuming discarded.

A group member will be named Product Owner, primarily being responsible for the backlog and organization of sprints, and one group member will be named Scrum Master, primarily being responsible for managing the daily stand ups.

More thoughts to be written later.

TimMo-dev commented 4 weeks ago

We should include something about how we use Github projects and manage different issues

TimMo-dev commented 4 weeks ago

For report related issues in "in review" status, it should be ruled that it has to be run through ChatGPT or grammarly

TimMo-dev commented 4 weeks ago

@mpmunch please review

JakobTopholt commented 4 weeks ago

May I do the review?