Hans Samios' Personal Lean-Agile Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools

Trace:
what_is_the_effect_of_changing_team_members_on_velocity

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
blog:what_is_the_effect_of_changing_team_members_on_velocity [2016/06/15 10:09] – ↷ Page name changed from blog:what_is_the_effective_changing_team_members_on_velocity to blog:what_is_the_effect_of_changing_team_members_on_velocity hpsamioswhat_is_the_effect_of_changing_team_members_on_velocity [2020/06/10 12:55] – ↷ Links adapted because of a move operation hans
Line 1: Line 1:
-====== What Is The Effective Changing Team Members on Velocity? ======+====== What Is The Effect of Changing Team Members on Velocity? ======
  
 When an organization transforms to a Scrum / Agile one of the key things we change is the way we determine who does work. Previously we would have mangers decide which people would do what work. If projects were large we’d build extensive systems to track the allocation of “full time equivalents (FTE)” to projects. In other words we brought people (or in fact parts of people) to work. With Scrum the unit of execution is not an FTE but a team (software = team). With Scrum the idea is that we want a team to work together for a period of time as, when they do this they become more than the sum of their parts and produce more value. To allow this to happen we change the “resourcing” problem so that we bring work to the team instead of forming groups of people around work. When an organization transforms to a Scrum / Agile one of the key things we change is the way we determine who does work. Previously we would have mangers decide which people would do what work. If projects were large we’d build extensive systems to track the allocation of “full time equivalents (FTE)” to projects. In other words we brought people (or in fact parts of people) to work. With Scrum the unit of execution is not an FTE but a team (software = team). With Scrum the idea is that we want a team to work together for a period of time as, when they do this they become more than the sum of their parts and produce more value. To allow this to happen we change the “resourcing” problem so that we bring work to the team instead of forming groups of people around work.
Line 23: Line 23:
 Starting with prediction number 1, we find that our prediction does not pan out. Looking at the chart below we see that the most increase was with low churn was in fact higher than the no churn team, whereas, as expected they both had more increase than the high churn team. Starting with prediction number 1, we find that our prediction does not pan out. Looking at the chart below we see that the most increase was with low churn was in fact higher than the no churn team, whereas, as expected they both had more increase than the high churn team.
  
-{{:blog:effect_of_churn_on_team.png?500 |}}+{{ effect_of_churn_on_team.png?500 |}}
  
 We need to dig a little deeper to understand what is happening here. Interviews with the management involved in these changes revealed that there are differences in what happens based on who is being added or subtracted from the team, that there is a place for judicious change: We need to dig a little deeper to understand what is happening here. Interviews with the management involved in these changes revealed that there are differences in what happens based on who is being added or subtracted from the team, that there is a place for judicious change:
Line 34: Line 34:
 Turning to the second prediction, that if you add or subtract a person from a high churn team, you basically have a similar increase or decrease in velocity going forward (since teams members have not jelled so the total ability of the team is simply the sum of the parts.) This prediction basically pans out. Subtract one team member reduces the velocity for high churn teams, while adding a team member increases the velocity. Turning to the second prediction, that if you add or subtract a person from a high churn team, you basically have a similar increase or decrease in velocity going forward (since teams members have not jelled so the total ability of the team is simply the sum of the parts.) This prediction basically pans out. Subtract one team member reduces the velocity for high churn teams, while adding a team member increases the velocity.
  
-{{:blog:tvi_recovery.png?500 |}}+{{ tvi_recovery.png?500 |}}
  
 Note that I would ignore the results for the “-2” and “2”, “3” as the number of teams that actually went through this level of change are 3 or less in each case (versus more than 20 for the “-1” and “1”) case. Note that I would ignore the results for the “-2” and “2”, “3” as the number of teams that actually went through this level of change are 3 or less in each case (versus more than 20 for the “-1” and “1”) case.
Line 58: Line 58:
   * Wayne Morgan on specific people changes we have seen and the results from those changes.   * Wayne Morgan on specific people changes we have seen and the results from those changes.
  
-{{tag>BlogEntry team FAQ velocity performance}}+====== Want to Know More? ====== 
 + 
 +  * [[:what_kinds_of_problems_do_you_see_when_agile_teams_churn_team_members_a_lot|What Kinds of Problems Do You See When Agile Teams Churn Team Members a Lot?]] 
 +  * [[:how_do_we_reduce_the_effect_of_team_churn_on_our_ability_to_deliver_value|How Do We Reduce the Effect of Team Churn on Our Ability to Deliver Value?]] 
 + 
 + 
 +{{tag>BlogEntry team FAQ velocity performance structure organization}}
  
-~~LINKBACK~~ 
-~~DISCUSSION~~ 
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/what_is_the_effect_of_changing_team_members_on_velocity.txt · Last modified: 2021/06/09 13:36 by hans