Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add retrospective template. #87

Merged
merged 1 commit into from
Nov 23, 2017
Merged

Add retrospective template. #87

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 35 additions & 0 deletions templates/retrospective.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# Retrospective Checklist

- [ ] Decide who is taking notes and who will write the report (usually this is the scrum master).
- [ ] Start recording the meeting.
- [ ] Go through the demos.
- [ ] Every Nitean talks about "What was good", "What was bad" and "What we could do differently".
- [ ] Go through the user cancelation list.

# What went well during the sprint?
...

# What went wrong during the sprint?
...

# What could we do differently to improve?
...

# Other comments.
...

Planned:

- Committed Story Points: X
- Marketing & Operations: X
- Feature: X
- Bug & Cleanup: X

Done:

- Committed Story Points: X
- Marketing & Operations: X
- Feature: X
- Bug & Cleanup: X

[Screenshot of the burndown chart]
4 changes: 4 additions & 0 deletions work-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -188,6 +188,10 @@ After each sprint, we do a retrospective. We think about:
We also add a note on how many Story Points we assigned, how many were done and the distribution between the departments and types of User Stories.

Last Retrospective agenda should be going through the [cancellation reasons of our VIP users](https://github.com/niteoweb/support/blob/master/EBN/cancellation-analysis.md) (Agency plan and above). Since they are our primary customers, we want to know why they're leaving and see if there are any actionable reasons.

Before each Retrospective scrum master creates a new issue. Use the [retrospective template](templates/retrospective.md) for this.

This template serves as a checklist for Sprint Retrospective. After the meeting scrum master briefly writes a report and this template helps him with that.

## Scrum

Expand Down