Showing posts with label team building. Show all posts
Showing posts with label team building. Show all posts

January 8, 2012

Empower the Product Owner

"Let's empower the product owner role fully!  If the product owner is the one ultimately responsible for the results of the product in the marketplace, then they are the "source and decision-maker" for things like budget, scope, approach, market/product timing.  These were things PMs respresented before but PMs were always just "middle men."  With agile, we put that work where it naturally occurs  –  with the PO.  So, when we're thinking of the "PM stuff" that Scrum does not prescribe, think of the role of PO  (plus, the role of the trash bin, because that's also where some "PM stuff" goes)."  Lyssa Adkins, Post in Lyra Mentor Group 2011
Planning an agile team structure is fun - redistributing the power as a result of introducing Scrum within an organisation is a delicate topic. Getting real with implementing the roles is where the hard work starts including the discussion about empowerment. How far can a product owner and thus a Scrum team go, where is the limit of their empowerment? How much do the managers trust their freshly born product owners and what responsibilities will they delegate to them and to which level? The product owner role links the agile organization with the rest of the company (world) which may be less or not agile at all. Thus the answers to these questions highly depend on the context's level of agility and may not be black and white but grey  –  and may evolve over time. 

Jurgen Appelo provides a simple yet powerful game called Delegation Poker to shed light on this grey area and foster an open discussion about the delicate issue of empowerment. The result of using this tool is an authority board which defines the level of freedom for Scrum teams and visualizes the walls within self organization may happen. Here is what I have learned using the tool with managers and product owners within an agile transformation. I plan two or even three iterations – timeboxed to 60 –120 minutes – with different focus depending on the size of the group and level of agreement about the management style within the group. One first dry run helps to get a clear picture of how the group wants to work together, an understanding of the work to be delegated and of the meaning of the delegation levels. It's also fun to use the winning element in this round so everyone tries to understand what delegation level may be best suited for the whole group. Another question that should be raised during the first round is how he delegation level will be implemented thus questions like 'uups agreement sounds so nice – we all want to be very polite right? – but isn't that a hell of work if we have to discuss about every user story in detail?'. 

The second round focuses on getting real with the responsibilities and their delegation level thus requires that everyone in the group understands the work of the product owner. A simple diagram mapping the flow from an idea to product increment helps to identify the most interesting spots for discussing the delegation level. 

It's essential to make clear how to deal with multiple hierarchy levels, e.g. CTO, product owner and direct line manager of the product owners. A simple diagram will do the job to clarify which hierarchy level is represented at the poker table. The full chain of power delegation being present in the game is necessary for coming up with binding results. Surprising differences between middle and higher management may surface during the game and result in insightful discussions about leadership style. Nevertheless the resulting authority board is most useful when the product owners (or any other group it is designed for) can take it and look up their level of freedom thus the discussion should be focused on the delegatees and not so much on the different viewpoints of the managers who delegate. 


The expected timeframe the authority board is supposed to be valid or will be revisited again should be made clear in advance: is the group discussing about the status quo or crafting a vision for the future or just the next step which includes a small challenge. I prefer not to use the winning mode oft he game when creating the final authority board and to have rather a discussion about deviations like in planning poker instead of truncating the highest delegation levels with the minority rule.

Delegation poker is fun to play, yields a common understanding of the responsibilities and makes the new level of freedom transparent for the Scrum teams when turning the organisation upside down during an agile transition. 

With the authority board in place the group has a starting point for implementing and re-adjusting empowerment when needed. And last but not least betting in a group together on the delicate issue of empowerment helps building the interlocking roles of product owner and agile manager.

References

November 15, 2011

Agile Agile Team Structure Design

TOMÁS SARACENO. CLOUD CITIES. 

Hamburger Bahnhof, Berlin, 2011

Coming up with a team structure of more than just one scrum team is a tricky task. One must solve a set of constraints like:


  • how does the structure fit to the product's architecture,  feature areas and business requirements 
  • who likes to work with who in a team
  • what skills are needed in which team 
  • who likes to work on which aspect of the product
  • ...
Technology choices have to be based on available skills and the product design itself is determined by the organizational structure as given by the conway's law. These interdependencies between team and product structure make things even more difficult. Also the level of freedom people have in organizing themselves has an impact on the acceptance of the team structure itself, motivation and agile mindset within the resulting organization. The complexity of creating an agile organisation and impact of how the organization is created on the outcome hampers any top down approach to team building. A single person trying to derive an optimal team structure by analyzing the product and mapping this to team member profiles will not succeed in many cases since the task is simply to complex. And implementing the top down generated org chart and filling it up with some agile live will be hard if not impossible.

Jurgen Appelo's game Meddlers is a useful and lightweight tool to allow groups collaboratively design their own team structure and thus provides a great alternative to the single manager creating the org chart. I use it in my agile team startups to take the whole problem of designing the agile team organization and staffing the teams to the team himself. 


How to use Meddlers in a Team-Startup
Before the group can start designing the team structure the product as well as personal style and individual contribution of team members need to be covered, e.g. in a first part of the workshop or during preparation. When these topics are sufficiently understood by the group I start the team structure design with presenting some constraints for the team structure like:

TOMÁS SARACENO. CLOUD CITIES. 

Hamburger Bahnhof, Berlin, 2011

  • Choose team members according to interest in the main feature area(s) and who wants to work together
  • Scrum guide 2011 (Team must be self-organizing,  cross-functional, and does not contain sub-teams, ...)
  • Development team size (3/6)
  • Required set of skills/capabilities each team must have to turn backlog items into increment
  • Balance of personalities and perspectives in every team - the more diverse the better

TOMÁS SARACENO. CLOUD CITIES. 

Hamburger Bahnhof, Berlin, 2011


After agreeing on the design constraints player teams of 4-6 people and an additional team acting as sounding board for the players are formed. For grouping the teams use the same constraints as for the final team structure. A simple and quick way to do this is to let the group standing in a circle throw a ball from person to person until team is fill up and repeating this until all player teams are staffed. The players get a timebox of 20 minutes to design a team structure and staff the teams using the Meddlers cards. They receive feedback and help by the sounding board who can freely walk around checking their blind spots and help out with any other problems. After the first iteration each team get's a 5 minute timebox for presenting their result to the whole group and collect feedback. From my experience a minimum of an additional timebox of 20 minutes is needed to incorporate the feedback and come up with an improved design, depending on the size maybe more. After the final iteration the design teams get a 5 minute timebox for presenting their result. Then a few minutes should be sufficient for the whole group to vote for the best design. As the last step the design with the best voting - or designs, if it is undecided - are refined and quality checked in an open fishbowl session of 30 minutes. The timebox for the whole collaborative team design takes about 60 - 120 minutes.

Implementing a team structure which is designed using Meddlers is straightforward. It leaves a group energized and motivated to start the new structure since it's owned by the group. I've seen teams just reorganizing their workplaces the next day in the office without any manager involved. I keep the result of the design in the team room to have it ready as starting point and playing ground for continuously growing the agile organization.


Practicalities


Print on A3 200 g paper and cut enough
game sets to prepare startup
Make sure to print the game on A3 format on 200 g/sq.m or thicker paper and cut as many games as needed. Also having some double sided sticky tape and flipchart paper or large carton is useful to assure the results. 


It would be great to have a place for name tags on the role cards but using small Post-it notes do the job too. For the roles it would be nice to have a blank role to be filled in ad hoc, agile manager and CTO/CIO.