Closed ghost closed 6 years ago
➤ Brandon Arbiter commented:
Building out individual cards for parsing of Medtronic 6 history message. Ping @darinkrauss @lennartgoedhart2 for review and time estimate.
Ping @ericluhrs to review/update Test Strategy.
➤ Darin Krauss commented:
@brandonarbiter Looks good. Per the "Remaining Work" card, I would prefer we handle mg/dL and mmol/L units for this subset of events all at once rather than handling mmol/L at a later point.
@lennartgoedhart2 I don't have any good sense for time estimates on this. Do you have any idea on scope (S/M/L) and story points (1,2,3,5,8)? Let me know if you want to discuss.
➤ Lennart Goedhart commented:
@brandonarbiter added points.
➤ Brandon Arbiter commented:
Updated Test points.
Cc: @ericluhrs
Problem
Success
Scope
Leader
Cost (breakdown of ux/dev/tst resource points)
User Stories
Done Criteria
KissMetrics Events
Related Cards
Test Strategies
Verification Test
Approved for production by
Demo Strategies
Pull Requests
Tags & Release Notes
┆Attachments: #368 Add history message parsing for 600-series