A journey about how’s high performance teams forming and develop Mobile application with lightweight dev. process like Scrum.
- 1. 贊 助 單 位：協 辦 單 位： 主 辦 單 位：AgileCommunity.tw “A Journey Of High Performance Teams Forming.” Speaker: JH Tsai/蔡俊宏
- 2. AgileCommunity.tw Agenda • Self-Introduction • The Background • What’s About Agile ? • A “High Performance Team” !!
- 3. AgileCommunity.tw Self-Introduction JH Tsai - Corp. RD, SQA/SEPG (Software Quality Assurance/Software Engineering Process Group) - Joined Trend Micro™ in July, 2013. • CSPO(Certified Scrum Product Owner) June, 2015 – ScrumAlliance Issued • CSM(Certified Scrum Master) April, 2014 – ScrumAlliance Issued • NPDP(New Product Development Profession) June, 2012 – PDMA Issued • PMP(Project Management Professional) February, 2010 PMI Issued
- 4. AgileCommunity.tw Acc. Estimated Defects 2344 Acc. Actual Defects 2007 Defect Variation Rate Estimate Base on Historical ActualAcc. Status Actual Defects 1885 Status Week 1/25 week14 Status Week 2% Current Week 2/8 week16 Current Week 3% Idx Milestone WeekRange Week Estimate Setting Actual Status Actual Estimate Base on Historical Actual 13Internal Beta cut 1/19 ~ 1/25 1/25 1,885 1,840 14 1/26 ~ 2/1 2/1 1,914 # 1,918 15 2/2 ~ 2/8 2/8 2,007 #N/A 1,951 16Internal Beta exit 2/9 ~ 2/15 2/15 #N/A 1,983 17External Beta cut 2/16 ~ 2/22 2/22 #N/A 2,016 5% warning 10% alert 1,951 2,007 0 500 1,000 1,500 2,000 2,500 10/26 11/2 11/9 11/16 11/23 11/30 12/7 12/14 12/21 12/28 1/4 1/11 1/18 1/25 2/1 2/8 2/15 2/22 3/1 3/8 3/15 3/22 3/29 4/5 4/12 Acc.NumberofSubmitDefects Time Estimation Model v2 : based on 9.7 defect density Estimate Actual IB Entry EB Entry
- 5. AgileCommunity.tw The Background • Office is isolated from Trend Micro but co-located with VMFIVE & GMOBILE. • Small teams and sharing resource. • Mobile App. is the target arena.
- 6. AgileCommunity.tw The Background II What SQA was requested to provide profession service ? 1. Apr. ~ Jun. – Deploy A Mobile Dev. Process. 2. Jul. ~ Oct. – As a multiple teams’ Scrum Master(SM).
- 7. AgileCommunity.tw The Background III, Continual What SQA’s solution to fit client’s expectation? 1. External: Bi-Weekly release dev. pace. 2. Internal: Scrum’s dev. methodology.
- 8. AgileCommunity.tw The Background III Fri Mon Tue Wed Thu Scope Definition User Trial (體驗日) Validation (內測日) Release (發布日)
- 9. The Background III, Continual AgileCommunity.tw Features ToDo Doing (RD) Doing (QA) Done Milestone This Week Releas e Next Week Releas e Other s Scope Definition (4/13) User Trial (4/14) Validation (4/22) Release (4/24) Scope Definition (4/20) User Trial (4/21) Validation (4/29) Release (4/30) Story 1 Story 2 Story 3 Story A Story B Analysis & Design Urgent cases Breakdown tasks
- 10. The Background III, Continual AgileCommunity.tw
- 11. The Background III, Continual AgileCommunity.tw 0 1 2 3 4 5 6 7 8 Release Research All Release Day : 5/14/2015 Drop Story Complete Story (Red) Complete Story 0 1 2 3 4 5 6 7 8 Release Research All Release Day : 5/21/2015 Drop Story Complete Story (Red) Complete Story
- 13. AgileCommunity.tw What’s About Agile ? Manifesto for Agile, the number 1 statement is ? Individuals and Interactions Over Processes and Tools
- 14. AgileCommunity.tw What’s About Agile ? Manifesto for Agile, the number 1 statement is ? Individuals and Interactions Over Processes and Tools
- 15. What’s About Agile ? What kind of team/person is the fundamental of Agile/Scrum Dev. ? The manifesto details for core values for enabling High-Performing Teams. By Jeff Sutherland AgileCommunity.tw
- 16. AgileCommunity.tw A “High Performance Team” Executive management need to understand that, being Agile is not a goal unto itself, Agile should be used as an enabler to accomplish business goals. ~By Payton Consulting
- 17. AgileCommunity.tw A “High Performance Team” PO Building the Right Product SM Healthy Project Environment TEAM Reach The Sprint Goal • Own Product • Frontline Shield Protecting - Focus mainly on Clients’ noise • Own Process • Second Shield Protecting - Distractions from inside the org. • Work Under double-layer shield to complete each sprint goal
- 18. A “High Performance Team” So, What a Scrum Master should have ? vSympathy vDiscipline vVision & Engagement AgileCommunity.tw
- 19. A “High Performance Team” AgileCommunity.tw 19 Artifacts Project Vision Statement (PRD) Prioritized Product Backlog Release Planning Schedule Transparency Meeting Information Radiators Sprint Review Meetings Daily Standup Meetings Burndown Chart Scrum board, others
- 20. A “High Performance Team” AgileCommunity.tw Scrumboa rd Inspection Frequent Feedback • Develop Epic(s) • Create Prioritized • Conduct Release Planning Final Inspection • Demonstrate and Validate Sprint.
- 21. A “High Performance Team” AgileCommunity.tw Adaptatio n Daily Standup Meetings Constant Risk Identificati on Scrum Guidance Body(SM) Change Requests Retrospecti ve Project Meetings Retrospecti ve Sprint Meetings
- 22. A “High Performance Team” AgileCommunity.tw Market Cost Structure Cost Structure Revenue Stream Revenue Stream ChannelsChannels Customer Segments Customer Segments Value Proposition Value Proposition ProblemProblem Existing Alternatives Existing Alternatives Early Adopter Early Adopter Key MetricsKey Metrics SolutionSolution Unfair Advantage Unfair Advantage Product
- 23. A “High Performance Team” AgileCommunity.tw
- 24. AgileCommunity.tw A “High Performance Team”