Utilization Iteration Retrospective
Iteration is one of six GitLab Values, but also really difficult. By focusing how we have iterated well (or not so well) in the past and how we have not will help us iterate faster. Please contribute the following Iteration Retrospective.
Summary
Epic &4547 GitLab.com Billable Members List
Details
- Did the team meet the iteration goals? Why or why not?
Yes, the goals as they've been set appear to be on track. There is work currently planned through the upcoming 14.1 Milestone with some previous issues extending all the way back to the 13.5 Milestone.
The Epic appears to be well organized and contains few clarifying comments.
- How many MRs were created to complete the Iteration?
To date, there are 36 MRs for this epic
- What were the Days to Merge for the MRs related to the MR?
The Mean Days to Merge was 7.4 days. Min: 0, Max: 38
google sheet
MR Table
- Are there successes or opportunities for improvement with respect to collaboration with peers or stable counterparts?
Moved to a comment thread
- Could the original issue have been broken down into smaller components?
Consider this when responding to the comment threads
- Could the MR(s) have been broken down into smaller components?
Consider this when responding to the comment threads
Tasks
Read
Watch
Contribute
In the threads below consider the following:
- Why was it (un)successful? If successful, how did it meet the definition of an MVC?
- 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 that can be incorporated into our processes and workflows.
Follow these rules for an effective retrospective.
Check your name off the completed list when all tasks are complete.
Completed
Next Steps
-
Engineering Manager to update your team's handbook page with ideas and improvements you've incorporated to improve iteration.
Thread Prompts
- What aspects of the Issue/Epic and resulting MR(s) were very good/bad examples of Iteration and why?
- Does anyone have alternative ideas for how this work could have been broken down?
- Is there anything that we can change in our processes or the way we work that could improve our iteration as a team?