Meeting Date:
Agenda
Announcements & Reminders
KnowBe4 Training: Due 8/22 TechJays update: Terminating Kowsik at end of August & rolling Suganya into Maintenance Agreement; Dawei sent for review today Aloa access to Repo for code reviews Priority Changes / Escalations
Inventory to Equipment Issues Discussion topics
Make a decision at the end of the Sprint — Add to August 21 agenda Team Charters (share progress/discuss communication plan) Experience, Data, and Software Team Charters by November 10th Q2 CSAT Review & updates () Scheduling a follow-up for Thursday Standards Documentation (Do we need any more on how to create/implement standards) Are we building an iterative model in how we work? Design > Dev Handoffs process is critical but concerns are silo-ing ourselves and ultimately creating noise/re-work Our ability to make aligned tweaks while in the development process How do we get far enough to start dev but have practices that allow for design/dev/data to make tweaks to structures, designs, apis ^ but also, how do we prevent the scope from changing/expanding so much that we never “complete” the work? How can we do a better job of clearly defining the scope earlier in the process? Sprint Backlog & Graveyard Boards in Asana There is a LOT of work that has been on our radar & dropped off over the last few months. We need to review and make sure nothing critical is falling through the cracks. Also, determine a path forward for managing backlog. Two kinds of backlog items - what we’ve agreed to do, but don’t have time for right now, and what we haven’t even agreed to do, yet. Should these be managed the same way, or differently? This brings up a good point on “How much is too much” for our workload. Until we scale back on commitments we wont ever get to backlog items. Application-based roadmaps () Go over what has been communicated to BU Leaders Impact to the team & discuss options for rollout plan Any additional feedback/thoughts after Kaitlyn’s demo on Thursday? Follow-up from Trevor’s Standards Meeting Project Executing Strategy Status updates expectations Bill Quality User Stories
Process Changes Action Items
Christa is reformatting BU Coda Docs to be centered around Applications (instead of Project Phases) Trevor is working on BR > Footprint Roadmap Dan is going to outline expectations for a Data Lead Role that is assigned on an Epic Other Open Action Items List 16