Windows Sprint 2 post mortem - ansible/community GitHub Wiki
I had some thoughts following Windows Sprint 2 which I have recorded here @jhawkesworth
Please add any further oboservations or suggestions so future sprints can be improved.
Sprint 2 post mortem
- Perhaps pick less issues so that overall we spend less time doing triage.
- The timeboxing idea wasn't bad but need a way to enforce it (a shell script to echo ^G every few mins perhaps). But needs to be flexible enough to switch order of tickets, as interested parties/OPs can appear at any time.
- Triaged approx 12 issues in 60 mins. Hard to say how long it to triage last 2 issues as WWG meeting conincided.
- Should state that your ticket gets priority consideration if you show up on #ansible-windows when publicizing tickets.
- Make notes on tickets as we go, it was time-consuming to have to go back to each issue and add notes later.
Other ideas
-
Maybe have a follow up session in say 2 weeks to clear up the wiki, see what still needs attention.
-
Figure out how we can get more community involvement in selecting sprint content.
-
a features only sprint might be a nice idea (win_xml alone might eat a whole session)
-
documentation was something that came up as part of a lot of the issues, so encourage community members who can write and test to attend
-
document how to use packer, vagrant etc to create test windows inventory.