Wikimedia Language engineering/Process Overview

Management

 * 1) Engineering Director
 * 2) Product Owner

Coordination

 * 1) Scrum Master

Development Team

 * 1) UX and Interaction Designers
 * 2) Senior Software Engineers
 * 3) Software Engineers
 * 4) Associate Software Engineers

Sprint Duration

 * 1) Each sprint is of 2 Weeks
 * 2) In exceptional cases like travel, the team can opt for a shorter or longer sprint.
 * 3) A shorter sprint is not less than 1 week
 * 4) A longer sprint is not more than 3 weeks
 * 5) The team has opted for breaks to be taken in between sprints, to coincide with the quarterly travel schedules that last between 7-10 days.
 * 6) Sprint change i.e. closing and planning happens on the same day (unless a planned sprint break is to occur)

Product and Release Backlog

 * 1) User requirements brought forward by the Product Owner are included as stories in the Product Backlog
 * 2) The team does not maintain a separate Technical Debt Backlog and technical stories (i.e. independent of any user feature) are also included in the Product Backlog (as they surface)

Stories
A story typically begins in the analysis phase. Some of the important story properties as defined in Mingle are :


 * 1) Status – depicts where in the workflow, the story currently is
 * 2) Owner – the current owner of the story
 * 3) Priority – indicates the importance of the story.
 * 4) Story size –indicates the size of the story as small, medium or large. This property is meant to be used for early stage release planning when the team does not have complete details of all the requirements but do want to size the requirements and plan them.  The size is indicative and is relative to the rest of the requirements. The story size can be used to determine the right mix of stories to be allocated to each of the sprints and also to determine the sequencing of the stories.
 * 5) Estimated effort(hrs) – captures the estimated effort in hours and is used for sprint planning.  The requirements are analyzed and discussed in detail before the sprint commences and hence the team will be able to task out the requirements and estimate them in hours.
 * 6) Actual effort (hrs) – captures the actual effort spent on the story at every stage of the workflow. It is meant to capture the sum total of all efforts spent on a story including development, testing and review. It is the team member’s onus to ensure the effort is cumulatively captured.

Transitions
A typical story transition is as shown below :

Ready for analysis -> In analysis -> Ready for Development -> In Development -> Ready for Testing -> In Testing -> Review -> Ready for sign off -> Accepted

TRANSITIONS IN THE ANALYSIS PHASE
A story is typically created in the ready for analysis status and is moved to In analysis status prior to the commencement of the sprint.

TRANSITION : Ready for analysis -> In analysis

The following two properties are prompted during this transition:
 * 1) Priority  : High/medium/low ( Mandatory)
 * 2) Epic story ( Optional )

TRANSITION : In analysis -> Development buffer

( In case, stories are not top priority for the sprint or need some additional information ) The following four properties are prompted during this transition:
 * 1) Owner :  Assign the correct owner relevant to this stage of the workflow.  ( Should be the developer for all development stories )
 * 2) Story size :  Ideally this should already be captured but if not, system prompts for the size.  ( If it’s a newly introduced story )
 * 3) Estimated effort (hrs ) : This is not mandatory at this point but can be captured if the information is handy.
 * 4) Epic story: If you have missed associating it earlier, here is another chance to do so. ( Please note, it has not been mandatory as there will be stories without epics )

TRANSITIONS IN THE DEVELOPMENT PHASE
TRANSITION: In analysis -> Ready for development

TRANSITION: Development Buffer -> Ready for development

The following four properties are prompted during this transition:
 * 1) Owner :  Assign the correct owner relevant to this stage of the workflow.  ( Should be the developer for all development stories )
 * 2) Story size :  Ideally this should already be captured but if not, system prompts for the size.  ( If it’s a newly introduced story )
 * 3) Estimated effort (hrs ) : This is mandated at this point as the story is deemed ready for development.
 * 4) Epic story: If you have missed associating it earlier, here is another chance to do so. ( Please note, it has not been mandatory as there will be stories without epics )

TRANSITION: Ready for Development -> In Development This transition prompts for owner to ensure the person working on the story is allocated.

TRANSITIONS DURING THE POST-DEVELOPMENT PHASE
TRANSITION: In Development -> Ready for Testing

Once the story development is done and is ready for testing, the story can be moved to Ready for testing and the transition prompts for actual effort and handover of ownership for testing.

TRANSITION: Ready for testing -> In testing

Transition moves card to in testing phase.

TRANSITION: In testing -> Review

Post testing, when the card is moved to ‘REVIEW’, the transition prompts for actual effort and handover of ownership for the review phase. Please note the testing effort needs to be added onto the existing value in the 'Actual effort(hrs)' field (This field would have already captured the development effort through the previous transition).

TRANSITION: Review -> Ready for sign off

Post review, when the card transitions to ‘Ready for sign off’, the transition prompts for actual effort during the review phase.Please note the review effort needs to be added onto the existing value in the 'Actual effort(hrs)' field (This field would have captured both development and testing efforts through previous transitions).

TRANSITION: Ready for sign off -> Accepted

This is the final transition where the story is deemed done and moved to the 'Accepted' status.