sprint-retrospectivelisted

# Sprint Retrospective ## When to use this skill - **End of sprint**: at the end of each sprint - **Project milestone**: after major releases - **Team issues**: when an immediate retrospective is needed ## Instructions ### Step 1: Start-Stop-Continue ```markdown ## Retrospective Template: Start-Stop-Continue ### START (Start doing) - Make daily standups shorter (within 5 minutes) - Use a code review checklist - Introduce pair programming ### STOP (Stop doing) - Deploying on Friday afternoons (rollback risk) - Overusing emergency meetings - Adding features without documentation ### CONTINUE (Keep doing) - Weekly tech sharing session - Automated tests - Transparent communication ### Action Items 1. [ ] Change standup time from 9:00 → 9:30 (Team Lead) 2. [ ] Write a code review checklist document (Developer A) 3. [ ] Announce the "no Friday deployments" rule (Team Lead) ``` ### Step 2: Mad-Sad-Glad ```markdown ## Retrospective: Mad-Sad-Glad ### MAD (What made us mad) - Urgent bugs after deployment (twice) - Requirements changed frequently - Unstable test environment ### SAD (What we wished went better) - Not enough time for code reviews - Documentation lagged behind - Accumulating tech debt ### GLAD (What made us glad) - New team members onboarded quickly - CI/CD pipeline stabilized - Positive customer feedback ### Action Items - Strengthen the deployment checklist - Improve the requirements change process - Reserve documentation time every Friday ``` ### Step 3