PIVOT Enablement Leadership

Initiatives

Backstage

Writing for Impact 101

Priority Playground

8/7/2023

Monday - 10:30 CT - 11:30 CT

⁠

Asana⁠

⁠

Meeting Date:
8/7/2023
⁠
⁠

Attendees:

@Christa A. Stephens⁠

@Trevor J. Glisch⁠

@Daniel T. Anderson⁠

@Michelle Helmholz⁠

@Todd R. Chamberlain⁠

⁠

Action Items 18

Action Items 18

Done

Task

Owner

Due date

Created Date

Update TechJays Vendor AGR to reflect changes

Michelle Helmholz

8/9/2023

8/7/2023

Follow-up with Aloa’s issues in Repo access

Trevor J. Glisch

8/10/2023

8/7/2023

No results from filter

⁠

Agenda

Announcements & Reminders

KnowBe4 Training: Due 8/22

TechJays update: Terminating Kowsik at end of August & rolling Suganya into Maintenance Agreement; Dawei sent

updated contract⁠

for review today

Aloa access to Repo for code reviews

⁠

Priority Changes / Escalations

Inventory to Equipment Issues

Discussion topics

Update on FW phase-out

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 (

PIVOT Q2 CSAT Results and Action Items⁠

)

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 (

Vendor Management Example⁠

)

⁠

Backlog → Sprint⁠

flow example

Management Fee Update

Go over what has been communicated to BU Leaders

Impact to the team & discuss options for rollout plan

Figma Dev Mode

Any additional feedback/thoughts after Kaitlyn’s demo on Thursday?

Follow-up from Trevor’s Standards Meeting

1Password Updates

⁠

Project Executing Strategy

Project Owner

Status updates expectations

Dev Lead

Design Lead

Data Lead

Bill Quality User Stories

Bill Quality Views

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

Other Open Action Items List 16

Done

Task

Owner

Due date

ETS Bulk Added > Touchbase with Brandon on expected time frame

Trevor J. Glisch

12/18/2023

Front-end: Temp to perm(?)

Trevor J. Glisch

Service Picks > Attach any Vendor after it has been submitted

Michelle Helmholz

No results from filter

⁠

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.

8/7/2023

Meeting Date: 8/7/2023⁠⁠

Agenda

Meeting Date:
8/7/2023
⁠
⁠