Frontend Architecture Working Group/Process

From MediaWiki.org
Jump to navigation Jump to search

Logistics[edit]

An Agile Process[edit]

While this document represents a working guide based on the information we currently have, the best plans are those that adapt to new information and changing situations. Throughout the process, the individuals involved are encouraged to review the process, propose changes, and implement them in concert with the relevant stakeholders.

Explorations and rotations[edit]

There are five explorations in total for which the working group will develop a proposal. Generating a proposal is limited two calendar months. Members must be present for the entire two months to participate in an exploration, and be available for follow up such as retrospectives after the exploration. When complete, members can rotate out and new ones can rotate in.

Working group composition[edit]

The working group will have 6-8 individuals for each exploration (excluding facilitation and architecture support), selected by Product and Technology Leadership and WMDE. The size will be capped in order to maintain productivity and ease of communication and scheduling.

At this size it is not possible for the WG to have experts in every domain. Although not all disciplines can be in the working group, working group members can and should ask other staff and community members for information and opinions when developing a proposal, as long as it does not interfere with their regular work.

Time commitments[edit]

Working group participation is 8 hours per week (can be more, time allowing).

This time will be allocated between a combination of discussion time and async work, with at least 1 in-person meeting per week. The facilitator will determine this based on the group, problem, and other logistical concerns.

In order to participate in the working group, members must be able to commit to the 8 hours per week for the entire length of the exploration (maximum 2 months). For 1 month after the exploration, there will also be follow up, retrospectives and other debriefs that working group members should also make themselves available for.

Product owner[edit]

In addition to the regular working group members, the working group will have at least 1 product owner (as mentioned above), who is generally expected to be a product manager at the WMF or WMDE. The scope of the work that a PM is expected to do for the working group is the same type of work they generally do when developing any product plan. While product owners are not required to engage in all working group activities, they do need to commit to relaying product requirements, provide feedback to solutions and help guide the working group towards a project proposal that the product manager endorses. It is likely, but not required, that the sponsoring PM will be the PM for the project that is being developed.

Process[edit]

For each cycle the following process is repeated:

  1. Exploration selection (Leadership with Sponsors)
  2. Exploration definition and scoping (Mentrix and selected staff)
  3. Member selection (Leadership with Sponsors)
  4. Exploration kickoff (Entire working group)
  5. Solution development (Entire working group)
    1. The group works on 1 exploration at a time
    2. 1 month check in
  6. Solution proposal (Selected members of the working group)
    1. The output of the group is a proposal, ideally only one but can present multiple options with a preferred option
    2. In addition to the written proposal, the members of the working group should be prepared to present the proposal in a meeting

Project constraints and notes[edit]

Proposed projects must be complete able within 3 months. If a project is too big, the working group is encouraged to find ways to cut scope to deliver the minimum viable product and allowing the product owner to plan and schedule the next iterations to realize the full vision.

Projects will be planned and executed on a 2 week sprint schedule.

Project selection will be driven by the Product Leaders with consultation from PMs and engineering leadership.