Now that we have published a 2-pager summary on wiki, should we send an email to everyone who we invited into one of our conversations?
|Resolved||None||T113053 [EPIC] TPG selects and documents a strategy|
|Resolved||• KLans_WMF||T133928 Email TPG strategy outcome (and maybe lessons learned too) to stakeholders|
|Resolved||• ggellerman||T131804 Document lessons from TPG strategy process|
- Mentioned In
- T133949: Post-IRL task: follow up on publishing some lessons learned re:strategy to WMF
T131100: Document and justify the choice of Improved Status Quo based on results of Q3 strategy tests
- Mentioned Here
- T131100: Document and justify the choice of Improved Status Quo based on results of Q3 strategy tests
Subject: Update on Team Practices Group Strategy process
I'd like to share the final outcome of the TPG strategy process with you. The voices of our stakeholders in the organization factored deeply into our decision - thank you for participating!
tl;dr - we're sticking with status quo. That is, we will not make any significant changes to how we currently operate. However, being TPG, we plan to make incremental adjustments to how we work, based on what we learned.
You can read a summary of our decision and rationale here: https://www.mediawiki.org/wiki/Team_Practices_Group/Strategy_process_FY2016/Decision_and_lessons
We've also documented what we learned from the process here: [link TBD, dependent on finishing T133928: Email TPG strategy outcome to stakeholders? ].
Thanks again, onward!
- Kristen and TPG
Looks good (subject to the "what we learned" stuff. And I might add at the end of the tl;dr something like "However, being TPG, we plan to adjust how we work, based on what we learned."
For the "to", I would propose: Everyone we invited to a strategy-related test meeting, including our agile skeptics.