O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Scrum: Physical or Virtual

3.649 visualizações

Publicada em

Why do some development teams favour physical story cards and a physical wall over digital? What are the advantages and disadvantages of using physical over digital? When should you use which and how can you combine them? These are difficult questions to answer and often they are the first questions that a team has to deal with when implementing an agile methodology. This session is an experience report rooted in the academic literature. It will aim to answer the questions above using use case examples from the author’s own experience. It will also incorporate the latest academic research into the field specifically using research from Human Computer Interaction in which Agile teams have been analysed to explain the benefits of physical and digital artefacts.

  • DOWNLOAD FULL BOOKS, INTO AVAILABLE FORMAT ......................................................................................................................... ......................................................................................................................... 1.DOWNLOAD FULL. PDF EBOOK here { https://tinyurl.com/y6a5rkg5 } ......................................................................................................................... 1.DOWNLOAD FULL. EPUB Ebook here { https://tinyurl.com/y6a5rkg5 } ......................................................................................................................... 1.DOWNLOAD FULL. doc Ebook here { https://tinyurl.com/y6a5rkg5 } ......................................................................................................................... 1.DOWNLOAD FULL. PDF EBOOK here { https://tinyurl.com/y6a5rkg5 } ......................................................................................................................... 1.DOWNLOAD FULL. EPUB Ebook here { https://tinyurl.com/y6a5rkg5 } ......................................................................................................................... 1.DOWNLOAD FULL. doc Ebook here { https://tinyurl.com/y6a5rkg5 } ......................................................................................................................... ......................................................................................................................... ......................................................................................................................... .............. Browse by Genre Available eBooks ......................................................................................................................... Art, Biography, Business, Chick Lit, Children's, Christian, Classics, Comics, Contemporary, Cookbooks, Crime, Ebooks, Fantasy, Fiction, Graphic Novels, Historical Fiction, History, Horror, Humor And Comedy, Manga, Memoir, Music, Mystery, Non Fiction, Paranormal, Philosophy, Poetry, Psychology, Religion, Romance, Science, Science Fiction, Self Help, Suspense, Spirituality, Sports, Thriller, Travel, Young Adult,
       Responder 
    Tem certeza que deseja  Sim  Não
    Insira sua mensagem aqui

Scrum: Physical or Virtual

  1. 1. Scrum: Physical or virtualwalls?Paula de Matos
  2. 2. What is this talk about? versus2
  3. 3. About mePaula de MatosGroup Coordinator and UserExperience Analyst at the EBIPrevious incarnations:• Java Technical Lead• Java Developer• Broadcast Engineer• Electronic Engineer
  4. 4. About the EuropeanBioinformatics Institute • Based on the Wellcome Trust Genome Campus near Cambridge, UK • Non-profit organisation • Close to 500 employees • Aims to provide comprehensive biological data to scientists
  5. 5. My work We like a physical cards and walls wall Team B (4 people) Team A (6 people) We like software tools to manage our process Team C (4 people)5
  6. 6. How I became an Agile fan? Picture attribution, Toby Bradbury (Flickr) – Creative Commons License6
  7. 7. Our Scrum-like process Tasks7
  8. 8. What is this talk based on? • My own experience • Survey: 23 respondents • Scientific publications Picture attribution, Flickr, The Bees8
  9. 9. Unscientific survey: 23 respondents • Open ended questions • Aim to get as broad a view as possible • 65 % of respondents had experience with physical and software tools Picture attribution, Flickr, The Bees9
  10. 10. Respondents agile experience < 3 years 3-10 years > 10 years 13% 44% 43% Picture attribution, Flickr, The Bees10
  11. 11. The academic literature • Sharp et al. (2006). The Role of Story Cards and the Wall in XP teams: a distributed cognition perspective. • Sharp et al. (2008). Collaboration and co- ordination in mature eXtreme programming teams. • Whittaker et al. (1999) Board meetings: the impact of scheduling medium on long term group coordination in software development. Picture attribution, Flickr, The Bees11
  12. 12. The academic literature • Methods: mainly observation and ethnography • Distributed Cognition Analysis: • Physical theme • Physical artefacts • Information flow Picture attribution, Flickr, The Bees12
  13. 13. What do I mean by user story and taskboard?13
  14. 14. What do I mean by user story? Picture attribution, Flickr, J Beau14
  15. 15. How are user stories stored?15 Picture attribution, Flickr, Natalia Osiatynska
  16. 16. Picture attribution, Flickr,Mircea Turcan16 29/09/201
  17. 17. Picture attribution, Flickr, Drew Stephens17
  18. 18. 18 Photo attribution: Roger Greenhalgh (Flickr) – under the Creative Commons license
  19. 19. 19
  20. 20. What does the “taskboard” look like?20
  21. 21. 21
  22. 22. 22 Photo attribution: Levent Ali (Flickr)– Creative Commons license
  23. 23. What are the advantages of physical walls?23
  24. 24. Visual24 Photo attribution: C. Fraser (Flickr) – Creative Commons license
  25. 25. Coordination of resources25
  26. 26. 26 Photo attribution: Logan Ingalls (Flickr)– Creative Commons license
  27. 27. It’s easy to update the board27 Photo attribution: Ha! Designs (Flickr) – Creative Commons license
  28. 28. Sense of achievement28 29/09/201 Photo attribution: Welsh government (Flickr) – Creative Commons license
  29. 29. Encourages personal communication between members29 29/09/201 Photo attribution: David Cosand (Flickr) – Creative Commons license
  30. 30. Encourages personal communication between members and managers30 29/09/201 Photo attribution: David Cosand (Flickr) – Creative Commons license
  31. 31. Holding a card engenders feelings of task ownership and responsibility31 Photo attribution: Victor1558(Flickr) – Creative Commons license
  32. 32. Encourages reflection32 29/09/201 Photo attribution: Mike Baid (Flickr) – Creative Commons license
  33. 33. Size limit of cards promotes collaboration33 Photo attribution: Roger Mateo Poquet (Flickr) – Creative Commons license
  34. 34. What are the drawbacks of using physical cards?34
  35. 35. Ghost cards35 Photo attribution: Mosieur J (Flickr) – Creative Commons license
  36. 36. No burndown charts or tie into project management software36 Photo attribution: Jeff Covey (Flickr) – Creative Commons license
  37. 37. Hours, points or estimates need to be tallied manually37 Photo attribution: Yum9me (Flickr) – Creative Commons license
  38. 38. Geographical location38
  39. 39. Readability39 Photo attribution: Jim Barter (Flickr) – under the Creative Commons license
  40. 40. Missing in action40 Photo attribution: Brenderous (Flickr) – Creative Commons license
  41. 41. Archiving41 Photo attribution: Damien Oz (Flickr) – Creative Commons license
  42. 42. Space constraints • Title • Estimate • Description • Stack trace • Bug tracker info • Additional comments • Etc….42
  43. 43. No tie into bug trackers and existing documentation43 Photo attribution: Ivan Walsh (Flickr) – Creative Commons license
  44. 44. Unwieldy for large teams44 Photo attribution: avlxyz (Flickr) – Creative Commons license
  45. 45. Advantages of software solutions to manage your tasks and wall45
  46. 46. Geographical location • Team members and management • Meeting rooms46
  47. 47. Automatic features – burndown charts, velocity47 29/09/201
  48. 48. Information rich story cards48
  49. 49. Access archived sprints49 29/09/201
  50. 50. Tie into existing software systems50 Photo attribution: Paolo Valdemarin (Flickr) – Creative Commons license
  51. 51. Disadvantages of software solutions to manage your tasks and wall51
  52. 52. Can become microtasking hell Task 1 Task 1.1 Task 1.2 Task Task Task 1.1.1 1.1.2 1.2.152
  53. 53. Keeping it upto date is difficult53 Photo attribution: Yon Garin (Flickr) – Creative Commons license
  54. 54. Visibility is lost54 Photo attribution: AV-1 (Flickr) – Creative Commons license
  55. 55. Cards are not distinctive enough55
  56. 56. Computers are full of distractions56
  57. 57. Case study: The best of both worlds57
  58. 58. We maintained the backlog using an agile software tool58
  59. 59. User stories were exported to Excel59
  60. 60. Cards were generated using an Excel visual basic script60
  61. 61. Cards printed and subtasks were assigned using post-it notes Check Implement Test cases mockups design users61
  62. 62. Cards and subtasks were placed on a mobile board62
  63. 63. At the end of sprint: post-its were chucked out and new stories printed63
  64. 64. Tips on maintaining physical walls64
  65. 65. Use effective stationery65 Photo attribution: Ivan Di Carlo (Flickr) – Creative Commons license
  66. 66. Place your wall in a prominent position66
  67. 67. Use a transportable board if you need your wall to be mobile67
  68. 68. Treat your cards with the respect they deserve68
  69. 69. Tips on choosing software solutions69
  70. 70. Compile a checklist of what you want the software to do70 Photo attribution: Mistersnappy (Flickr) – Creative Commons license
  71. 71. Consider your existing software infrastructure71
  72. 72. Ease of use72 Photo attribution: Ha! Designs (Flickr) – Creative Commons license
  73. 73. Consider how you will replicate the tactile nature of the taskboard Check Implement Test cases mockups design users73
  74. 74. In summary74
  75. 75. 1st Conclusion Choose a solution that suits the team, organisation, culture and environment.75 Photo attribution: Jace Cooke (Flickr) – Creative Commons license
  76. 76. 2nd Conclusion Trial and error.76 Photo attribution: Everyones idle (Flickr) – Creative Commons license
  77. 77. 3rd Conclusion Don’t underestimate the sensory nature of physical walls… think carefully about how that can be replicated in a software only solution.77 Photo attribution: Nikki Duggan (Flickr) – Creative Commons license
  78. 78. Thanks • Cheminformatics and Metabolism team members • Survey respondents • The authors of the academic literature cited78
  79. 79. Contact me Email: pmatos@ebi.ac.uk LinkedIn: Paula de Matos Twitter: @Paula_deMatos79

×