Looking forward to write #agile user stories

A good joke has a kernel of truth. Agile allows for less documentation, maybe even no documentation and a developer does not need to plan beyond the duration of a sprint. When you start with agile it first goes all haywire and yes the writing of code is what delivers functionality.

I will not be writing code, I will be writing about the functionality that is being developed or has been delivered. Such stories will be in English, short and sweet. They may contain screen shots or pictures that amuse and they are intended to have more people find their way in the most multi-lingual software of all; MediaWiki.

Functionality developed with agile will not appear fully formed like Pallas Athena out of the head of Zeus. It will grow more organically. As experience shows users will surely find ways to use the delivered functionality in ways that were not considered.

As we learn what works and why or what does not work and why, we will collect your stories. These stories are in turn converted in agile user stories and may be decomposed in multiple related stories. Such stories end up in the product backlog and will be prioritised and maybe developed.

There is for instance a user story in this example of Wiktionary template hell:

* Japanese: {{t|ja|スクラム|tr=sukuramu|sc=Jpan}}

The  story may be about editing Japanese, it can be about how the Japanese text was entered or how it has to be shown to a reader. We do want to learn from you what this is all about. For this we need you and becoming part of a language support team is a short cut to getting our attention.
Thanks,
        GerardM