Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

--Please thread your updates to the daily Slackbot standup message in the #fn_pm channel.

...

Thursday, July 16, 2020

no reports

Wednesday, July 15, 2020

Stephen Roger

Y:

  • design/prod collab on UI enhancements and future features

  • backlog and bug grooming/triage

  • future feature/roadmap

T:

  • Start FAQ doc for Outreach/Implementation team

  • Organize & distro notes from Outreach/Implementation & Product team sync meeting please DM me with any requests for content to be included

  • Investigate priority for Localization &  enhanced support for top internet browsers

  • backlog and bug grooming/triage (cont'd)

  • future feature/roadmap (cont'd)

B- None (edited)

Jennifer Schnidman 

🚀

  • Provided QA/Guam a beta build w bug fixes for continued testing

  • Triaged bugs, confirmed Thurs release scope

  • Confirmed Puerto Rico launch timeline

  • Provided guidance on localization and launch planning to Hawaii implementation team

  • Confirm GPS rollout timelines for Guam

  • Finalize Thursday's production release communication plan w @xian

  • Draft implementation tracking spreadsheet

  • Update GPS roadmap in Prodpad to reflect lingering MVP1 discovery needs

  • Discovery/validation for Zendesk integration

  • Record updated e2e GPS/Places product demo, prepare for Friday sprint review

  • 🌵 Not quite blocked by implementation team but still chasing down Guam rollout details (edited)

Tuesday, July 14

Jennifer Schnidman

🌴

  • GPS/Places passing e2e testing!

  • Provided Guam an updated alpha build w bug fixes for their own e2e testing and demo to HA

  • Sprint planning (will share priorities in a separate post)

  • Shared initial draft of Zendesk integration requirements for feedback

  • Record updated e2e GPS/Places product demo

  • Confirm GPS rollout timelines for Guam, Puerto Rico and Hawaii

  • Triage bugs, finalize Thursday's production release plan

🌵

  • Blocked by implementation team - still chasing down rollout dates for 3 customers

Monday, July 13

no report

Friday, July 10, 2020

Jennifer Schnidman

🚀

  • Coordinated new alpha build for Guam testing (see #mobile-gps-releases for more info)

  • Coordinated plan for production release next week (will include location accuracy and exposure notification improvements, Spanish (PR), and publicly add Guam to list of Health Departments)

  • Met with BT team to ensure GPS and BT release plans are coordinated

  • Triaged bugs

  • Lead GPS/Places retro and grooming

  • Sprint review - record updated e2e demo :hand_with_index_and_middle_fingers_crossed::skin-tone-3:

  • Input Haiti and Guam feedback on expected features on Prodpad

  • Share draft requirements for Zendesk integration

🌵 cactus: none 

Stephen Roger

🌴 PTO today ⛱

Thursday, July 9, 2020

Stephen Roger

  • Y:

    • Planning and meeting for HI implementation

    • Working on HA implementation processes & optimization

    • Design updates for Places

  • T:

    • Continuing first two bullets above

    • HA account creation flows/designs/specs

  • B: None

    • NOTE: will be offline for parts of today and some of tomorrow. (edited)

Wednesday, July 8, 2020

Alpita

  • Y:

    • Started working on adding support for missing languages in dayjs needed by Engineering

    • Translators onboarding

  • T:

    • In progress- (This one is more engineering than PM) adding missing language support to dayjs; getting missing translations for ht and getting es_pr translations reviewed. won't add tagalog/fil support as it already exists. Will create a PR on dayjs once I have everything needed.

    • Following up on Micronesia/Guam for more clarity/ visibility on the timeline

  • B:

    • Need more clarity on the Micronesian languages related roll-out. There's several certified translators who have registered and starting to work on it.

 Jennifer Schnidman: @Alpita - I've confirmed that Jeff Kushmerek is the person to connect w regarding the Micronesia implementation

Tuesday, July 7, 2020

Bob Mallon 

  • Y:

    • Sprint Kickoff

    • Accepting Stories from Last Sprint

    • 2 Phone Testing for Exposure Notifications

  • T:

    • Exposure config continued exploration

    • More 2 Phone Testing

    • QA Meeting / Kickoff

  • B:

    • Issues with Server config blocking 2-phone test, blocker on getting Testflight build to HAs

    • Affected User flow bug

Monday, July 6, 2020

Spectra: @channel: As shared in the product weekly update meeting, we now have ProdPad as a way of gathering feedback from across the org:

Visit this link and share away: http://bit.ly/pathcheck-product-feedback

From any channel in which @ProdPad is a member (feel free to invite), you can share feedback by using the command "/ProdPad feedback [Your Feedback Here] to submit"

All feedback that's shared is published in a public channel: #product-prodpad-feedback (where you can emoji, plus one, squeal with delight, and "hell yes" to your heart's content)

Go ahead and give it a try - REAL feedback, please. (Or we'll be inundated with 'test' notifications :sweat_smile:) (edited)

xian: is there a specific hashtag that turns a slack message into Prodpad feedback? or do you cc @ProdPad and add any hashtag? (I'm not sure of the workflow, thanks!

C Todd Lombardo: /Prodpad feedback  then add whatever feedback here

Spectra: Thanks @xian @C Todd Lombardo. I crafted the ProdPad instructions message with aim to fill in details later (to avoid sending my whole message as feedback) then of course got squirrel distracted and forgot. To everyone, instructions for how to share feedback with ProdPad directly from slack, have been updated via the original message.

In essence: "/prodpad feedback [your message here]"

Bob Mallon

  • Y / Thursday:

    • Sprint Review and Retro

    • Test verification server

    • Story acceptance/rejection

    • Planning meetings for next sprint

  • T:

    • Sprint kickoff & other weekly meetings

    • Further work on exposure Config settings

    • Meet with support team

    • Setup 2 phone test for ENs

  • B:

    • Bug on verification code entry

...