...

...

https://drive.google.com/open?id=18sQvR7QVWH766XUOesQ0jrXWODdC4CmZ

Potential Challenges

m200127 - demo MVP v1 

Great job on the demo
Excellent job on the demo and delivery on ux and back-end services that matched the design specs from Sahoja so far.

Sahoja still in design mode
Clearly they had not gone through a deep analysis of their own design docs as a team before they submitted the design docs to Paramount. That certainly impacts rework on our end they could have avoided. The "committee" approach at Sahoja makes it difficult to finalize design requirements. Sanjeev is really the UX designer here. All others should cycle their input back to him first for review before submission to Paramount.

Project communications
Kevin is correct that we need to limit the official commnication channels for effective communications. Comments in a messaging app are not design documents to work from. Who owns the approval of design documents at Sahoja? They need to manage the inputs to Paramount and the approvals for those docs. Nice job on the Paramount end documenting our requests for input.

Engagement notifications
Sanjeev now looking to add more engagement options ( notifications to donate etc.). He should understand the need for user policies to drive that and NOT a system-wide policy on notifications. Notification options can include email or text messages.

Performance
What's the login performance trace show?

Front-end page updates on back-end transactions
2 basic options are: 1> use simple call back for page refresh or 2> web sockets updates allowing the server to push to the front-end data changes directly. Both can work well in React / Redux.

m191230 - Sahoja meetings

...