2020-04-13 Core Devs



Sprint planning checklist

Preparation

Meeting

Follow up

Preparation

Meeting

Follow up

Compile previous sprint assignments
Gather new tasks
Round table updates
Review progress on previous sprint assignments
Rate difficulty of new tasks
Assign tasks / Decide whether previous tasks should switch owners

Sprint planning meeting items

Use this template to structure your meeting, set expectations and goals, and define the backlog for the upcoming sprint. For detailed instructions and best practices, see our sprint planning guide and review how to estimate story points.

Notes

  1. Roundtable updates

MT – Want to push git branching discussion back a week or two, largely due to difficulty of OE license forking stuff. 0.6.1 question complicates things. Started gathering knowledge about benchmarking, want to prototype a few things. Lots of System object discussions w/ stakeholders.

SB – Minor fixes to evaluator, performance improvements – Mixture setup runtime down from 1 hour. Updated paprika branch. Carrying on with mixture studies.

DD – Finished #379. Finishing up #381 – Needs review. OFFs #5 (ion charges) is coming. OFFTK #572 (WBO torsions). Will be starting on evaluator #226.

JS – Tried DD’s suggestion to run stuff in local storage, didn’t work. Updating for API changes in updated Paprika branch, mostly for running in batch mode.

JW – Mostly small tasks. Also OpenKim work.

 

  1. Roadmap/Issue tracker review

  2. Elect new tasks

    1. Guide/example for making new parameterhandler

    2. Stupid DOI URL DDoS protection

    3. 0.6.1 release? – Will not do this

    4. Travis updates across ecosystem (miniconda URL)

    5. 1.0.1 and 1.1.1 cutting + OFFTK SFI rebuild

    6. CHARMM-GUI integration – Push to next week.

    7. Provide feedback to DD on #381

    8. Blog post about file formats and move to SDF

  3. Review previous tasks

    1. JW – Cerutti support – Ongoing/Completed – Assignment remains / 3 → No work last week, will keep task

    2. JW -- #281 / 13 – Assignment complete

    3. JW – Chargeincrement PR – Incomplete – Assignment remains / 21 – No work last week

    4. DD – #379 – Assignment remains / 3 – Almost complete, already approved for merge

    5. DD – #381 – Assignment remains / 3 – Almost complete, needs feedback

    6. MT (primary) DD (secondary) QCA OpenMM energy evaluation – Ongoing / 8 – Upgraded to 50 / Assignment remains for MT, but others will support as needed

    7. MT – Git branching discussion – Ties in with OE license security, release process, 0.7.0 /0.6.1 scheduling / Assignment removed

    8. DD (primary), MT (secondary). Start on knowledge transfer for OpenFF Evaluator handover → Assignment remains for DD, MT removed. / 21 / 0

    9. DD – Torsion WBOs / 21

  4. Measure capacity

    1. JW – 24

    2. MT – 50

    3. DD – 48

  5. Review open OFFTK PRs

    1. Unblock 560 by resolving 568 / 3

    2. Review 543 / 2 – JW

    3. Review 569 / 2 – JW

  6. Assign new tasks

    1. Stupid DOI URL DDoS protection / 2 – JW

    2. Travis updates across ecosystem (miniconda URL) / 8 – MT – JW will provide list

    3. 1.0.1 and 1.1.1 cutting + OFFTK SFI rebuild / 3 – JW + DD

    4. Provide feedback to DD on #381 / 2 – JW

    5. Issue triage – 5 – JW

  7. Measure capacity

    1. JW – 40

    2. MT – 58

    3. DD – 51

Details

Start date

April 13

Start date

April 13

End date

April 20

Sprint theme

Big-picture prioritization and developer onboarding

Adjusted velocity tracking

Capacity planning

You can customize this template to change or add capacity measurements. You can also review older sprints by adding columns.

 

Current sprint

Previous sprint

 

Current sprint

Previous sprint

Total days

 

Team capacity

 

Projected capacity

 

Individual capacity

 

Potential risks

Risk

Mitigation

Risk

Mitigation

 

 

 

 

Sprint planning resources

Sprint boards and retrospectives

  •  

Team resources and definitions

  •