2014-04-02 Meeting Notes

• MAF is successfully installed on opsimblitz2;
• Cathy to test on osimblitz2 and run from there accessing OpSimDB on both opsimblitz1 and opsimblitz2
• Test simulataneous running of both MAF and OpSim
  • first start simulation, then run MAF - if that does not work
  • second change environment variables to get to work?
• Iain to do second test on the setup of PYTHONPATH

consolidate old machines: new drives on order - Iain will work with cathy to copy all info as in proposal

We talked about development that Francisco could complete by July at a special meeting Apr 1:

1. 3 epoch universal cadence implementation (1week + testing)
2. Rolling Cadence (2 rolling cadence fixes by this week - in sprint)
3. Look ahead for are distribution (including deterministic lookahead debugging)
4. Look ahead for sequences

with Srini taking over the feasibility studies for the speed improvements.

Francisco will send out sub-steps and estimates for time lines so we can assign these tasks to sprints.

 We will spend time in the weekly meeting debriefing after a sprint closes to see what worked and how to do better next sprint. Andy help review our past sprint and made some suggestions

• continue increasing the accuracy of capturing the actual work and tasks we are spending time on.
• break down an activity to smaller pieces that fit within a 2week sprint
• issues should be specific enough that the estimated storypoints should start being more reflective of actual time spent
•  use subtasks to itemize increments within a sprint
• if you get to a blocker - use subtasks to show progress or current status and next steps
• use epics to capture sets of issues that last longer than a sprint (2weeks)
• at meeting we will have agreement among team to what it takes to close and item if it is in question
• add 10% for managing and jira-izing to the estimate for each issue (story)

Kem, Cathy, Srini, Francisco and Steve continued the meeting to structure the next sprint.