scrum practice

1. Scrum Practices Linchuan Wang Scrum Assembling in Chengdu May 23, 2009

2. Scrum Dash Board of Chengdu Team Two

6. Scrum of Scrum with the Integration Team Team One Plenware Team Two Plenware XYZ Team US Team Team ABC HW Team Artist Team Integration Team Customer Release&test report Customer Defects report Release Notes -new features -known bugs&limitations -change logs … Component/Feature Test Case and Report Smoke Test Case Report Bug and defect report Engineering Release Since the main repo is keep up updated (and built) continually , for each check-in there would be one build, so the customer (whoever) could get any check-in build as an “as-is” engineering release. In that sense, every one (team) can release a new feature, patch or whatsoever by pass the integration team for convenience without quality assurance if that’s really somebody wants. !!!NOTE!!! For each single check-in on the main repo the submitter HAS to make sure the smoke test case could be passed. If it’s not sure please execute the smoke test by yourself. Smoke Test Case

8. How to form Common Test Case Suite Team One Plenware Team Two Plenware XYZ Team U.S. Team ABC HW Team Artist Team Integration Team Test Case Test Case Test Case Test Case Test Case Test Case Common Test Case

9. How it works All test case of Set 1 passed Action: request a regression test Red Team Blue Team Integration Team Working Log Test Case Set 1 Test Case Set 1 Test Case Set 2 Test Case Set 3 Test Case Set 2 A Sprint Regression testing trigger Some test case of Set 1 passed Action: Check in regression one Blue team has to pass three sets of test case to meet the Sprint Goals. Red team has two. Integration Team has to pass 5 sets from both Red and Blue Team plus all sets passed previously for new deliverable by the end of Sprint. Main repository Start regression testing Action: test case execution Defects Reporting Check-in Test Case Set 1 Test Case Set 1 Test Case Set 1 Test Case Set 1 Test Case Set 2 regression two … Smoke Test Smoke Test Smoke Test Smoke Test Smoke Test Smoke Test: For each single check-in on the main repo the submitter HAS to make sure the smoke test case could be passed. If it’s not sure please execute the smoke test by yourself. Smoke Test

10. Release Planning

11. Team One

12. Team One Cont’ 195hrs left 42pts planned 29pts_burned.

13. Team Two

14. Team Two Cont’ 23hrs left 28pts planned 27pts_burned

15. Team Three 170hrs left 71pts planned 54pts burned.

16. Enhanced Product Burdown

17. Completion Forecasting

18. Project Management Retrospective