1 / 32

Team Miles of Style

Team Miles of Style. Chris Bentivenga, Dan Cunningham, Sean Congden , Mike Drogalis Sponsors: Wayne Evans, Jim Drago Coach: John Loser. About Garlock. Create sealing technologies Used in wide variety of applications Pharmaceutical plants Nuclear power plants Oil refineries & pipelines.

gaille
Download Presentation

Team Miles of Style

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. Team Miles of Style Chris Bentivenga, Dan Cunningham, Sean Congden, Mike Drogalis Sponsors: Wayne Evans, Jim Drago Coach: John Loser

  2. About Garlock • Create sealing technologies • Used in wide variety of applications • Pharmaceutical plants • Nuclear power plants • Oil refineries & pipelines

  3. Problem • Garlock wants to provide a system to check product status and hopefully predict failures • Mission critical

  4. Scope • Receive sensor readings • Thresholds and alerts • Sensor history and details • Security in isolated data stores • User hierarchies

  5. Why Scrum? • Requirements and scope volatility • We aren’t Mechanical Engineers • Demo each sprint • Will allow for some end-user testing early • Sponsor is very hands on

  6. Scrum Details • Roles • Two-week sprints • Meetings • Tri-weekly standups • End of sprint meetings • Artifacts • Sprint backlog • Velocity chart • Tools • Pivotal Tracker • Trello

  7. Requirements Elicitation • Initial meetings • Requirements captured in user stories • Estimated with planning poker

  8. Design • Web App • Easy Deployment • Forces • Arbitrary Locations • API • Strong data isolation • Dynamic visibility • 3 Designs • API ⬄ storage ⬄ dashboard • Explicit trade-offs

  9. Managed deployment Managed deployment Datastore isolation API isolation, hides datastore location

  10. Design Tradeoffs

  11. Design Tradeoffs

  12. Design Tradeoffs

  13. Design Tradeoffs

  14. Current Architecture Retained for long term storage Send a sensor reading Authenticates (256 bit API key) and dispatches Local, Rackspace, AWS, anywhere

  15. Technology • Hand-off is paramount • Web framework • Rails • Spring • Scala Play • SQL vsNoSQL • MongoDB • Big data • Performance • Highcharts for JS data visualizations

  16. Technology • Hand-off is paramount • Web framework • Rails • Spring • Scala Play • SQL vsNoSQL • MongoDB • Big data • Performance • Highcharts for JS data visualizations

  17. Technology • Hand-off is paramount • Web framework • Rails • Spring • Scala Play • SQL vsNoSQL • MongoDB • Big data • Performance • Highcharts for JS data visualizations

  18. Technology • Hand-off is paramount • Web framework • Rails • Spring • Scala Play • SQL vsNoSQL • MongoDB • Big data • Performance • Highcharts for JS data visualizations

  19. Technology • Hand-off is paramount • Web framework • Rails • Spring • Scala Play • SQL vsNoSQL • MongoDB • Big data • Performance • Highcharts for JS data visualizations

  20. Technology • Hand-off is paramount • Web framework • Rails • Spring • Scala Play • SQL vsNoSQL • MongoDB • Big data • Performance • Highcharts for JS data visualizations

  21. Testing • Unit testing • Scala Spec • Play Framework • Integration testing • Continuous integration & deployment • UI and navigation testing • Acceptance testing • Sprint reviews • Sponsor feedback

  22. Testing • Load testing • Big data problem • Garlock sample data • Usability testing • User interface focal point • Garlock employee feedback

  23. Risk Mitigation • Unexpected major features • User interface not useful to Garlock engineers • Design unable to handle large sensor load • New technology gold plating • Developer strain weeks 9 and 10

  24. Metrics - Coverage

  25. Metrics - Velocity Metrics - Velocity

  26. Metrics – Requirements Volatility 15 Additions

  27. Metrics - Bugs 21 Found 12 Fixed 9 Current

  28. Reflection • Good • Scrum • Team gels • Bad • Winter Break Planning • Code reviews • Testing discipline • Other • Play

  29. Second Quarter • Next sprint • Usability Analysis • Garlock engineers • Customer experts • Hand-off

  30. Demo

  31. Questions?

More Related