11/1/21
What went well:
What could go better: Less firefighting. More of a controlled roadmap with actual requirements and designs and planning.
There is difficulty in having sidebar conversations for dev purposes across different teams
Action:
Communication Planning and documentation:
For requirements: We should add the ability to document who required the item and why.
Is this in the project plan
Breakdown what is in the grant prior to and during submission to evaluate feasibility
And after grant is approved, we should breakdown the actual stories with high level features
Need to have a grant breakdown planning process with roadmap and resource allocation
Need to have open conversations with researchers for the requirements:
Access to Larrson and his time.
Utilize mPower requriements for adding to MTB assessments. to leverage options for study bursts.
10/18/21
Study Bursts are not as defined as should be. Feels okay about design and server frameworks, but open questions are expected.
Dual Account signup and Enrollment work to be completed. Additionally working on documentation
Android - Investigate Mpower assessment integration, Data Tracking documentation and feasibility relating to things like medications etc.
iOS- Investigate data tracking feasibility for MTB
Investigate
Exporter - continuation.
10/4/21
QA feedback:
Worried that so few QA bugs were logged. It seems like most of the bugs were filed by internal (Design) and not with the QA team.
...