Iteration Training - Alina Mihaila
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 - FY##Q#
Review
-
Minimal Viable Change (MVC) -
Iteration -
Move Fast -
Product Processes: Iteration Strategies -
Cross-Culture Collaboration Guide. It is important to be aware that while iteration is a company value at GitLab and at the core of how we operate, iteration does not come easily for all people. By understanding how different cultures and groups approach iteration and the learning curve associated with adapting to an iterative work culture, we can collaborate from a more empathetic lens. While the content in the guide does not explicitly focus on iteration, generating awareness around things like Collaboration Focus
(task-oriented or relationship-oriented) directly relates to the speed at which people ship.
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. (Consider leaving a comment in this issue with the link to the document or async issue) -
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. -
Using the results of these discussions, choose a piece of work that's ready for development and discuss how it could be better iterated on. -
Identify areas of improvement for the team and incorporate into your Product Development Workflow. Consider to schedule a review on the results in a few months later. -
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 Optional
-
-
If you are a manager, consider encouraging your team members to complete the 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?
- Be sure to note this in the team retro and how you would have approached this differently through the lens of iteration
- If this happens regularly, schedule 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? -
Consider scheduling a task to review your MRs at the end of each milestone. How many could have been broken down into smaller iterations? -
(Optional) Add a comment to this issue linking to an issue/MR where you proposed breaking down the feature into smaller iterations.
Edited by Alina Mihaila