ACCU Is XP still alive and kicking


Published on

This is a case study of XP practices at Connextra and then later at Unruly Media (founded by people who worked at Connextra) presented by Rachel Davies at ACCU conference 2013.

Published in: Technology
1 Comment
1 Like
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

ACCU Is XP still alive and kicking

  1. 1. Come  to  this  session    if  you  have  an  interest  in  hearing  about  current  state  of  XP  and  how  its  been  evolving.  This  is  a  case  study  of  XP  prac=ces  at  Connextra  and  then  later  at  Unruly  Media  (founded  by  people  who  worked  at  Connextra).    1  
  2. 2. Extreme  Programming  Explained  -­‐  Kent  Beck  (Addison  Wesley  2000)  hMp://    2  
  3. 3. Prac=ces  from  “XP  Explained”  in  1999  ed  1.  3  
  4. 4. XP  Circles  of  Life  as  described  by  Ron  Jeffries  at  XP2001.  
  5. 5. 5  XP  Explained  2nd  ed.  
  6. 6. Knobs  to  11  6  
  7. 7. Connextra  history  7  
  8. 8. 8  At  Connextra,  wethought  the  template  would  make  a  neat  XPDay  give-­‐away.  We  were  surprised  that  this  format  spread  around  the  world.    
  9. 9. TimMackinnon  was  co-­‐author  of  Endo-­‐tes=ng:  Unit  Tes=ng  with  Mock  Objects  paper  and  developers  at  Connextra  were  first  to  use  them  from  2000  before  Mocking  frameworks  had  been  developed.  9  
  10. 10. Another  less  widely  known  Connextra  prac=ce  was  Lone  Ranger.  A  nominated  developer  who  was  available  on  a  daily  basis  to  handle  customer  support  requests  (nomina=ng  interrup=ble  developer  to  minimise  interrup=ons  to  all  teams).  All  developers  took  turns  to  be  LR.  Ref:  Extreme  Support  by  Rachel  Davies  &  Colville  Wemyss    10  
  11. 11. Gold  Cards  –  every  developer  had  1  day  per  week  to  work  on  research  of  new  ideas  or  improvements.  Ref:  Innova=on  and  Sustainability  with  Gold  Cards.  XPUniverse  2001    11  
  12. 12. Unruly  is  a  video  technology  company  that  works  with  top  brands  and  their  agencies  to  predict  the  emo=onal  impact  of  their  videos  and  get  them  watched,  tracked  and  shared  across  paid,  owned  and  earned  media.    Sarah  “XP  is  integral  to  our  whole  business  ethos  and  company  philosophy.  Its  important  that  all  teams  -­‐  whether  thats  marke=ng,  ops,  design  or  media  -­‐  are  comfortable  with  con=nuous  itera=on  and  happy  to  "embrace  change"  as  the  XP  moMo  goes!”      12  
  13. 13. Some  photo’s  of  team  at  Unruly.  13  
  14. 14. We pair on production code,everyday (except Gold Cards).Often I see people working intriples.
  15. 15. We use traditional index cardswithin team area and electroniccard walls to radiate progress tocustomers across EMEA and USoffices.
  16. 16. Stan on Infra and Mike on UX
  17. 17. We formed a cross-team Boratsquad to move forward ourinfrastructure vision. Developersalready deploy code and maintaininfrastructure but this is about“reducing variance, improving themean”We used a gradient to see who wasinterested to be on this squad.
  18. 18. We did dot-voting to prioritise areasfor our Infrastructure backlog.
  19. 19. Helps break down tensionsbetween teams and is fun duringthe day 
  20. 20. Vikki made this for our larger teamretrospective before we split intosmaller teams.
  21. 21. Distributed team. We try to involveAimy one of our Product Managersin New York. You can see her hereon Google Hangour with her faceplastered with sticky notes andwearing a tiara from (GoogleHangout effect)
  22. 22. Knobs  to  11.  Are  we  s=ll  looking  for  areas  where  can  we  improve?  Yes!  22  
  23. 23. Iteration length was 18 workingdays, seems a long time (comparedto 2 week sprints) but actually werelease code daily, this is aboutagreeing priorities with ourstakeholders. However, 18 daysmakes the day of the meeting moveabout in our stakeholder calendars– we’re trying 15 days (every 3weeks) with 2 teams and otherteam is on 10day cycle.
  24. 24. When  I  joined  the  company  there  was  a  huge  and  growing  backlog  of  wordy  stories  in  TargetProcess.  This  cumula=ve  flow  chart  shows  that  we  were  inves=ng  =me  wri=ng  these  when  they  were  not  gemng  done.  Now  moved  to  a  simpler  tool,  Trello,  which  is  more  like  a  card  wall  and  less  effort  to  maintain.  24  
  25. 25. Were  we  spending  too  much  =me  in  detailed  es=mate  sessions,  talking  about  stories  that  never  got  implemented.  We  have  reduced  whole  team  =me  doing  this  and  can  give  ballpark  es=mate  with  1  or  2  developers.  Whole  team  only  has  detailed  design  discussion  for  stories  that  are  definitely  chosen  for  our  next  itera=on  (discussion  happens  aper  planning).  25  
  26. 26. We  had    established  a  Product  team  to  work  with  stakeholders  to  figure  out  new  stories.  But  they  ended  up  wri=ng  long  stories  that  were  too  big  to  get  implemented.  26  
  27. 27. We  moved  our  Product  Managers  down  to  sit  with  the  team.  27  
  28. 28. We  merged  Product  and  Development  to  create  cross-­‐func=onal  teams.  Developers  involved  in  story  crea=on  and  gives  ballpark  at  same  =me.  Detailed  discussion  with  team  only  happens  for  most  valuable  stories.  28  
  29. 29. Now  stakeholders  talk  directly  to  Developers.  29  
  30. 30. We  created  a  hot  ideas  process  where  Developers  are  the  first  point  of  contact  and  lead  story  discussions.  30  
  31. 31. We  created  a  visual  map  of  our  users  to  make  it  easer  for  people  to  have  conversa=ons  with  them.  31  
  32. 32. Your  ques=ons?  
  33. 33. 33