1 / 19

StarCite Engineering Weekly Meeting

StarCite Engineering Weekly Meeting. StarCite Engineering Feb 9, 2009. Agenda. Quarterly Engineering top priorities Shanghai Engineering team weekly update – 5 minutes Releases schedule overview Unit Test weekly progress chart Rally Iteration Weekly status Engineering Operation Metrics

mauli
Download Presentation

StarCite Engineering Weekly Meeting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. StarCite Engineering Weekly Meeting StarCite Engineering Feb 9, 2009

  2. Agenda • Quarterly Engineering top priorities • Shanghai Engineering team weekly update – 5 minutes • Releases schedule overview • Unit Test weekly progress chart • Rally Iteration Weekly status • Engineering Operation Metrics • QA metrics • Special Topics – 10 minutes • Complete Agile progress in SM – Leslie • Code review process - Justin • Q&A

  3. Engineering Q1/09 Top 3 Priorities (aligned) Absolutely has to happen – put best effort and team to meet the metrics and dates

  4. Performance, Stability and Quality – Why, What and How • Why? • To improve internal quality to enhance both the functional and non-functional quality of our products to satisfy customers • To gain business benefits • What to do? • Effective code review including design review • Unit test coverage and effectiveness • SQL profiling • Code re-factoring • How? • To re-enforce code review, unit test and SQL profiling; to make them as part of the development work • To provideguideline and good examples, to build good practice, • To be measurable; to know where we are today; to set near- and long-term target; to track progress;

  5. Release Schedule in Q1/2009 Congratulations on the release of Search service

  6. Unit Test Objectives

  7. Current Unit Test Coverage Numbers – by last Friday * Newly started project, has no unit test coverage yet

  8. QA Automation – Accomplished in 2008

  9. QA Automation – Q1 2009 Target 100% Smoke test script get updated

  10. Engineering Operation metrics Total Open/Closed Level1 (Last 7 days) *3 customer discovered S0 – due to server out of memory.

  11. Engineering Operation metrics (cont.) Level1 Status and Assignment (Last 7 days)

  12. QA metrics – Q4 2008 release review

  13. QA metrics – Q4 2008 release review

  14. QA metrics – Q4 2008 release review

  15. QA metrics – Q4 2008 release review

  16. Special Topics – Complete Agile • Big improvement is evident by comparing the iteration burn down charts • -- SM12.15.2 – sprint 2 shows healthier burn down chart than the SM12.15.2 – sprint 1 • - SM12.15.2 – sprint 2 accomplished much more story points by last day of the iteration SM.12.15.2 – sprint 1 SM.12.15.2 – sprint 2

  17. Special Topics – Code Review process • Cross Code Review • Purpose: promote a culture “team excellent” of 2009 goals from Yang, and an attitude “I DO welcome anyone reviewing my codes and it can help me grow faster“. • Focus: most important technique hotspots: • Out-of-memory issue identified by operation team • Unexpected server restart identified by operation team • Very long DB operations identified by SQL profiling log and app Log • Legacy codes need re-factor and the new codes • Other important issues identified by Team • Peer Code Review • Purpose: improve code quality by regular code review activities   • Focus: • All new codes have to be reviewed and the activities must be tracked on Rally. • Legacy codes are encouraged to have more code reviews and related action plans

  18. Special Topics – Code Review process • Encourage Plan • Performance bonus: code review efficiency (including frequency and quality) will be treated as one very important performance metric of team member. • Recognition: we will recognize the best engineers for the contribution on code review activities and the detailed plan will be decided later. • Leaning Credits: the engineers with good contribution on code review activities will get extra leaning credits to get encouraged.   • Introduce a web based tool for code review: • Review Board which developed by Vmvare(http://www.review-board.org/) • Evaluation is underway. If anyone is interested, please come forward and talk to Justin

  19. Mr. Q&A

More Related