Embed Size (px)
DESCRIPTION
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. - PowerPoint PPT Presentation
Citation preview
Team Miles of StyleChris Bentivenga, Dan Cunningham,
Sean Congden, Mike DrogalisSponsors: 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
Problem
● Garlock wants to provide a system to check product status and hopefully predict failures
● Mission critical
Scope
● Receive sensor readings
● Thresholds and alerts
● Sensor history and details
● Security in isolated data stores
● User hierarchies
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
Scrum Details
● Roles
● Two-week sprints
● Meetings● Tri-weekly standups● End of sprint meetings
● Artifacts● Sprint backlog● Velocity chart
● Tools● Pivotal Tracker● Trello
Requirements Elicitation
● Initial meetings
● Requirements captured in user stories
● Estimated with planning poker
Design
● Web App● Easy Deployment
● Forces● Arbitrary Locations
● API● Strong data isolation● Dynamic visibility
● 3 Designs● API storage dashboard⬄ ⬄
● Explicit trade-offs
Datastore isolation
API isolation, hides datastore location
Managed deployment
Managed deployment
Design Tradeoffs
Traded Received
Storage Abstraction Ease of deployment
Organizational user isolation Ease of testing & auth
Physical decoupling Ease of authentication
Design Tradeoffs
Traded Received
Storage Abstraction Ease of deployment
Organizational user isolation Ease of testing & auth
Physical decoupling Ease of authentication
Design Tradeoffs
Traded Received
Storage Abstraction Ease of deployment
Organizational user isolation Ease of testing & auth
Physical decoupling Ease of authentication
Design Tradeoffs
Traded Received
Storage Abstraction Ease of deployment
Organizational user isolation Ease of testing & auth
Physical decoupling Ease of authentication
Current Architecture
Send a sensor reading
Authenticates (256 bit API key) and dispatches
Retained for long term storage
Local, Rackspace, AWS, anywhere
Technology
● Hand-off is paramount
● Web framework● Rails● Spring● Scala Play
● SQL vs NoSQL● MongoDB
● Big data● Performance
● Highcharts for JS data visualizations
Technology
● Hand-off is paramount
● Web framework● Rails● Spring● Scala Play
● SQL vs NoSQL● MongoDB
● Big data● Performance
● Highcharts for JS data visualizations
Technology
● Hand-off is paramount
● Web framework● Rails● Spring● Scala Play
● SQL vs NoSQL● MongoDB
● Big data● Performance
● Highcharts for JS data visualizations
Technology
● Hand-off is paramount
● Web framework● Rails● Spring● Scala Play
● SQL vs NoSQL● MongoDB
● Big data● Performance
● Highcharts for JS data visualizations
Technology
● Hand-off is paramount
● Web framework● Rails● Spring● Scala Play
● SQL vs NoSQL● MongoDB
● Big data● Performance
● Highcharts for JS data visualizations
Technology
● Hand-off is paramount
● Web framework● Rails● Spring● Scala Play
● SQL vs NoSQL● MongoDB
● Big data● Performance
● Highcharts for JS data visualizations
Testing
● Unit testing● Scala Spec● Play Framework
● Integration testing● Continuous integration & deployment● UI and navigation testing
● Acceptance testing● Sprint reviews● Sponsor feedback
Testing
● Load testing● Big data problem● Garlock sample data
● Usability testing● User interface focal point● Garlock employee feedback
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
Metrics - Coverage
Name Classes Conditionals Files Lines
Controllers 17% 100% 29% 8%
Models 89% 100% 100% 42%
Metrics - VelocityMetrics - Velocity
#1 #2 #3
10 13 12
Metrics – Requirements Volatility
15 Additions
Metrics - Bugs
21 Found12 Fixed 9 Current
Reflection
● Good● Scrum● Team gels
● Bad● Winter Break Planning● Code reviews● Testing discipline
● Other● Play
Second Quarter
● Next sprint
● Usability Analysis● Garlock engineers● Customer experts
● Hand-off
Demo
Questions?
