Thursday, December 22, 2011

Workable code is not always deployable code

The #Wikimedia #Localisation team cranks out code, workable code - every sprint. At the end of the sprint, for us a sprint lasts a fortnight, all the completed "stories" are tested against their acceptance criteria and when the tests are good, they are signed off and marked as completed.

With this jargon out of the way, it is possible to consider features.

The Translate extension needs an additional feature to help translation administrators manage their work. Pages that have been marked for translation have a life-cycle; at the start they are marked for translation but at a later stage there is no longer a need for translation. Such a status change has an impact on what translators are to see.

There are many stories that make up the Translate status feature, for instance:
  • you can watch the list
  • you can change the status on a text
  • the list is different depending on the role of a user and the status of a text
A sprint is run in a fixed amount of time. In a sprint there often are stories for multiple products. When the stories do not provide enough functionality for a feature, additional stories will make it in the next sprint. When you read this carefully, you may appreciate that "enough functionality" is not the same as "feature complete". The point is very much that with Agile we get feedback as soon as possible.

When you are interested in the stories in our current sprint, have a look in Mingle (user: guest - password: guest).
Thanks,
      GerardM
Post a Comment