linaro-project-management team mailing list archive

[Joey Stanford <joey.stanford@xxxxxxxxxx>]

FYI.

Attached is a screenshot of the backlog view.


---------- Forwarded message ----------
From: Lee Jones <lee.jones@xxxxxxxxxx>
Date: Tue, May 24, 2011 at 3:24 AM
Subject: ST-Ericsson Landing Team Shake-Up
To: ST-Ericsson LT Mailing List <st-ericsson@xxxxxxxxxxxxxxxx>
Cc: Scott Bambrough <scott.bambrough@xxxxxxxxxx>,
"anmar.oueja@xxxxxxxxxx" <anmar.oueja@xxxxxxxxxx>, Joe Bates
<joe.bates@xxxxxxxxxx>, Victoria Janicki <vicky.janicki@xxxxxxxxxx>,
Joey Stanford <joey@xxxxxxxxxx>


Hi ST-Ericsson Landing Team,

Just in case you were not in the relevant sessions at LDS and are
subsequently unaware, Linaro are in the mist of a Project Management
shake-up. We have just hired a handful of new Project/Program Managers &
Directors and are changing the way in which PM'ing is conducted
throughout Linaro. A large part of the change will be the method we use
to run projects. The majority of the teams are moving to a more Agile
[1] style of Project Management.

In keeping with the remainder of the company, I have decided to give it
a shot. However, we are not without hinder. Due to the way in which the
team's tasks are delivered, it is extremely difficult to predict what
the we will be working on too far in the future. Therefore, we will be
using a derivative of Scrum [2] where we will be working only in weekly
Sprints and will have no Release per-say.

To start us off, I have authored a document which is currently
masquerading as a sheet on the Driver Status document [3]. There you
will find the Product Backlog. This is a list of tasks that we as a team
would like to undertake and complete. Please note that this list is not
exhaustive. In it's current state it only details the work-items in the
Driver Status document, however items can be appended to this list by
anyone as tasks arise. For instance any upcoming Snowball tasks are yet
to be identified.

Once we start a weeks work there will be no stopping or changing task.
Obviously we will remain flexible with super-high priority tasks, but
for the most part when you start working on something you will not stop
until it is complete. This will allow us to see exactly where we are
with regards to a particular task and how much time is required to
finish it/them off.

If you are a member of ST-Ericsson and you have other responsibilities
we will factor that in. For that to happen I require a percentage
of the amount of time you will be spending on Linaro work. If for
example you pledge 50%, you really do need to compete 2.5 days or 2.5 x
(hours in the working day) in that week. This method has an added
advantage in that it will give us leverage to escalate any issues with
pledge slippages to ST-Ericsson's management; hopefully resulting in
more solid future pledges from some (*cough* Graphics *cough*) teams. :)

We will conduct a weekly meeting, either at the start or at the end of
the working week. This is called a Stand-up Meeting. Each person will in
turn state the work they completed in that week and what they plan to
work on the next week. I plan to be fairly fluid in the way tasks are
allocated. Basically you will pick your own tasks and provide your own
estimates of how much work you think is required. Once agreed you will
then be free to work on that task and nothing else. Any other Landing
Team tasks that arise must be bought to my attention prior to conducting
work on them - 90% of them will hit the Product Backlog and will have to
wait until the next Sprint (week) begins.

If you have any questions or queries about what has been mentioned in
this email please feel free to contact me privately or reply to all. I
will be only too pleased to answer them. Remember, if you have a
question or do not understand something, there are probably others in
the same boat, so speak up.

Kind regards,
Lee Jones
ST-Ericsson Landing Team Lead

[1] http://en.wikipedia.org/wiki/Agile_management

[2] http://en.wikipedia.org/wiki/Scrum_(development)

[3] http://tinyurl.com/44g9xab

Attachment: Screenshot-ST-E Kernel Driver Status - Mozilla Firefox.png
Description: PNG image