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

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

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

6. 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

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

8. Requirements Elicitation ●Initial meetings ●Requirements captured in user stories ●Estimated with planning poker

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

11. Design Tradeoffs TradedReceived Storage AbstractionEase of deployment Organizational user isolationEase of testing & auth Physical decouplingEase of authentication

12. Design Tradeoffs TradedReceived Storage AbstractionEase of deployment Organizational user isolationEase of testing & auth Physical decouplingEase of authentication

13. Design Tradeoffs TradedReceived Storage AbstractionEase of deployment Organizational user isolationEase of testing & auth Physical decouplingEase of authentication

14. Design Tradeoffs TradedReceived Storage AbstractionEase of deployment Organizational user isolationEase of testing & auth Physical decouplingEase of authentication

15. Current Architecture

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

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

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

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

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

21. Technology ●Hand-off is paramount ●Web framework ●Rails ●Spring ●Scala Play ●SQL vs NoSQL ●MongoDB ●Big data ●Performance ●Highcharts for JS data visualizations

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

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

24. 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

25. Metrics - Coverage NameClassesConditionalsFilesLines Controllers17%100%29%8% Models89%100% 42%

26. Metrics - Velocity #1#2#3 101312

27. Metrics – Requirements Volatility 15 Additions

28. Metrics - Bugs 21 Found 12 Fixed 9 Current

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

30. Second Quarter ●Next sprint ●Usability Analysis ●Garlock engineers ●Customer experts ●Hand-off

31. Demo

32. Questions?