Proven Process Baselining Phase 2 - Artifacts & Playbook Updates Workstream

Proven Process Baselining Phase 2 - Artifacts & Playbook Updates Workstream

In Phase 2 of our Proven Process Baselining initiative, this group is part of the workstream focused on artifacts and Playbook updates.  See slides 24 – 30 in the Phase 2 Kickoff deck for a reminder of what that means, and specifically slide 30 for what we’re asking of you in this workstream.

What you can expect to be the standard process for this workstream the next few months:

1. At the beginning of each sprint, the CI Team will send an email outlining the artifacts we’ll be working on that sprint. As part of that, we’ll do an initial call for artifacts (i.e. client samples, templates, etc., that might already exist we can use as a baseline for updates to reflect Phase 1 outcomes).

2. If you have something (or know someone who does) we can work from, reply to the email with the example artifact.

3. CI will then work on the artifacts for that sprint, either building on an example that was sourced, creating something new, or updated an existing template – we’ll reach out with questions if needed.

4. On the Friday close of the sprint (every 12 days), we’ll send a follow up email to this group with a master Excel workbook that includes links to the draft artifacts, a section for feedback, and a signoff column. We’ll also send a Teams chat for an additional forum for asynchronous communication.

5. The group will have a one-week feedback window to review, share feedback via the workbook, and sign off. Note: if the artifact isn’t relevant to the team you’re representing, you will not need to review or provide sign-off. We’ll note when that is the case in the workbook.

6. If artifacts are signed off, they’ll go into the Playbook. If there are outstanding questions or feedback we need to go back and iterate on, we’ll move that item forward into the next sprint and refine as needed.

For our first sprint (10/30 – 11/10), the following items are being worked on (we’ll treat this first sprint like a test run and work out any kinks in the process as we go):

• OneClient standard folder structure

• External SharePoint / Teams site standard folder structure

• Project close checklist

• Dashboard or other reporting mechanism to create greater visibility to AAR outcomes and progress on action items

Let Emily or Brooke know if there are questions. We’ll see how this first sprint goes and make any needed adjustments to the process for sprint 2 and beyond. You’ll hear from us again on 11/10 with the workbook to review, provide feedback, and signoff.