Fwd: dev ops split?

We started responding directly, perhaps without realising. Thanks for
all the responses.

---------- Forwarded message ----------
From: M. Manca <m.manca <at> micronengineering.it>
Date: 2012/4/24
Subject: Re: [XP] dev ops split?
To: Otto Behrens <otto <at> finworks.biz>

Il 24/04/2012 17:51, Otto Behrens ha scritto:
> Thanks for the response
>
>> First of all in my teams it is not possible that an engineer choose by
>> yourself an out of order user story from the backlog. Normally if there are
>> stories that have to be done by specific engineers I sign them in a
>> different way (may be a different background color). If the specific stories
>> are not so much I manage a board with a single lane if not  I manage a multi
>> lane board specifing who can take the specific type of stories.
> How do you decide which engineer does works on what lane or task? Is
> the multi lane board not a form of split in the project team?
I work on embedded projects so for me is common to have engineers
involved in the application software and others involved in o.s.
software. In other project types may be there are engineers working with
a db and others at the application and so on.
>
>> In any case the policy is that the 1st free engineer has to take the story
>> on the top of the backlog (or the story on the top of the stories ready to
>> start). This situation may be managed differently if there are senior and
>> junior engineers in this case introducing pair programming may accelerate
>> learning for junior engineers.