Get consensus on the purpose and definition of the Thursday COINSTAC full team meeting

[praeducer]

Sub-tasks

• [x] Create a standard agenda. see below
• [ ] Confirm this plan with other key stakeholders and meeting attendees
• [ ] Create a standard meeting note template
• [ ] Publish final version to the wiki
• [ ] (optional)Visualize the flow of the conversation
• [x] Do the students and computation authors need individual updates? Maybe they have their own meeting like the devs have their standup? Getting Vince, Sergey, Jess, and Anand together at any single time is really hard... we'll have to fit it in.

[praeducer]

@rssk and Dev Team's perspective and needs:

1. Discovery of the organization's needs; business/research/user requirements gathering (technical requirements can be discussed on Friday).
2. Negotiation (optional) between what to commit to now versus later; pushing back to make sure technical debt is addressed and the there is still time to address important future state technical changes that benefit the project long term.
3. Confirmation of existing understanding and that work done has met requirements.
4. Balancing (optional) the reality of what is possible, what is not getting done, and what can't be done

Discovery of Vince's, PI's (e.g. Jess, Sergey and Jeremy) and the organization's needs such as:

• their businesses vision, goals, and deadlines.
• their grant and research requirements and how the dev work relates to them.
• the core features and their updates.

Discovery of @spanta28's and Computation Author's needs such as:

• features to support their research and computations.
• ideas to improve the UX.
• bugs they've ran across.

Meeting framework:

• Send summary email after meeting. Include new work discovered, action plan (what was committed to), upcoming key events and deadlines.

Principles:

• Not individual dev updates unless they ask Sandeep ahead of time to present something specific.
• It's great if we actually stay focused on past priorities and work we agreed upon. Sticking to core features is a good thing. We actually we to avoid discovering and negotiating new work. We'll accomplish more long term if we focus on less now.

[praeducer]

@spanta28 to confirm with PI's before we publish to documentation.