Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

A manually updated dashboard showing overall “Ready for Testing” status for MVP1. This is intentionally high-level. For details see Jira, Practitest, Detailes Test Reports, or ask on Slack (#testing, or one of the Scrumt Team channels)

If info here does not match what you believe is the case, what you see in Jira etc. (and the difference can’t be accounted for by the “last updated” timestamp, please have a conversaton with Diarmid Mackenzie or Adam Leon Smith as this suggests a comms gap.

Colour coding is highly subjective, but roughly: green = on track, amber = off track, but with a correction plan in place, red = off track & no clear plan, grey = descoped

Link to MVP1 spreadsheet
Link to JIRA

Last updated: 11 June, 10am Eastern

MVP Story

Overall Status

Action needed

MVP1: GPS logging gaps

More-or-less done on Android. iOS with Guam Dev. No clear date/plan for iOS yet.

Clear iOS plan from Guam. Now capturing locations, but data not going into Realm yet. Further update promised 6/12 - now overdue

MVP2: GPS accuracy

Deferred to Mercury - though there has been Android progress under MVP1.

MVP3: Encryption on device

Implemented and mostly tested

MVP4: Clarify limitations via copy

Ready for Test as of 6/14

MVP5: Feature Flags

Implemented, tested, all good.

MVP6: Clarify Exposure Notification

With Rocket. SAF-283/SAF-284. Was due to be R4T by 6/11.

Still not R4T as of 6/15

MVP7: Auto-subscription

In develop as of 6/14, but I’ve been told by Jacob Jaffe (Deactivated) that it is not working.
We also need to be able to update the HD YAML file to test it

Being proposed that we de-scope this.

MVP8: Improved user consents

Ready for Test. No blockers.

MVP9: Internationalization

Lots of work still in Progress - no clear date for delivery into test.

Get clear plan from Alpita. Waiting for stable English app copy.

MVP10: Designate Privacy Policy in Settings

Ready for Test.

https://pathcheck.atlassian.net/browse/PLACES-350

MVP11: Safe Places UX

About 80% Ready for Test. I’m assuming there is a plan for the remaining 20%? (214, 327, 331, 332)

Get clear plan for 4 remaining TO DOs (all with David - awaiting firm completion plan) Still waiting for final fixes(filters) as of 6/15

MVP12: Manually enter points as CT

SAF-496 “duration” still outstanding
(SAF-496 and SAF-541 both still not R4T).

Get plan on SAF-496 Expect to deliver 6/11., but still not available as of 6/15. Back-end refactor will follow after MVP1.

MVP13: Load, edit, save aggregated data

Ready for Test.

MVP14: Configure Retention Policy

Ready for Test.

MVP15: Publisher Tool

Ready for Test

MVP16: Secure transmission of location data

Ready for Test

https://pathcheck.atlassian.net/browse/PLACES-348?atlOrigin=eyJpIjoiZGYwMTA4YTVmODNkNDA0Mjk4ZGE0MWNlY2M1MDNlZmMiLCJwIjoiaiJ9

MVP17: Scalability

Pagination & Hashing App code now merged, but JJ says still some connecting code missing. Also still missing “HA by URL” function

JJ actively working on this.

MVP18: Encryption of Points of Concern

This function is ready, but can only be tested with MVP17

As per MVP17

MVP19: Efficacy measurement

Descoped

MVP20: Tunable GPS intersection logic

This function is ready, but can only be tested with MVP17. Agreed PLACES-80 is out of scope.

As per MVP17.

MVP21: Onboarding flows for HAs

Descoped.

MVP22: Safe Paths → PathCheck

Under implementation with Yonatan.

Still marked as “Blocked” - status not clear.

Jen had suggested 6/15 or 6/16.

MVP23: Rework HA YAML file

SAF-400. Will deliver alongside MVP7.
Status unclear as MVP7 status unclear.
Also SAF-400 includes SAF-243 Self-Assessment which seems wrong.

Status unclear

MVP24: Tab redesign

SAF-479. Ready for Test

  • No labels