Skip to content

New Proposed Outline #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 11 commits into from
Empty file.
Original file line number Diff line number Diff line change
@@ -1,13 +1,17 @@
# Use Done-Done checklist

Software Engineering is not just implementing functionality and writing code, but also other associated tasks and activities to ensure all requirements are fulfilled when you finished your work. This is closely relevant to `done-done` term, which stands for a simple list of activities like writing code/unit tests/release notes/design docs and so on that adds verifiable/demonstrable value to the product.

Below is an example Done-Done checklist you should follow to ensure everything is done (may vary depending on project/client):
* Is covered by unit and integration tests YES/NO
* Is continuously tested in each environment YES/NO
* Is sufficient diagnostic/user telemetry and dashboarding YES/NO
* Is sufficient public documentation YES/NO
* Feature owner sign off YES/NO
* [if applicable] Customer value demo screencast is recorded and sent to the team
YES/NO
* [if applicable] Is Relevant architectural review is done YES/NO
# Team Definition of Done Agreement

## Content TODO's

- Solidify recommended checklist as opposed to providing example (see [cobalt](https://github.com/microsoft/cobalt/wiki/Definition-of-Done) definition of done)

Software Engineering is not just implementing functionality and writing code, but also other associated tasks and activities to ensure all requirements are fulfilled when you finished your work. This is closely relevant to `done-done` term, which stands for a simple list of activities like writing code/unit tests/release notes/design docs and so on that adds verifiable/demonstrable value to the product.

Below is an example Done-Done checklist you should follow to ensure everything is done (may vary depending on project/client):
* Is covered by unit and integration tests YES/NO
* Is continuously tested in each environment YES/NO
* Is sufficient diagnostic/user telemetry and dashboarding YES/NO
* Is sufficient public documentation YES/NO
* Feature owner sign off YES/NO
* [if applicable] Customer value demo screencast is recorded and sent to the team
YES/NO
* [if applicable] Is Relevant architectural review is done YES/NO
8 changes: 8 additions & 0 deletions 0000-pre-sprint/team-agreements/definition-of-ready/readme.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# Team Definition Of Ready Agreement

## Content TODO's

- Define criteria for a story to be ready to pull into a sprint.
- Examples
- Has estimate
- Team understands implementation/design
8 changes: 8 additions & 0 deletions 0000-pre-sprint/team-agreements/estimation/readme.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# Team Estimation Agreements

## Content TODO's

Recommend sizing scale such as fibonacci
Pick stories to establish baseline (example below assumes fibnonacci)
- What story represents 5
- What story represents 2
Empty file.
Empty file.
Empty file.
29 changes: 29 additions & 0 deletions 0010-day-one/sprint-planning/readme.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
# Planning

## Content TODO's

- Complete outline below
- Determining team capacity
- Tasking sprint stories
- size of tasks
- WIP limits / dividing up into workstreams

## Goals

What are the intended outcomes of the ceremonies?

## Participation

What members of the team should participate?

## Impact

What positive impact has been observed as a result of this practice?

## Measures

How might one measure the impact of this ceremony positive or negative?

## Facilitation Guidance

How might one go about running the ceremony? Is there a general pattern that the ceremony should follow?
Empty file.
Empty file.
23 changes: 23 additions & 0 deletions 0020-day-two/scrum-of-scrums/readme.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
# Scrum of Scrums

For those that may be unfamiliar (until the content below is completed)... [Scrum of Scrums](https://www.agilealliance.org/glossary/scrum-of-scrums)

## Goals

What are the intended outcomes of the ceremonies?

## Participation

What members of the team should participate?

## Impact

What positive impact has been observed as a result of this practice?

## Measures

How might one measure the impact of this ceremony positive or negative?

## Facilitation Guidance

How might one go about running the ceremony? Is there a general pattern that the ceremony should follow?
26 changes: 26 additions & 0 deletions 0020-day-two/stand-ups/readme.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
# Standups

## Content TODO's

- Complete outline below
- Define what should and should NOT be in the standup update

## Goals

What are the intended outcomes of the ceremonies?

## Participation

What members of the team should participate?

## Impact

What positive impact has been observed as a result of this practice?

## Measures

How might one measure the impact of this ceremony positive or negative?

## Facilitation Guidance

How might one go about running the ceremony? Is there a general pattern that the ceremony should follow?
Loading