Versions Compared

Old Version 9

changes.mady.by.user Justine Houchin

Saved on

compared with

New Version 10

changes.mady.by.user Justine Houchin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Panel
bgColor#F4F5F7

Divison & Branch Alignment

Panel
bgColor#F4F5F7

Digital Talent & Capacity Branch Goal:

Digital Talent and Capacity helps the BCPS build and grow teams
with the skill and ability to deliver digital, human-centered
products and services for the peoples of BC.

Panel
panelIconId1f920
panelIcon:cowboy:
panelIconText🤠
bgColor#79E2F2

Digital Talent Development 24/25 Quarterly OKRs

Child pages (Children Display)
allChildrentrue
Panel
panelIconId1f635-200d-1f4ab
panelIcon:face_with_spiral_eyes:
panelIconText😵‍💫
bgColor#79E2F2

Frequently Asked Questions

Live SearchspaceKeyDT

Table of Contents
minLevel3
maxLevel3
outlinefalse
stylenone
typelist
printabletrue
Panel
panelIconIdatlassian-question_mark
panelIcon:question_mark:
panelIconText:question_mark:
bgColor#F4F5F7

So what’s the difference between an outcome, an objective, a key result, an epic, etc, etc, etc?

That’s hard to say! Many people in our ecosystem are using these words in different ways, and the overlap is confusing. For our purposes:

Status
colourBlue
titleoutcome/objective:
Our team is using these interchangeably. Yes, they’re different things. Yes, we want to be outcome-focused. But with so many people across the Digital Office using “objective,” we want to be sure we can be understood. For us, this means the change we’re trying to effect, the impact we’re trying to have, etc. These are usually 1-2 year long goals. You can find the Chief Digital Officer’s objectives for 24/25 here and the Talent & Capacity branch objectives for 24/25 here.

Status
colourBlue
titlekey results/initatives:
The measurable pieces of work that lets us know whether we’re making progress toward our objective(s) or not. You’ll sometimes hear others across the Digital Office refer to these as quarterly goals or quarterly OKRs (it’s confusing!). These are the scoped down increments of work that team’s bring across the line in 1-2 quarters, and they’re tracked by the Senior Management Team on https://bcdevex.atlassian.net/jira/software/c/projects/DO/boards/61?assignee=5e8245da68b30b0c1ac676f0&assignee=70121%3A78ae9e67-24cf-4c4b-9691-63ecacca8c7d&assignee=70121%3A9879a257-1059-4575-bb26-a31e32c3e325&assignee=557058%3Af81026df-3e09-40a5-b450-705bdbe44937&assignee=5a9ef0cddafd4b2a7d6eaeb1&assignee=6245caa52e101c006a8e820c&assignee=712020%3Aea7bc5b0-7d9e-4ced-a474-6257111ea441 (Permissions on this are wacky right now - if you can’t see the board, rest assured that we’re working on it). The PO will work with the team and the leadership teams to draft these each quarter and update progress within these pages. For the sake of sustainable pace, we try not to have

Status
colourBlue
titleepic:
Different teams mean entirely different things when using this word, but for us it’s a JIRA-only term and a way to organize our buckets of work. Often, we’ll make an epic in JIRA for all the backlog items we need to complete to accomplish our key result.

Panel
panelIconIdatlassian-question_mark
panelIcon:question_mark:
panelIconText:question_mark:
bgColor#F4F5F7

Do our OKRs tie into a greater strategy or vision?

Yes and no. Should they? Absolutely. But we’re a brand new branch and a pretty new division. Our leadership teams have some work to do around building all these foundational pieces.

For now, you should be able to see the alignment between our objectives and Mission 4 of the Digital Plan. Creation of the Digital Talent Strategy is a piece of work currently being undertaken by a cross-divisional executive group - updates on this work to come soon!

Panel
panelIconIdatlassian-question_mark
panelIcon:question_mark:
panelIconText:question_mark:
bgColor#F4F5F7

What on earth is a “Decoder Ring”?

Not quite as good as the prize at the bottom of your cereal box, but almost.

The Decoder Ring is a scoring rubric that Digital Office leadership teams use to estimate and compare the priority value of any piece of work we might bring into our backlog. If you’re part of the DO, you can find the latest iteration of the rubric and supporting documentation here. By charting how value something might have against how much effort or capacity it will take our teams, we’re able to make better decision about what we spend our limited time working on.