Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.



Published on

  • Be the first to comment

  • Be the first to like this


  1. 1. Spotlight  PPM  Webinar   Effec5ve  use  of  Scrum  with  Global  Teams   Wednesday,  August  21st  at  10:30  am  PDT   Presented  by:  Marshall  Guillory,  President  and  Principal  Enabler,  Synergy  Agile  
  2. 2. Topics   •  Assump5ons   •  Effec5ve  use  of  Scrum?   •  Communica5on   •  The  Leadership  Vacuum   •  There  is  no  “I”  in  Scrum   •  Process   •  Tools   •  Take  Away  
  3. 3. Assump5ons   •  Time-­‐boxed  to  30  minutes  –  welcome  to   Scrum!   •  Audience  knows  what  agile  Scrum  is?  If  not,   browse  on  over  to  the   Website  and  also  learn  more  about  the  agile   revolu5on  at   •  You  have  read  the  presenter  bio   •  Have  had  coffee  or  your  favorite  morning   wake  up  intake    
  4. 4. Effec5ve  use  of  Scrum?   •  “Scrum  is  a  simple  framework  for  effec5ve  team   collabora5on  on  complex  projects.  –”   •  Please  define  effec5ve  use  of  Scrum   –  It  is  effec5ve  when  it  is  genera5ng  value  for  the  team,   the  project,  and  the  client   –  When  the  teams  efforts  are  not  genera5ng  value,  the   team  is  not  effec5ve   –  Don’t  blame  the  process  and  philosophy   •  Value?  
  5. 5. Credit:  Oblivion  2013   Sally  (actress  Melissa  Leo)  -­‐  “Are  you  an  effec5ve  team?”  
  6. 6. Communica5on   •  Cliché?  Yes.   •  Important?  S5ll  is.  Scrum  is  ineffec5ve  without  it.   •  Not  just  what  we  say…we  heard  you,  but…   –  Was  anything  received,  processed  and  consumed?   •  Cultural  and  Language  Barriers   –  Defeated  with  pa5ence  and  use  of  more  than  one  tool  and   format   –  Frequency,  varia5on   –  Quality  and  quan5ty  
  7. 7. The  Leadership  Vacuum   •  Observa5ons  on  failed  or  marginal  projects:   •  Lack  of  leadership:   – Managers   – Team  /  Technical  leads   – Execu5ves   – Clients   •  Scrum  Master  is  the  coach.  He  is  the  teams   spiritual  guide  and  should  drive  leadership   poten5al  in  stakeholders  
  8. 8. There  is  no  “I”  in  Scrum   Managers  as  Enablers  and   Leaders   •  Agree  to  enable  more   •  Manage  less   •  Lead  more   •  Schedule  less   mee5ngs   •  Understand  your  value  add   •  Champion,  Defend  and   Crush  Nega5vity  for  the   Scrum  Team   Engineers  as  Self-­‐Organized   Team   •  Agree  to  communicate   •  More  ofen   •  More  concise   •  Keep  up  with  tasks   and  documenta5on   •  Understand  your  value  add   •  Be  social,  par5cipate  in  the   process!  
  9. 9. The  Home  Run   People,  processes,  and  tools  (technology)  drive  quality  in  products  and   services.  
  10. 10. Process   •  All  process  must  have   value   •  One  size  does  not  fit  all   •  We  must  be  able  to   measure  the  value   (benefit)  of  any  and  all   process.   •  All  process  must  be   documented,  repeatable,   reliable,  and  consistent.   •  Why?   –  Processes  are  simply,   communica5ons  standards   –  The  team  “language”   –  ins5nct  –  you  know  the   previous  and  next  step  if   you  know  the  process   –  Process  intui5on  -­‐  velocity   •  Scrum  –  as  a  philosophy   rather  than  a  checklist   Process  for  the  sake  of  process,  is  not  progress.  
  11. 11. Tools   •  All  tools  must  have  value   •  One  tool  does  not  fit  all   problems   •  Tools  are  not  always  the   answer   •  No  value  if  not  used!   •  Analogy:  Using  a  hammer   to  drive  a  screw  vs.  a   hammer  to  cut  a  board   •  Binary  usage   •  Why?   –  Efficiency   –  Collabora5on   –  Communica5on   –  System  of  record   •  Document  Management   •  RQM   •  Task  Tracking   •  Video  Conferencing     •  Spotlight  PPM  
  12. 12. Take  Away   •  Focus  on  enabling  leadership  poten5al  to   become  a  real  driving  affect  on  projects   •  Engage  only  the  processes  that  you  need   •  Choose  the  right  tool  for  the  job  
  13. 13. References   •  A  study  in  project  failure   •   •   •  The  Standish  Group  Chaos  Report   •  Contact: