Contemi Vietnam Sunday, June 26, 2022 Scrum review (mobile team) Michael Nguyen Senior software engineer
May 10, 2015
Contemi Vietnam
April 11, 2023
Scrum review (mobile team)
Michael Nguyen
Senior software engineer
• Scrum levels• Scrum must have (mobile team)• Scrum issues (mobile team)• References
Agenda
SCRUM LEVELS
Scrum
Scrum level 1
• R&D is busy at the beginning• QA/QC is busy at the end• “Probably Shitable Product” during development• The management forms the teams• Scrum master: 5% capacity
Scrum level 2
• Hyper productive teams• Proactive Scrum master, capacity: 50% • Team formation is usually being done by the teams• Overall release stabilization is being done as part of the
sprint
Scrum level 3
• Test Driven Development• Pair programming (code review, refactor, unit test …)• Continuous Integration (automation test)• Self-organizing team (team creates the team, team
guards itself - no scrum master)• Flow (velocity, no over time)• Risk management
SCRUM MUST HAVE(MOBILE TEAM)
Scrum must have
• Agile methodology• Manifesto http://agilemanifesto.org/ • 12 principles http://agilemanifesto.org/principles.html
Scrum must have
• Scrum concepts• Scrum process (PB -> SB -> sprint -> product …)• Team members and responsibilities
• Scrum master• Product owner• Development team
• Meetings input and output • Planning • Daily• Review• Retrospective
Scrum must have
• Scrum concepts• Artifacts
• Product backlog• Sprint backlog• Potentially Shippable Product (PSP)• Sprint burn down chart• Release backlog
• Others• Definition of “DONE”• Coding standards• Time-box
SCRUM ISSUES (MOBILE TEAM)
Planning meeting issues
• Input: user stories• Output: sprint backlog tasks, sprint goal• Issues
• User stories not clear (As a [user role] I want to [goal] so I can [reason]), acceptance criteria is not defined
• Timebox• Estimation to task not accurate• Solution to task not defined/clear enough• Sprint commitment: what will be done, demo time, retro
time
Development issues
• Input: tasks• Output: code, shippable product• Issues
• Teamwork / Conflict• Testing• Interruptions / New requests from PO
Review meeting
• Input: shippable product• Output: sprint pass/fail• Issues
• Preparation for demo not good enough• Device for demo (need to demo on bigger screen)• Need to note feedback, bugs, improvements/suggestions
Retrospective meeting
• Input: problem lists from team• Output: solution to problems (maybe not all but
important ones first)• Issues
• Not keep track of previous sprint output/solution• No feedback on technical
REFERENCES
References
• http://www.youtube.com/watch?v=D8vT7G0WATM• http://agilemanifesto.org• http://www.agilesparks.com/files/
Scrum_levels_Danko_Danny_Kovatch.ppt• http://www.ijse.org.eg/Content/Vol2/No1/Vol2_No1_1.pdf• http://www.protechtraining.com/pdf/
ScrumCheatSheet.pdf• http://www.n-axis.in/methodologies-agile.php