Sprint 3 Retrospective
Sprint 3 Retrospective
What Went Well
- A code has been written that will allow you to write features in the future
- The practice of testing and CI/CD has been implemented
- Linters, formatters, and link checker have been added
Problems Encountered & Solutions
Problem 1
Not enough workers to write the code
Description
- We have only one developer in the project who can write in python.
Root Cause
- Lack of competence in the team
Solution Applied
- Improve knowledge and skills in the team
Problem 2
The difficulty of testing the bot
Description
- It’s hard to write tests for the part of the system that runs on the telegram side
Root Cause
- Telegram does not provide an opportunity to conduct testing on its side
Solution Applied
- Using the telethon library
Changes in next Sprint
| Priority | Improvement | Action | Apply |
|---|---|---|---|
| High | Improve bot testing | Use the telethon library | ✅ YES |
| Medium | Technical Skills | Improve team’s technical level in python | ✅ YES |
| Low | Reduce project time | Add more developers to the project | ❌ No |