PI Planning 26.4 Tasks

[abarciauskas-bgse]

• Solicit information from VEDA instances on their dataset needs using https://github.com/NASA-IMPACT/titiler-multidim-user-survey/blob/main/.github/ISSUE_TEMPLATE/dataset-needs.md or something comparable
• Complete a brainstorming exercise, such as dumping all ideas and known needs into a document. Include DS VEDA lead. This can start at any time.
• Organize those into various categories of work, such as "Dataset generation", "Community, or "titiler-xarray". This will help identify associated or dependent tasks as well as help team members identify which categories of work they are most interested in.
• Priotize ideas based on need for VEDA or technical context.
• Pruned based on capacity and interest.
• Refine the pruned list of ideas. Make sure all pruned ideas are described as objective statements, with subtasks as appropriate. Any number of objectives is fine as long as it matches capacity.
• Each objective should have an objective statement, motivation, tasks, risk, LOE, owner (see Example 25.2 objectives).
• Create a sprint by sprint gantt chart (see last slide of 25.2 objectives).
• Meet about proposed plan with the project lead at IMPACT (i.e. Brian). This meeting is usually coordinated by the NASA project coordinator for all VEDA sub teams.
• Increment the PI number in the objective template
• Create objective tickets (delegate to owners of each objective).