Skip to content
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.

Document the responsibilities of squad leads #102

Open
nottrobin opened this issue Nov 20, 2018 · 0 comments
Open

Document the responsibilities of squad leads #102

nottrobin opened this issue Nov 20, 2018 · 0 comments
Assignees

Comments

@nottrobin
Copy link
Contributor

nottrobin commented Nov 20, 2018

Some suggestions of such responsibilities:

  • Explain the required elements that must be presented in the squad's Backlog spreadsheet
    • Tasks in the current iteration
    • Status of tasks
    • Points? Maybe not?
  • Define the meetings before which the Backlog spreadsheet must be up-to-date:
    • The "end-of-iteration demos" meeting
    • The "management iteration planning" meeting
    • The "scrum of scrums" meeting
  • Prepare (and email around?) a 1- or 2-paragraph summary of what the squad achieved in the last iteration. These paragraphs can then be included in the email / blog post that the design team put out about the completed iteration.
  • The internal running of the squad, the planning meetings, management of tasks etc., is up to the individual squad lead. But also suggest some patterns:
    • Pre-planning and planning meeting
    • Retro meeting
    • ZenHub? GitHub projects? Whatever you like?
    • Suggested kanban board lanes
    • Suggested stand-up format
    • Using points and velocity?
@nottrobin nottrobin self-assigned this Nov 20, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant