HISU SCRUM & Project Review
Agenda
-
Introduction
-
Retrospective
-
Team Velocity and Performance
-
Improvements and Suggestions
-
Feedback
HISU
so far
Total
Modules
16
Modules
Completed
14
Modules
IN TEST
2
Total Team: 13
- QA - 3
- Frontend - 4
- Backend - 5
- Manager - 1
Team Velocity
Average
38.5
HISU Sprint 8
Total
Modules
2
Modules
IN TEST
2
- UI/UX Design Updates
- Bug Fixes for 14 modules
- Backend Refactoring Changes
Stories Completed
HISU Retrospective
Key Highlights
- Lack of Communication between the Frontend and Backend teams
- Wireframe or Ideation for UI/UX Design
- Both FE and BE in one sprint are hard
- Code Guidelines
- QA was involved after the sprint
Action Items
- Teams seated together
- Communication platform for both frontend and backend via JIRA, Whatsapp
- BE starts a sprint early
- UI/UX discussion in Sprint Planning
TEAm Velocity and Performance
Team Velocity
Average
38.5
Team Commitment
Average
87.75
TEAm Velocity and Performance
Cont,,,
- In progress and Testing is all off limits
- All should be on same line
Cumulative flow of Issues
TEAm individual Performance
Cont,,,
- Still requires more metrics and data for drill down data points
Improvements & Suggestions
- Moving from Sprint to Kanban
- Why? Continous flow of Work
- Taking up responsibility
- Why? Ownership makes product better
- Leads should lead the team with confidence
- Why? Absence of Leadership
- Saturday mornings for some learning (Alternative)