linaro-project-management team mailing list archive

[David Zinman <david.zinman@xxxxxxxxxx>]

Greeting,

Here is the postmortem and lessons learned for Linaro's first release for 2012.

 https://wiki.linaro.org/Cycles/1201/Release/Review


Highlights and Key Successes
============================

The Ubuntu development platform team has delivered Ubuntu TV
fully accelerated on a PandaBoard with Ubuntu LEB and the Ubuntu
TV UI and XBMC also for PandaBoard.

 http://www.youtube.com/watch?feature=player_embedded&v=uQMOETMZA5Y

The members demonstration was very successful with the graphics WG,
landing teams, verification team, platform teams and the Igloo community
all contributing some very fine achievements to the effort.

Internal communications have been getting better and there is now a
weekly sync between the platform groups and the working groups that
is similar to the platform - landing team syncs. Each team brings a high
priority issue or but to the table in order to find a plan for resolution.

Postmortem and Lessons Learned
==============================
This cycle seemed to present a challenge to most of the teams to stay
focused on the delivery, There was no release from the Power Management
group, and output was down for the Multimedia, Graphics and Platform
teams. An issue here is that some release procedures are not being
followed by some of the teams.

An important issue that came up this cycle is that platform teams are
requesting the source code for binary blobs. At integration, when an
issue has been found, the path to the person that can fix and regenerate
the binary blob is too long to actually fit the integration into one cycle.
Add to this the requirement to use kernels and toolchains that are not
aligned with the binary blobs and a conflict is created between
development and schedule.

Some of the lessons learned that came out of the cycle are:
 * There needs to be offspring knowledge within the infrastructure. The
   resource that had this domain knowledge is no longer with Linaro. To
   be effective, this knowledge should be brought in house again.
 * Listen to community users and incorporate useful information and
   go to people directly to get their reviews.
 * Need to become better at declaring scope which has good probability
   to be delivered at the beginning of the cycle, rather than declaring all
   pieces of work that we want to work upon and shed items which are
   impeded on the way. Impediments should be highlighted early on to
   get resolved.

-- 
David Zinman
Linaro Release Manager | Project Manager
Linaro.org | Open source software for ARM SoCs