QA (public) » openQA Project (public)

Motivation¶

Let's discuss how #179038 took that long

Background¶

So what happened?

Questions¶

1. Why did the ticket take that long
   • A1-1: Mostly because the "wrong approach" involving retries was taken in the beginning
   • => I1-1-1: See I2-1-1
   • => I1-1-2: Do more TDD, for real, don't cheat, real TDD, we mean it!
   • A1-2: Also because implementing the code review suggestions took long
   • => I1-2-1: We should try more focused team-work also supported by a Scrum Master in each (small) team
   • A1-3: Because of misunderstanding test code mocking something …
   • => I1-3-1: Do TDD, see I1-1-2, seriously
2. Why was the "wrong approach" using a for-loop taken?
   • A2-1: Maybe the ticket description was not read or followed properly
   • => I2-1-1: Remind ourselves to read ticket descriptions carefully and crosscheck that in dailies
   • A2-2: Being unfamiliar with the code and in particular the "minion" framework
   • => I2-2-1: Use the collab sessions or do pair-programming or ask for code walkthroughs more often
3. Why was the "whole thing" implemented even though during refinement we clearly split out #179185 "Detection of long-time remote git clone outages"?
   • A3-1: Because the collab sessions did not help|effective
4. Why did the collab sessions not help?
   • A4-1: Because there were often new code review comments coming up
   • => I4-1-1: See I5-1-1
   • A4-2: We were too confident with the approach
   • => I4-2-1: Cross-check more often if the taken approach is still correct, e.g. in dailies be more specific about steps planned
5. Why did new code review comments come up repeatedly?
   • A5-1: Because only during code review it became apparent that the "single file" approach will not work with multiple git providers
   • => I5-1-1: Rather than 100+ github PR comments do more pair-programming sessions

Acceptance criteria¶

• AC1: A Five-Whys analysis has been conducted and results documented
• AC2: Improvements are planned

Suggestions¶

• Bring up in retro
• Conduct "Five-Whys" analysis for the topic
• Identify follow-up tasks in tickets
• Organize a call to conduct the 5 whys