Shortly after announcing the Ubuntu Phone, we made an ambitious and frankly unprecedented decision to make the development of the phone’s core apps a community initiative. We weren’t just open sourcing the apps being developed by Canonical (though we did that too), we would let the community drive the design and development of what would become the foundation of the Ubuntu Touch app ecosystem. And we would do it ten short months.
Work Item Tracking
Building 11 apps in less than a year is a lot of work, and tracking that work is itself a lot of work. To do this, we are using the same tools and process as the rest of Ubuntu’s development. This means using Launchpad for code hosting and bug tracking. But more importantly, it also means using Blueprints for planning, breaking the work into individual tasks, and assigning those tasks to individual contributors. This also allows us to use the Ubuntu Status Tracker to view the progress being made on those tasks. As of right now, that chart looks like this:
As you can see, when we started tracking them we had about 165 work items defined, and about 140 left to finish. As tasks are completed, and the developer updates the Blueprint with the new status of the work item, the orange part of the chart will shrink, and the green part will grow. If we can keep the green part on or below the black line, then we’re on track to finish them all by our October goal.
Ten months is a short amount of time to build a collection of well designed and polished apps, but it’s also a very long time for planning development work. In order to narrow our focus and concentrate on immediate development tasks, we’ve further broken down the development period into a number of milestones, one for every month between now and October.
So instead of planning out the entire cycle, we will be scheduling tasks on a monthly basis. This will make the amount of work seem less daunting, and also give us a more agile cycle of planning, development, and evaluation. Each milestones will in turn get it’s own burn-down chart, so we can track the progress being made within the month as well.
Work items are also separated by team, which allows us to track the progress of individual projects, as well as the overall projects of the core apps campaign.
This allows teams to easily check if they are on track to complete their project by October, and also gives them an idea of how much (or how little) work remains to be done.
The first milestone, coreapps-13.10-month-0 is coming up in mid-April. For this milestone, we have been scheduling work items that were already making good progress, or that were small enough they could be completed in the two weeks between when it was defined and when it ends.
The milestone after that, ubuntu-13.10-month-1, ends mid-May, and will be our target for an alpha-level release of most of the apps. As you can see, there is still a lot of work to be done between now and then, but we are currently below the burn-down line, so as long as we keep the momentum going we will make that goal.
Everything not currently scheduled for one of these two milestones is targeted to the final October goal. Sometime in May we will begin scheduling work items for the coreapps-13.10-month-2 milestone, based on the progress made on these first two miles.