Iteration Training - Tim Rizzi - Q22020
Iteration Training
Iteration is one of six GitLab Values. This template is intended to be an onboarding introduction to new team members, and a refresher for those who have been with GitLab.
Steps
-
Assign this issue to yourself with the title of Iteration Training - First Name Last Name - Q#YYYY
Review
Watch
-
Interview about iteration in engineering with Christopher and Sid -
Iteration Office Hours with CEO -
Youtube playlist with collected iteration content Optional
Actions
-
Join the Iteration Office Hours regular meeting on GitLab Team Meeting Calendar -
If you are a manager, hold an iteration retrospective with your development group -
Discuss past examples of successful iteration. Why was it successful? How did it meet the definition of an MVC? -
Discuss past examples that could use improvement. How did the example not meet the definition of an MVC? In what ways could you have iterated differently? List specific examples. -
Identify areas of improvement for the team and incorporate into your Product Development Workflow -
Update your teams handbook page with ideas and improvements you've incorporated to improve iteration -
Update this training template to iterate and improve on our iteration training
-
Questions to ask yourself
- During planning - is the task the smallest thing possible? If not, cut the scope.
- At the end of the milestone - did something slip because it was too big? If so, consider having an iteration retro.
Self assess
-
We use Google Docs as a communication standard. Review your recent documents and proposals. How many of them could have [started with an MR]?(https://about.gitlab.com/handbook/communication/#sts=Everything%20starts%20with%20a%20Merge%20Request) -
Review your recent merge requests. How many could have been broken down into smaller iterations?