feat: add OKR, agile and Jira delivery practices

[jdhoffa]

Adds a compact documentation for how teams define outcomes and run agile delivery.

Added:

• an OKR guide
• a tool-agnostic Agile overview
• common agile ceremonies for sprint cadence
• a Jira runbook for implementing the workflow
• a (very) brief note on using Atlassian Goals for OKRs

This layout separates outcome-setting (OKRs), operational delivery model (Agile), and tool-specific implementation guidance (Jira).

[AlexAxthelm]

Overall good for me

[john]

This is great. No problems but if you could address my comments where it makes sense I'll then approve.

[john]

We've talked about adapting process to the scale of the work at hand--for many projects I think we may want to skip the epic step. Can we note that we adapt to scale, and as an example epics can be optional if appropriate? Personally I almost always skip them, but I see them being employed effectively on our larger projects so I'm not opposed to it being a recommended option. Just don't want anyone thinking they're doing something wrong if they're not creating epics for their two month project.

[jdhoffa]

Yeah "Epics/Stories" is sort of meant to reflect that.
If the project is big, the PRD probably benefits from being split into Epics, of not you can go straight to stories.

I can just write PRD -> Tickets to keep it generic enough here? I don't think the overview page is the place to get into too much detail about ticket types (that happens in jira.md).

[jdhoffa]

This is great. No problems but if you could address my comments where it makes sense I'll then approve.

Addressed most of your comments. Let me know about the Epics/Stories split :-)

[jdhoffa]

@rosewangrmi I have:

• Update guidance for "async" standups
• Removed "core team" from backlog refinement, and added adhoc SME or engineer attendance, as required

Let me know if that sounds good :-)