JSG-driven scope, as defined in GitBook. We anticipate the home page for teams’ assignments to change, as at the moment it’s a mix of Squad description and time-sensitive tasks 🙂

Anyhow, there were some expected deliverables for our Group this week. This is what we were able to achieve:

General Management

Working on the writeup formalizing the WoW (way of working). This has been presented to Martin on April 8, waiting for feedback.

ACCESS_RIGHTS

Github Project Board: Requested research complete. Workers need write access rights as per [the official docs](https://docs.github.com/en/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization](https://docs.github.com/en/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization).

Github Project Board: Pinged JSG to request access. Waiting for response. Access Provided

WORKFLOW_FEEDBACK

• Test-Failed column seems redundant. If testing failed, leave a comment and move to Dev in progress.
• Why two Backlog columns? Community Dev and Bounties.
• Leave only one Code Review column to simplify the flow.
• No need for Merged on Dev column. Merged tickets to go to To Test.
• Rename Tested-Ready for Prod to Done :)

ENVIRONMENT_SCORE

Guides are been worked on / consolidated from elsewhere.