Wikimedia Technology/Annual Plans/FY2019/TEC12: Developer Productivity/Goals

=Program Goals and Status for FY18/19=

TEC12 Developer Productivity
 * Goal Owner: Greg Grossmeier
 * Program Goals for FY18/19: We will streamline and integrate the delivery of services, by building a new production platform for integrated development, testing, deployment and hosting of applications. Wikimedia developers experience a tooling parity between our Continuous Integration (CI) and production environments which enables them to release code more frequently by continuously reducing risk.
 * Annual Plan: TEC12 Developer Productivity
 * Primary Goal is Knowledge as a Service: Evolve our systems and structures
 * Tech Goal: Support our Technical Community



 = Q1 Goals =

Outcome 1 / Output 1.1
Local development is unified with testing and production
 * Create a production tooling compliant Dockerfile that sets up a basic LAMP stack, installs MediaWiki, and can run unit tests. (more)

Dependencies on: WMF Recruiting

Goal(s)

 * Make a hire to create the capacity needed for this program.

Status
July 2018

August 10, 2018
 * - blocked on filling the senior hire (backfill)

September 14, 2018
 * Interviewing is and might go into the month of October to find the best candidate.

December 6, 2018
 * A hire has been made in late November 2018 and this part of the goal is ✅

Outcome 2 / Output 2.1
Developer satisfaction improves year over year
 * A survey is created and shared with all Wikimedia developers to measure overall satisfaction and productivity as well as identifying the most sought after needs. The top needs are shared as key goals for the team.

Dependencies on: WMF Learning & Evaluation and WMF Legal teams

Goal(s)

 * Write and share a survey to measure developer satisfaction and areas for investment. -

Status
July 2018

August 10, 2018

September 14, 2018
 * This is now, but might go into the early part of October for privacy policy, etc.



= Q2 Goals =

Outcome 2 / Output 2.1
Developer satisfaction improves year over year.


 * A survey is created and shared with all Wikimedia developers to measure overall satisfaction and productivity as well as identifying the most sought after needs. The top needs are shared as key goals for the team.

Goal(s)

 * The Annual Developer Productivity Survey results are synthesized and shared, creating a first year baseline.

Status
October 2, 2018
 * This is not yet sent. status for now.

November 7, 2018
 * Survey sent. - https://lists.wikimedia.org/pipermail/engineering/2018-October/000629.html

December 6, 2018
 * Discussed our progress so far - the survey has been sent and needs to finish up reviewing and then publish the results, thus, it's . However, we'd like to continue this goal in Q3 to get more feedback.



= Q3 Goals =

Outcome 1 / Output 1.1
Local development is unified with testing and production
 * The goal for 1.1 has changed and we need to do some background information gathering first to help inform on how we can create a tool that can be used by developers that has platform parity with continuous integration and deployment.

Goal(s)

 * Conduct interviews with development stakeholders and compile a report that informs future work creation of a rubric.

Status
January 2019
 * Discussed...

February 2019
 * Discussed...

March 2019
 * Discussed...



= Q4 Goals =

Outcome X / Output X
Lorem ipsum dolor sit amet, consectetur adipiscing elit.
 * Nullam interdum, elit in malesuada aliquam, libero lorem auctor lacus, eu mattis lacus velit vitae mauris.

Dependancies on: ___________

Goal(s)

 * Ut eget sodales odio. Maecenas a varius leo.

Status
April 2019
 * Discussed...

May 2019
 * Discussed...

June 2019
 * Discussed...