This page outlines the Builders Squad’s perspective on the way of working and communication scheme between the Builders Squad and Jsgenesis, or JSG.

We have been trained in centralized, linear, rational, top-down, hierarchical control protocols. How might we unlearn the dogmas of methods and re-train ourselves to apply these methods anew or rearrange them toward the creation of altogether new methods? Travis Wyche, DeathGuild

0. Status of the Squad and Squad workers in JSG setup

1. Weekly sync with JSG

2. Product Owner role

3. Proxy Product Owner Role

4. Project 55 vs Project 56

These two Github Projects are the main source of work for Builders. It means no JSG person (or CM, for that matter) can task the Builders with some piece of work that’s not in one of these projects. Moreover, tasks for Project 56 need to be made known to JSG at least one Term in advance, so the hours burned for them come at no surprise in the Squad report.

5. Backlog

To increase transparency and traceability, all tasks coming from JSG stakeholders must first land in Community Github Project backlog. By default, all new backlog items have low priority.

Builders Lead checks the backlog daily for new items.

Builders Lead Proxy PO works with JSG Product Owner to prioritize backlog items.

Builders Lead together with the Workers works out tasks estimates (in [Story Points](https://www.atlassian.com/agile/project-management/estimation#:~:text=Story points are units of,work%2C and risk or uncertainty.), and potentially in $JOY)

Higher priority backlog items are moved to top, lower priority items are moved to the bottom.

Workers are assigned tasks from the top of the backlog, and move them to In progress swimlane.

6. Grading and Evaluations Challenges

Three principal constituents of the Builders Squad Score are TESTING_SCORE , GENERAL_DEVELOPMENT_SCORE and PIONEER_DEVELOPMENT_SCORE. Builders Lead to make sure these parameters are as close to 1 as possible.