CI Development Routine
Daily Scrum: 9:30AM Daily
Peer Code Review: Every Friday
Sprint Period: 2 weeks
Sprint Planning: Bi-weekly (1st & 3rd Monday)
Sprint Review: Bi-weekly (2nd & 4th Friday)
Knowledge Sharing: Monthly (Every last Friday of the month)
Daily Scrum
DS is to get latest development updates. Each dev will answer:-
1. What did you do on previous working day? Scrum Progress %?
2. What do you plan to do today?
3. Any blockers?
Each dev should spend less than 3 mins to update. Anything longer should be in a separate discussion.
Expected Attendees:-
1. Project Manager (Optional)
2. Tech Manager
3. All dev
4. All support engineer
Sprint Planning
SP is to set a Sprint Backlog (Sprint Goal, Product Backlog, Deliverable Plan). Topics to cover:-
1. Why is this Sprint valuable?
2. What can be Done this Sprint?
3. How will the chosen work get done?
Product Backlogs will be entered into MantisBT.
Max time: 4 hours
Expected Attendees:-
1. Project Manager
2. Tech Manager
3. Product Owner
4. All dev
Sprint Review
SRV is to inspect the outcome of the previous Sprint and to determine future adaptations. Dev will present what was accomplished in that Sprint and its progress towards the Sprint Backlog. Incomplete tasks will be moved back to the Product Backlog. Product Backlog will be adjusted to meet new opportunities.
Max time: 2 hours
Expected Attendees:-
1. Project Manager
2. Tech Manager
3. Product Owner
4. All dev
Sprint Retrospective
SRT is to plan ways to improve quality & effectiveness. Topics:-
1. What went well?
2. What problems were encountered?
3. How were the problems solved?
4. What did you learn from this Sprint?
Max time: 1 hour
Expected Attendees:-
1. Project Manager (Optional)
2. Tech Manager
3. All dev
Peer Code Review
PCR is for dev to reduce code smells and also to improve coding style, convention and code readability. Review should be objective. The purpose is not to review system functionality. Each week, each dev will review code that was committed onto our SVN for the past week. Reviewer and reviewee will rotate every week so that each dev will have a chance to view coding styles of all team members.
Knowledge Sharing Session
KSS is for dev to share new technical skills or information on newly developed tech or modules to peers. Each dev will contribute to KSS every month.
Max time: 3 hours
Expected Attendees:-
1. Tech Manager
2. All dev
