Page MenuHomePhabricator

[GOAL]: Document definitions and development processes for the different types of software work and how they progress from one stage to the next
Closed, DeclinedPublic

Description

Define processes and tools prototypes/experiments/features

Why

Differentiating between prototypes, experiments and stable features will help
scope our different pieces of work and classify them on the pipeline where they
belong.

Improving our processes and tools will allow us to create prototypes easily,
perform multivariate testing, and stabilize features in a clearer way.

Current situation

Everything is a prototype, at some point we transform it to a beta feature and
after some time we pass it to stable often without sign off. Everything is always
in production or just on local developer's machines. The criteria for moving from
prototype to beta feature to stable aren't clear.

Objectives
  • Create and document definitions and development processes for the different types of work (prototype, beta feature, feature)
  • Create a process for process for promoting/discarding prototypes and beta features
  • Feature flag our different features through our properties. Enable the needed features on production. Enable experimental, incomplete or deprecated features on staging.
  • Document and implement how to A/B test in our platform for running experiments.

Event Timeline

Jhernandez claimed this task.
Jhernandez raised the priority of this task from to Medium.
Jhernandez updated the task description. (Show Details)
Jhernandez added a subscriber: Jhernandez.
Jhernandez renamed this task from Document definitions and development processes for the different types of software work and how they progress from one stage to the next to [GOAL]: Document definitions and development processes for the different types of software work and how they progress from one stage to the next.Jul 31 2015, 4:22 PM
Jhernandez set Security to None.

@pizzzacat FYI this was one of the goals we wanted to research and define, at least start talking about it and clarifying it as much as possible.

It would be great if you could keep me/us in the loop, since you told me this is in your areas of interest right now, maybe we can help!

How should we sync on all this?

I drafted this a while ago, which may be of some use.

Jhernandez changed the task status from Open to Stalled.Jul 25 2016, 4:04 PM
Jhernandez removed Jhernandez as the assignee of this task.

Product should be involved in this

Jdlrobson renamed this task from [GOAL]: Document definitions and development processes for the different types of software work and how they progress from one stage to the next to [GOAL]: Document definitions and development processes for the different types of software work and how they progress from one stage to the next.Jul 1 2020, 9:46 PM
Jdlrobson removed a project: Readers-Web-Backlog.
Aklapper changed the task status from Stalled to Open.Jul 25 2020, 5:13 PM
Aklapper lowered the priority of this task from Medium to Low.
Aklapper removed a subscriber: pizzzacat.

The previous comments don't explain who or what (task?) exactly this task is stalled on ("If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on"). Hence resetting task status.

Closing this open WMF-Product-Development-Process task as that project seems dead for years (see T253629). Feel free to reopen this task either if someone will take responsibility, or if this task should remain open and (!) tagged with some other active (!) project tag. Thanks a lot!