[Task]: Way of working documentation updated

[sumiat]

Summary

As our team is growing there are a lot of questions how we should create tickets, how we should handle new or unplanned tickets in sprints, etc. We should have this in the wiki and could fit somewhere under this space: https://app.gitbook.com/o/cFcvhi6d0nlLyH2VzVgn/s/v1V0jIH7mb7Yb3jlNrgk/collaborating/communication-channels/github-project-and-ticket-management

Topics to add to the wiki:

• ticket creation process: who can create tickets (everyone!), where are tickets created, how should they be labeled
• documented that we do story point a ticket before work is started on it
• are we updating the ticket regularly? how often? should we leave comments or is the PR enough?
• handling new/unplanned tickets: mid-sprint, bug fixing
• regular reporting on sprint progress and velocity

Acceptance criteria

• [ ] Documentation updated in the wiki with the above potential topics and shared to review with leads and team

[EOKENAVA]

@sumiat - Find here a draft of the way of working documentation - https://app.gitbook.com/o/cFcvhi6d0nlLyH2VzVgn/s/v1V0jIH7mb7Yb3jlNrgk/planning/way-of-working

[EOKENAVA]

I did separate the reporting aspect from the document as it is a bit loaded and needs input from A6

[sumiat]

thanks @EOKENAVA! Added some comments and feedback here: https://app.gitbook.com/o/cFcvhi6d0nlLyH2VzVgn/s/v1V0jIH7mb7Yb3jlNrgk/planning/way-of-working/~/comments/avcjEsfnYSSTrEGQ4lnu?node=nFszY37FHj31 and https://nava.slack.com/archives/C05E2HK61TJ/p1708451940742319

[margaretspring]

Putting back into Icebox to be addressed by Henry (starting 10/15) or myself when things settle a bit from transitioning into restart project.