Team Practices Group/Health check survey/FY2014-15Q1
The Team Practices Group (TPG) was dissolved in 2017.
 | This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. |
This is the health check survey used for FY2014-15 Q1.
| Focus area | Awesome example | Crappy example | Influencers/indicators |
|---|---|---|---|
| Releasing | Releasing code is simple, safe, painless, and mostly automated. | Releasing code is risky, painful, lots of manual work, and takes forever. | |
| Process | Our way of working is perfect for us and our collaborators. | Our way of working sucks. |
|
| Code quality | We're proud of the quality of our code! It is clean, easy to read, and has great test coverage. | Our code is a complete mess, and technical debt is raging out of control. | |
| Value | We deliver great stuff! We're proud of it and our stakeholders are really happy. | We deliver crap. We feel ashamed to deliver it. Our stakeholders hate us. |
|
| Speed | We get stuff done really quickly. No waiting, no delays. | We never seem to get done with anything. We keep getting stuck or interrupted. Stories keep getting stuck on dependencies. |
|
| Mission | We know exactly why we are here, we are really excited about it, and we understand how our work aligns with the WMF's mission and priorities. | We have no idea why we are here, there is no high level picture or focus. Our so-called mission is completely unclear and uninspiring. We have no idea how or if our work aligns with the WMF's mission and priorities. |
|
| Fun | We love going to work and have great fun working together. | Booooooooring. |
|
| Learning | We're learning lots of interesting stuff all the time. | We never have time to learn anything. |
|
| Support | We always get great support and help when we ask for it! | We keep getting stuck because we can't get the support and help that we ask for. |
|
| Destiny | We are in control of our destiny! We decide how to organize ourselves and how to build things. | We are just pawns in game of chess, with no influence over what we build or how we build it. |
|
| Open-source citizenry | We're active participants in the development of software on which we rely (upstream) and software that relies on our software (downstream). We collaborate with and receive high-quality and relevant contributions from the broader open source software community. | We have an actively hostile relationship with another open source project and/or the broader open source software community. We've forked an upstream project because we can't get what we need merged and we barely support the fork. We receive no or only low-quality/irrelevant contributions from the broader open source software community. |
|