...
| Info |
|---|
This time we will focus on how certain events or situations made us feel. We'll use these to talk about how we can improve our process going forward. |
Mad | Sad | Glad |
|---|---|---|
mk - ArcGIS Server complex. Services need to be published in consistent manner | Quarterly planning was good | |
mk - gaps in product scope coming home | ||
[DJ] Security requirements looming large. Scary…. | ||
[AH] So many things need to be rolled over to next sprint | ||
VWM - How long this QA is taking | ||
[AH] It’s not that we can’t start or do SA network migration it’s not a technical challenge, but I’m still explaining why we can’t set a start date due to external factors… what is wrong with the “method” for socializing that? | ||
[DJ] Needing to second-guess stakeholder requirements / expectations - deliver product and hope that it’s close | ||
[DJ] Definition of “Done-Done-Done…-Done”? SA maps - keep putting stuff in there to make our nice new maps look like their old bad maps | ||
[AH] Meeting with VicRoads Zita… then another ~1 week later and the scope was nowhere near what we discussed. MUCH bigger | ||
[AH] PT’s really struggled to get to past UAT, and really struggled to get to prod, Low-Loaders found issues in UAT, Tooley broke really not good. |
✅ Action items
- MXDs to work in multiple environments Mike King :
Jira Legacy server System JIRA serverId 4a110730-6798-3da6-a642-4ff9ad1cd602 key NSSP-5555 - SA - ensure we have clarity of vision / intent / release plan Andrew Hughes
- NHVR contributor page within OSM wiki Jack Boschert :
Jira Legacy server System JIRA serverId 4a110730-6798-3da6-a642-4ff9ad1cd602 key NSSP-5621 - What is our branching strategy & where do we need to be Mike King :
Jira Legacy server System JIRA serverId 4a110730-6798-3da6-a642-4ff9ad1cd602 key NSSP-5623 - David will divide up the work for remainder of VIC
- Comms & Expectation setting with Zita - Andrew Hughes / Johanna Burdett -
- Kill global automation rule that moves stories to done - Jacques.DuToit (Unlicensed)