Mach 30 #EngineerSpeak Hangout November 19, 2015
Discussion Topic: Sprint 3 Stand Up 6 and Sprint Review
Attending: J, Jeremy, Aaron, Chris
Start: 2210 Eastern
End: 2330
Summary:
Sprint 3 completed with 3 of 5 PBIs counted as done, those not done still represent major progress, “we have most of the pieces in place and linked, just need to iron out some kinks”
Minutes:
- Did - supported Chris to resolve python library references in MTK documentation/projects; proposed implementing initialization script to add project root to the sys.path var in python when starting IPython which will be picked up by notebooks; need to add PBIs to implement this proposal
- Will do - n/a
- Blocks? - none
- Did - none required
- Will do - n/a
- Blocks? - none
- Did - helped Jeremy with his blocker (working on the singleton for Pint units registry); worked on the data table for YVN-10, but found a bug while getting the results of the test cases, and created an infinite loop (ever increasing data size)
- Jeremy - may have info about that… in working on the unit tests for the geom ran into the iteration looping back to the beginning of the table after finishing the tests so it runs for ever..
- Chris - looked like the table keeps getting added back to itself so it appears to loop again, but it is really just another copy of the data in the test table; not sure why this is happening though
- Will do - n/a
- Blocks? - blocked by whatever this bug with the data set is
- Did - wrote the CAD unit tests, kicked up bugs in implementation (Pint registry) and in the CAD model (would like to add more test cases and more verifications), but need to fix the CAD and verify the fix before the unit tests could be extended more
- J - lean heavily toward calling this tech debt based on the need to update the CAD before we can work on unit tests any more and based on PSAS chamber geom for their cold gas thruster
- Jeremy - the test cases are written to boiler plate level (no verification is in place because the geometry is broken and cannot be verified)
- Chris - ok, so then not done
- CQ-02: There is a bug in the polyline handling in CADQuery that will prevent the modeling of the junction between the chamber and the nozzle in Yavin.
- YVN-20: Update ODE with latest meeting minutes, wiki information, etc.
- J/Aaron - <walk through the project landing page and all wiki pages>, claiming done
- YVN-10: Create unit tests for the PressureVessel class and integrate them into its MTK document as the harness for the reported test results.
- MTK-11: Update ODE with latest meeting minutes, wiki information, etc.
- J/Aaron - <walk through the project landing page and all wiki pages>, claiming done
- YVN-22: Create unit tests to validate the geometry of the hello_world_chamber: number of faces, wall thickness, etc.
- ---
- What to do during the holidays
- J - work adhoc on the incomplete items from Sprint 3
- Chris - thought we would do a sprint, but if things don’t get done, that is ok
- Jeremy - doesn’t expect to be able to commit to a sprint through the holidays, but intends to work on the CAD unit tests as time is available
- Repeat in this sprint and from previous sprints
- More clearly define the PBIs (seemed like we needed more discussion on if some of the PBIs were done or not) and sized
- There was a lot of collaboration and teamwork to work through blockers
- Even though 2 PBIs not done, still felt like the team did a good job selecting the amount of work to take on
- Sizing for a couple of the PBI’s maybe wasn’t quite accurate, especially where Jupyter and IPython are concerned.
- What we can do next time better
- For tools that are new(ish), consider dialing up the risk a little bit to account for the unfamiliarity and potential for discovering new issues
- Better communication severity of issues.
- Better communicate schedules
- Carry-overs from previous sprints:
- Have team members review their calendars in detail to improve capacity estimation
- May also be helpful to publicize this information on an ongoing basis
- Stakeholders should consider being more active to address PBIs that aren’t working (eg, we should probably have removed YVN-15 before the end of the sprint as it could not be completed as specified)
- When no work has been completed on a PBI that is in-progress for more than a week, the team should see if they can help fill the gap
- We need to know that we may need to rely on our own processes and data for confirmation at least, if not for the primary research data.
- Try to eliminate single points of failure - have people that can act as backups for workload.
- Possibly ship replacement or otherwise known working parts to team members having hardware issues.
- Refine the EC review process, both in terms of automation and in terms of sequence. None were major issues.
- Would prefer to not wait until the last minute (even just week to week) to do the committed work
- Weekly posts to P2 or the blog based on the stand ups