Showing posts with label Agile. Show all posts
Showing posts with label Agile. Show all posts

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

Monday, November 21, 2011

#Agile is about getting functionality out

Many software development projects fail to get functionality in a timely manner. Often all functionality is released all together and it has to function to the nth degree. Usually it doesn't and usually the users of the new functionality grumble and object. The Wikimedia Localisation team does not produce everything in one go. What it does is produce functionality that is described in a story
Alolita wants to edit to localise the translatewiki.net user interface in Hindi and uses the Narayam functionality to mimic a Devanagari keyboard. She is not able to type blind and she uses a mock-up of the keyboard to find the keys she needs to press
In Agile this is called an "user story" and for us it is part of the Narayam "epic story". This story is analysed, it is divided in tasks, they are given points and every fortnight it is decided what stories to implement in the next sprint. Those stories can be quite rough around the edges consider; a story that takes as a premise that the user can type Hindi blindly is already in production.

The point of the stories is that they describe precise functionality and this is what is realised in a limited time frame. These stories are selected at the beginning of a sprint and consequently not only does new functionality get frequently realised and implemented, priorities for what the language team is to do are also constantly re-assessed.

Our hope is that our users; the Wiki communities will find us responsive. Our aim is to make the gap  between the user-experience in English and any other language as small as we can make it.
Thanks,
      GerardM

Monday, October 24, 2011

#Language options looking for an iteration II

When you expect a user to understand a language, you can be wrong. Everyone has no experience for most of the languages we have Wikipedias in.

Niklas experimented using data from the browser to suggest an appropriate interface.  Obviously more needs to be done but as it is such an obvious improvement to our usability. The experiment was happily received with not too many words :)
Thanks,
       GerardM

Sunday, October 23, 2011

#Language options looking for an iteration

At #translatewiki.net we live at the #MediaWiki edge.. Living at the edge brings you surprises. It brings us for instance a language drop down thingie with weird options. Dutch, British English, English and American English.

Typically my user interface is set to English so I changed it to Dutch to see if it would pick up the fact that there is Belgian Dutch, formal Dutch and Dutch. It did not; it only translated these "language options" into Dutch and it did not sort them properly.

I then checked the options for English only to find that it did not pick up on Canadian English as being a valid option. American English is not even an option.

This fun event will be mentioned at the "stand up" meeting of the Localisation team. It will be interesting how the "product owner" will evaluate this new functionality and if and how our team will deal with it. Whatever the result, I do not expect that too many words will be used.
Thanks,
       GerardM

Wednesday, October 19, 2011

The #agile #bugmeister

The #Wikimedia bugmeister works in an environment where increasingly more development teams adopt agile for their project management. As the function of a bugmeister is not defined in agile, the question was raised during the training for the localisation team what a bugmeister is in an agile environment.

We love our bugmeister and, we want to fit him in. The short answer is that a bugmeister represents aspects of both business analysis and quality control. The long answer has it that software is accepted based on the compliance of a "user story" in the software. For a reported bug to be a bug in the understanding of agile, it does not comply and it results in a user story explaining the breakage. The existence of a bug may also indicate that a "user story" exists where the existing functionality does break. The analysis of such a situation is what a business analyst does. The resulting user stories are presented to the "product owner" for inclusion in a next sprint.

When the previous paragraph sounds like gobbledygook, it is very much because of the specific terminology used by agile. Having specific terminology is a good thing because it forces an agile newbie to consider and reconsider his understanding of what is expected of him or her.
Thanks,
      GerardM

Sunday, October 02, 2011

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

Friday, September 30, 2011

#Agile training at the #Wikimedia Foundation

The #Localisation team consists of people who are used to each other. We worked together for a long time and now it is a job. With a job come dreary things, things like time management in order to be paid but it makes available time to spend on the real issues that are so dear to our heart.

With more time and with being part of the team of MediaWiki developers all kinds of things change and need to be addressed. As an amateur (ie non paid professional) you choose what you want to be involved in. Siebrand did the project management as well as being the working "first among equals" and in reality he has been herding cats.

The carrot and stick approach worked well; if you code this it will go live soon or if you localise these messages first, your Wikipedia will be more usable. Making sure that the environment was optimal for getting the jobs done has always been part of project management.


Now that we are a team intending to work with best industry practices, it is wonderful that the Wikimedia Foundation knows about best practices and intends to implement them in the various disciplines in the organisation. For software there is agile and we have the good fortune to have two days of training by Hai from ThoughtWorks.

The good news is that as a result of implementing an agile management style, we will have frequent updates of language related software. We will have a lot of communications particularly with the language support teams we are setting up about functionality and requirements (both ways) and we expect that as a result many great languages will get all the readers and editors they deserve.
Thanks,
      GerardM

Saturday, September 24, 2011

Q&A with the #MediaWiki #bugmeister

As more developers are working on the MediaWiki software, keeping a grip on the outstanding issues becomes more then a day job. Mark Hershberger has as its task to manage the needs of the community and does this in a hands-on fashion by bringing focus to the bugs reported in Bugzilla.

He has been doing it for a while now and this interview may give you an idea why having a bugmeister is a great idea.
Enjoy,
      GerardM
Can you explain what a bugmeister does
The main idea of a bugmeister, is clear from the posted job opening. This basically says that the bugmeister acts to bring the community's issues to the attention of WMF Project Managers and Developers. In addition to making sure the community's needs are heard, I've also worked recently to get the developers from the community involved in WMF activities. For example, I'll be hosting a fund-raising-focused triage in a few weeks where community input is wanted.

There seems to be more work then can be done by one bugmeister, is it true that by focusing on what needs the most tender love and care, you pick from the low hanging fruit ?
There are a lot of bugs in Bugzilla (over 6000 open issues right now) so I admit that bug-solving is driven somewhat by the squeaky wheel since those are the issues the community has shown the most interest in.  I do want to chew through those other bugs but I think that focusing on the new bugs and most-often referenced old bugs will get a lot of these bugs handled.

WMF is very much into agile development, is a bug triage something that you do at the beginning or at the end of a sprint
Good question.  I'm not sure I have an answer, but let me try.

Part of the purpose of triage -- at least how we're using it at the WMF -- is to understand problem reports and how to solve them and, after that, to assign them to a team or a person to work on.

So, as far as I understand sprints, triage would happen at the beginning.

Identifying and assessing the new bugs is what I understand you do. How does this fit into the process of fixing bugs
This varies with how high a priority the bug gets. For a quick overview of the time-line of my involvement time-line see the documentation on MediaWiki.org.

For example, bugs that are "highest" priority get very close attention. "high" priority bugs less so, and so on.

Every week there are more new bugs then there are bugs that are marked as fixed, how significant is this?
First, the weekly bug report isn't completely accurate -- it has some bugs.  For example, I noticed recently that it had reported 594 bugs created in one week when a query shows only 122 were created that week.

Second, it is normal for projects with open bug reporting tools to have more bugs created in a given period than closed.  I'm having trouble finding the report at the moment, but I recall seeing Mozilla Firefox had more bugs opened in a year then closed.

There is a perceived lack of people working on the review of software, can you comment
Over the past year Rob Lanphier has worked to get more people reviewing the code since, yes, we had too few people doing code review. We're in a lot better position now, but we still do not have the resources to review every bit of code that is in subversion.  I'd rather make the code repository and code distribution available to anyone who wants to extend MediaWiki, since this is better than telling people "We can't review your code, so it isn't welcome!"

As an example of how code review has gotten better, Rob Lanphier and I have been doing a lot of work on getting code reviewed faster and code marked FIXME fixed faster as we ramp up to a 1.18 deployment. This is a big pain point since we want to make more frequent releases of MediaWiki and become, as you pointed out, more agile.  And we don't want to release un-reviewed code.

I think, though, that if you look at the way FIXMEs have been resolved, or how new revisions have been reviewed, that you'll see some very good trends. In the past few weeks we've really been driving unreviewed code down pretty hard.  I'm confident that we can continue to keep unreviewed code low.

Code not written by WMF employees is certainly reviewed -- especially if it is going to be deployed on the site or released as part of MediaWiki. Since we only have limited resources, we cannot review all code in our Subversion repository.

For example, we host Semantic MediaWiki and extensions, but this code is not used on any Wikimedia website and is not distributed as part of MediaWiki, so, in order to make sure that the code we do release reviewed, we have to ignore Semantic MediaWiki for the most part.

An example of MediaWiki code that is not used on the cluster, but that is reviewed is the new Installer for MediaWiki or code that supports databases other than MySQL (such as PostgreSQL).  But, when it comes to Database code we're somewhat limited in our ability since we're so focused on MySQL, so we are looking to recruit volunteer reviewers who use and are familiar with the other databases that MediaWiki can use to help review this code.

Siebrand indicated that the presence of people from many disciplines was why the recent i18n bug triage was so successful. How does this mix with the small teams typical of agile?
Triages are more successful when more people are involved, true. Since a basic part of the Bug Triage, at least in the way I've been running them, is open community involvement -- I hold the triages on IRC and everyone is invited -- I don't think we're limited by small teams.

What is the measure of your success; is it in the volume of work done on bugs or is it in a changed way or working of the developing community or is it a mix of things
I think it is still too early to answer that question definitively. I'm actually working with a researcher to find out what sort of metrics we can find in the bug database to draw good conclusions about community involvement, # of bugs solved, and the like.

A function like a bugmeister seems far removed from the community editing on the projects, do you and how do you keep informed on what happens in the projects
I work with different community members to enable editing on the projects. Extending the functionality of a project like we did with the Google News Site Maps (GNSM) extension on wikinews is a big part of that.

This coming Wednesday, I am having a WikiBooks-focused triage with some people from that community that I met in the Collection extension triage. During this time we'll be able to find out how we can help their project succeed more.

What is your favourite MediaWiki project, what is the most challenging project
I admit a soft spot for WikiSource, but this is mostly because I think we could use it to provide a community-driven replacement for ReCaptcha. Google is using ReCaptcha to help the New York Times scan in old newspapers, but, as far as I can tell, they aren't making the result publicly available. I think we can do better.

Thanks,
Mark.

Monday, September 12, 2011

#Agile the process works !!

The "stand-up meetings" of the Wikimedia L10N team are great. Every day in the European morning we learn briefly about the latest developments, the work done, the work planned for the day. .

Stand-up meetings are part of the agile / scrum software development. They are great because you learn about what the current issues are.

What you are looking for is how things like stand-up meetings are worth their time. We wrestled with support for Narayam in the Chrome browser. Amir was fixing an issue with searching strings and was struggling with Chrome as well. Thanks to the stand-up meeting we learned early on that both Narayam and WikiEditor Search are likely to suffer from the same underlying issue.

The amount of time saved is a benefit. The real benefit is that it helps us to become more of a team. A team that understands that everyone in the team is a resource that can be drawn upon.
Thanks,
       GerardM