Wikimedia Apps/Team/iOS/Development Cycle

The following is an outline of the team's standard process. It is important to ensure that everyone has a shared understanding of what each phase means. There are no pre-set dates or durations for phases, as the team will discuss timing as they work and agree together on when to move from one phase to the next.

Stories and Scope

Create initial board with epic stories

Design Research

Comparative analysis

Present design proposal

Fill in epics

Exploratory Stage

Engineers research and experiment with design, deliver prototypes for testing

Initial evaluative user testing

Most major unknowns should be identified, remaining work is understood

After giving their update, each person chooses who goes next by saying the other person's name.

Share what you've worked on

Share what you'll be working on

Share what's blocking you

Product Owner

Engineers

Designers

Tech Program Mgr

Task Sync

once a week

50 min

Team meets to sync up on what they're up to and decides if any tasks on the current release board need to be discussed and/or estimated. The first part of the meeting is a classic standup. Part of the meeting is dedicated to reviewing user feedback - team members take turns gathering user feedback before the iOS Task Sync and share the findings with the team during the meeting.

Share what you've worked on

Share what you'll be working on

Share what's blocking you

Establish if there's enough work until the next meeting

Review the Needs Engineering Sync & Ready for Development columns on the current release board

Move tasks from Needs Engineering Sync to Ready for Development, if applicable