Sprint 2 Retrospective

What Went Well

  1. We developed a fully interactive Telegram bot prototype with functional navigation and mock responses
  2. We received a clear feedback from the customer.
  3. Update QAST

Problems Encountered & Solutions

Problem 1

Description

  • Extended time required for feature implementation.

Root Cause

  • The team lacked the specific technical skills needed.

Solution Applied

  • Redistributed workload by reducing other responsibilities for the primary developer.

Problem 2

Description

  • the lack of first steps to implementation in issues.

Root Cause

  • Issues were created based on user stories, but no user stories existed for the initial steps.

Solution Applied

  • Conducted a grooming session and created issues for all initial steps.

Changes in next Sprint

Priority Improvement Action Apply
High Sprint Planning Conduct sprint planning session at sprint start ✅ YES
Medium Technical Skills Improve team’s technical level in required technologies ✅ YES
Low Automated Tests Start writing automated tests ❌ No