Teaming Helper
Role Descriptions
Role 1: The Driver:
- Ask a clarifying question about what to type
- Type something you disagree with
- Use a keyboard shortcut
- Learn something new about the tooling
- Ignore a direct instruction from someone who isn't the navigator
- Cross your arms and look sad when you don't have anything to type
Role 2: The Navigator:
- Ask for ideas
- Filter the group's ideas and tell the driver exactly what to type
- Tell the driver only your high-level intent and have them implement the details
- Create a failing test, make it pass, refactor.
Role 3: The Nose:
- Point out repeated code
- Point out a long line of code
- Point out a complex conditional
- Propose an action for removing a code smell
- Identify a missing test case
Role 4: The Researcher:
- Find and share relevant documentation
- Find and share relevant information from a blog
- Find and share relevant information from a coding forum
- Find and share a keyboard shortcut for the tool
Role 5: The Robot:
- Point out a repeated task in a tool
- Point out a repeated aspect of the team process
- Point out possible boilerplate code
- Propose automating a repeated task
- Propose pipeline improvements
Role 6: The Archivist:
- Draw up a plan on a visible chart/whiteboard/task list
- Express an idea as taking shape using a visual medium
- Articulate the current task at hand and make it visible to the group
- Encourage and update the ReadMe
Role 7: The Cop:
- Make sure the tests are run and green
- Point out when the team violates a process or working agreement
- Capture design decisions and other technical details for the team
- Watch out for fatigue or disinterest and bring people back into the group
- Call out when people are not being heard or allowed to finish
- Encourage naming conventions