1 / 53

EOSP from Bosch Buzzers (Fall 2007)

EOSP from Bosch Buzzers (Fall 2007). Darpan Saini Liang-Yun(Mac) Wang Vytesh Ramesh Yongjoon Choi Yun-Yin(Melody) Huang. Outline. Introduction What happened in this semester Reflection on Risk Team building and operation Planning and execution Requirement elicitation

brit
Télécharger la présentation

EOSP from Bosch Buzzers (Fall 2007)

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. EOSP from Bosch Buzzers(Fall 2007) Darpan Saini Liang-Yun(Mac) Wang Vytesh Ramesh Yongjoon Choi Yun-Yin(Melody) Huang

  2. Outline • Introduction • What happened in this semester • Reflection on • Risk • Team building and operation • Planning and execution • Requirement elicitation • Statement of work • Plan for the Spring Bosch Buzzers - EOSP Fall2007

  3. Mentors and team members • Mentors • Mel Rosso-Llopart • Felix Bachmann • Pedro Bizarro • Technical Advisor • Dr. Herbsleb • Team members Bosch Buzzers - EOSP Fall2007

  4. Introduction to the project • Client • Robert Bosch LLC Research and Technology Center of North America • Representative: Charles Shelton, Chris Martin • Business goal: to help Bosch Body Electronics business unit deliver embedded software • On time • Within budget • At high quality Bosch Buzzers - EOSP Fall2007

  5. Project goal • Short research in global software development • Produce a prototype software to assist communication during the design phase • This prototype could later be extended as a research tool Bosch Buzzers - EOSP Fall2007

  6. The original project Bosch Buzzers - EOSP Fall2007

  7. The new project Bosch Buzzers - EOSP Fall2007

  8. What we have done in this semester Aug Sep Nov Bosch Buzzers - EOSP Fall2007

  9. Reflection on weakness and threats • SWOT analysis and Risk evaluation session • Weakness • Not enough domain knowledge • Invited Dr.Herbsleb to be our Technical Advisor • Communication • Create team activities and increase mutual understanding • Threat • Research scope too large • Set limitation on number of cases we will study for the research • May not be able to find a concrete software to build • Actually happened and our client reduced the scope Bosch Buzzers - EOSP Fall2007

  10. Reflection on roles and team building • Language proficiency • All team members are extremely patient • All three weaker members are planning for external help • Personality and goal difference • Improve understanding through group activities • Respect the difference and try to make the best use of it • Conclusion • All roles perform quite well and everyone seems comfortable with his/her role • We are a solid team! Bosch Buzzers - EOSP Fall2007

  11. Team building activities Bosch Buzzers - EOSP Fall2007

  12. Team operation • With agenda, meeting minutes, and postmortem session • Weekly status meeting and client meeting • Informal meetings • Skype meeting: all discussion history is kept there… • Standup meeting: usually 5 to 10min • Technical Advisor meeting • Detailed timesheet: started at Nov 19 • Files distributed via groove and yahoo group Bosch Buzzers - EOSP Fall2007

  13. Reflection on team operation (1) • Regular status meetings • Becoming shorter in general, since more and more topics have been moved to informal meetings • Informal meetings • Skype meetings • Typing is slow, thus information density is not as high • It is hard to understand who is talking about what topic • Standup meetings • Not everyone joins every meeting • No meeting minutes and cannot be traced back • We may have to document the informal meetings as well • The level of detail for meeting minutes differs greatly Bosch Buzzers - EOSP Fall2007

  14. Reflection on team operation (2) • Client meetings • Client’s time at the end of the meeting • Clients are generally satisfied with our performance in the meetings • Technical advisor meetings • Discussion of related research work • Suggestion on readings • Best practice in distributed development • Very helpful Bosch Buzzers - EOSP Fall2007

  15. Action item and task tracking • Tasks : long term with known due date • Group assignment, P&C sessions, research report,… • Action items : short term and usually assigned in the meetings • Both are tracked or reviewed in the weekly status meeting • Generally speaking, the action item tracking is effective Bosch Buzzers - EOSP Fall2007

  16. Ratatouille Bosch Buzzers - EOSP Fall2007

  17. Reflection on action item tracking About 94% of the action items were finished in 2 weeks Bosch Buzzers - EOSP Fall2007

  18. Original project plan • Oct. 29 – Report draft • Oct. 29 – Nov.23 – Weekly client review • Nov. 19 – SOW draft • Dec. 12 – SRS/SOW final Bosch Buzzers - EOSP Fall2007

  19. Reflection on planning and execution • SRS and SOW are on within deadline • Report draft is delayed for more than 2 weeks • Discuss later with SCRUM • Report final is also delayed although the scope is reduced • Focus changed to the new direction • The actual working hour is still high Bosch Buzzers - EOSP Fall2007

  20. Producing the research report • Plan and process • Use SCRUM to manage the producing of the research report with 2-week sprint • Only Friday, Saturday, and Sunday are counter as workdays • Meet from home using skype • Actual • The estimation for the first sprint is not accurate • After the first sprint was near its end, the project scope changed and the focus of the team also shifted Bosch Buzzers - EOSP Fall2007

  21. Test drive of SCRUM Define prioritized tasks in the product backlog Recursively define subtasks till you reach enough granularity to say if a task is “done” or “not done” Bosch Buzzers - EOSP Fall2007

  22. Reflection on SCRUM • The subtasks were not defined with enough precision • This made task tracking hard and inaccurate • Defining the exit criteria for tasks was not easy since we were writing a report • The earned value was 56% of planned value • If we were to use SCRUM again • Make sure every task and subtask is well defined before entering the sprint • Make sure we are spending majority of our time on the project, e.g. the summer when we have 48 units Bosch Buzzers - EOSP Fall2007

  23. Over against plan Under against plan Reflection on timesheet Interview A+DS Germany Prepared SRS,SOW proposals Start SCRUM Interview Sandip QAW session Direction changed MSD paper Brainstorming Started GSD research Team roles P&C Ops P&C Lifecycle P&C Planning P&C Problem def. P&C SOW P&C Bosch Buzzers - EOSP Fall2007

  24. Requirement elicitation for the collaboration tool Bosch Buzzers - EOSP Fall2007

  25. Result from the requirement elicitation process • Design goal • Comparing distributed with co-located design negotiation • Reduce the difference by 50% • Real-time, synchronous editing of UML diagrams • 2~10 concurrent users • Mix of whiteboard and conventional modeling tool • Every can draw at different part of the diagram • Easy to call for attention • Automatic conformance checking • Design and implementation • Against rules set by the architect • Code name: Camel • A horse designed by a committee Bosch Buzzers - EOSP Fall2007

  26. What Camel looks like Eggs should be okay… Melody: Look at here ! Access violation: vytesh cannot access meat Darpan: Can we bypass this rule? Bosch Buzzers - EOSP Fall2007

  27. Requirement elicitation process Bosch Buzzers - EOSP Fall2007

  28. Requirement elicitation and research (1) Bosch Buzzers - EOSP Fall2007

  29. Requirement elicitation and research (2) Bosch Buzzers - EOSP Fall2007

  30. Outcome of the QAW (1) • Duration: 3 hours • Priority: High(9), Medium(7), Low(1) Bosch Buzzers - EOSP Fall2007

  31. Outcome of the QAW (2) Bosch Intranet Bosch Buzzers - EOSP Fall2007

  32. Reflection on elicitation and research • Contextual diagrams helps to create quick mutual understanding • Prepare question list and make sure everyone, including the interviewee has a copy • A concrete problem to solve would stabilize the project, but it is not always easy to define • The QAW helps to create many use cases which capture important expectation and quality attributes into testable statements Bosch Buzzers - EOSP Fall2007

  33. Reflection on statement of work • The major content is the scope, high level requirement, and milestones • Status: signed • Writing this statement force the team to think of • What is our plan for the next semester? • What would our client want from this project? • What can we promise to our dear client? Bosch Buzzers - EOSP Fall2007

  34. Several highly modular, extensible Camel designs http://www.brickshelf.com/gallery/timgould/Historical/Camel/camel1.jpg http://img329.imageshack.us/img329/5489/untitled0ho.png Bosch Buzzers - EOSP Fall2007

  35. Process - ACDM • We choose ACDM because… • learn and try • collocated architecture experts • clearly defined roles and responsibilities • architecture-centric project • Things to consider • Equal distribution of tasks and responsibilities Bosch Buzzers - EOSP Fall2007

  36. Team Role Bosch Buzzers - EOSP Fall2007

  37. ACDM stages Stage 1: Discover architecture drivers Complete Stage 2: Establish project scope Processing Stage 3: Create notional architecture Incomplete Stage 4: architecture review 5. Production Go? No-Go? Stage 6: Experiment planning Stage 6: Production planning Stage 7: Experiment executing and refine architecture Stage 7: Production Bosch Buzzers - EOSP Fall2007

  38. Semester plan • Spring 2008 • Detailed requirements • Software architecture document (SAD) • Software detailed design draft (SDD) • Software test plan (STP) • Required technology training (e.g. Eclipse plug-in) • Production plan for summer Bosch Buzzers - EOSP Fall2007

  39. Planning considerations • Based on ACDM 7 stages • Considering overhead • 25% on meetings • Status/mentor/client meeting • Working hours for studio project • Each team member spends 12 hours a week • Historical data • Consider the experience from last year Bosch Buzzers - EOSP Fall2007

  40. Initial Plan for next semester SDD SAD, SRS Bosch Buzzers - EOSP Fall2007

  41. Summary • Accomplishment • SOW • Scope clarified • High-level requirement • QAW • Risk evaluation session • certified small-team software risk evaluators • Research report • Team synergy • Preparation • Spring rolls roles defined • Process decided- ACDM Get-set-go for spring!! Bosch Buzzers - EOSP Fall2007

  42. Wish you all a very happy Christmas and a happy new year

  43. Backup Slides

  44. QAW - High Bosch Buzzers - EOSP Fall2007

  45. QAW - High Bosch Buzzers - EOSP Fall2007

  46. QAW - High Bosch Buzzers - EOSP Fall2007

  47. QAW - High Bosch Buzzers - EOSP Fall2007

  48. Plan for next semester • Overhead: • Meeting: 12.5 hours/week Bosch Buzzers - EOSP Fall2007

  49. Plan for next semester • Overhead: • Meeting: 12.5 hours/week Bosch Buzzers - EOSP Fall2007

  50. Initial Plan for next semester • Overhead: • Meeting: 12.5 hours/week Bosch Buzzers - EOSP Fall2007

More Related