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.

Collaboration and Agile - BA World Melbourne 2011


Published on

Published in: Technology, Education
  • Be the first to comment

Collaboration and Agile - BA World Melbourne 2011

  1. 1. We’re Agile Now: So Collaborate or Else!<br />Collaboration and how to do it well in an agile project<br />Jacky Jacob<br />Supervising Consultant and Agile Coach<br />Object Consulting<br />
  2. 2. Today<br />Communication vs Collaboration<br />What collaboration means in an agile team<br />Roadblocks<br />Team collaboration<br /> Slide 2 of 30<br />
  3. 3. “When the revolution comes, machines will talk to machines and people's vocal cords will atrophy"<br />Mystery, Jonathan Kellerman<br /> Slide 3 of 30<br />
  4. 4. Early Collaboration<br /> Slide 4 of 30<br />
  5. 5. Being a collaborator<br />You can go from this<br />To this<br /> Slide 5 of 30<br />
  6. 6. Who does a BA need to collaborate with?<br />Elicit Requirements<br />Analysis and <br />documentation<br />Product Owner<br />Stakeholders<br />Product Owner<br />Dev’s, Testers<br />Architects<br />Scrum Master<br />Project Manager<br />Help to identify<br />the solution<br />Dev’s, Testers, Architects<br />Verify solution against requirements<br />Communicate to team<br />The requirements<br />Dev’s, Testers<br />Product Owner<br />Dev’s, Testers<br />Scrum Master<br /> Slide 6 of 30<br />
  7. 7. The 3 C’s in any agile project<br />Communication <br />conveying information<br />Cooperation<br />working in harmony, side by side<br />Collaboration<br />working together to achieve a goal<br /> Slide 7 of 30<br />
  8. 8. Communication vs Collaboration<br /> Slide 8 of 30<br />
  9. 9. Collaboration<br /><br /> Slide 9 of 30<br />
  10. 10. Collaboration = Trust + Transparency<br />10<br />
  11. 11. Roadblocks to collaboration<br /> Slide 11 of 30<br />11<br />
  12. 12. 12<br />Roadblocks<br />
  13. 13. Roadblocks<br /> Slide 13 of 30<br />
  14. 14. Don't want to or what's in it for me?<br />Distrust or lack of trust<br />Don’t want to share knowledge<br />Don't know how<br />Personalities<br />Lack of time<br /> Slide 14 of 30<br />14<br />Human Roadblocks<br />
  15. 15. Agile Manifesto<br />Individuals and interactions over processes and tools<br />Working software over comprehensive documentation<br />Responding to change over following a plan<br />Customer collaboration over contract negotiation<br />That is, while there is value in the items onthe right, we value the items on the left more<br /> Slide 15 of 30<br />
  16. 16. Key Agile Principles for Collaboration<br />Changing requirements<br />Face-to-face conversation<br />Team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly<br />Best architectures, requirements, and designs emerge from self-organizing teams<br />Work together daily<br />Build projects around motivated individuals<br />Extract from:<br /> Slide 16 of 30<br />
  17. 17. 17<br />Wisdom of the crowdMany Are Smarter Than the Few <br /><ul><li>Diversity of opinion
  18. 18. Each person should have private information even if it's just an eccentric interpretation of the known facts.
  19. 19. Independence
  20. 20. People's opinions aren't determined by the opinions of those around them.
  21. 21. Decentralisation
  22. 22. People are able to specialise and draw on local knowledge.
  23. 23. Aggregation
  24. 24. Some mechanism exists for turning private judgments into a collective decision.</li></li></ul><li>18<br />Collaboration and Agile Analysis<br /><ul><li>“Agile analysis is highly evolutionary and collaborative process where developers and project stakeholders actively work together on a just-in-time (JIT) basis to understand the domain, to identify what needs to be built, to estimate that functionality, to prioritise the functionality, and in the process optionally producing artifacts that are just barely good enough.”
  25. 25. Scott Ambler</li></ul>18<br />
  26. 26. Phases in an Agile Project<br />19<br />Waterfall<br />Definition<br />Build<br />Test<br />Design<br />Agile<br />Initiate<br />Evolve<br />Discover<br />
  27. 27. Opportunities to Collaborate<br />24 hrs<br />Iteration<br />Prioritised Feature List<br />Vision<br />Retrospective<br />Daily Cycle<br /> IterationPlanning<br />ProductIncrement<br />Demonstrate<br />Releasable<br />Product<br />Selected<br />Features<br />20<br />20<br />
  28. 28. Collaboration using Scrum <br />Additional meetings / workshops<br />Product backlog grooming sessions<br />Product owner, tester, developer meetings<br />Tech huddles<br />Ad-hoc discussions<br /> Slide 21 of 30<br />
  29. 29. Agile Collaboration<br />Co-Location<br />Video Conferencing<br />Walls (and lots of them) / Sticky Notes<br />Big Visible Charts (BVC)<br />Be transparent to all<br />22<br />
  30. 30. 23<br />
  31. 31. 24<br />
  32. 32. 25<br />
  33. 33. 26<br />
  34. 34. 27<br />
  35. 35. 28<br />
  36. 36. Team Collaboration<br />Priorities<br />Team success over or in alignment with individual performance<br />Targets<br />Delivering quality outcomes <br />Learning<br />Learning from within and across teams:<br />Honest, constructive feedback<br />Knowledge sharing, not hoarding<br />Explicit team processes<br />Communications<br />Working and workflow<br />All roles are clarified within the team<br />Decision making (self empowered team)<br /> Slide 29 of 30<br />
  37. 37. 30<br />Encouragement and positive feedback<br />
  38. 38. Getting collaboration to work<br />Skill<br />Respect<br /> Slide 31 of 30<br />
  39. 39. What's needed for effective collaboration<br />Everybody needs to understand;<br />WHY should we work together<br />WHAT should we do together<br />WHO should do what<br />HOW should we work together<br />32<br /><br />
  40. 40. Create a Social Contract <br />Team Culture and behaviours<br />Team Agreements <br />33<br />
  41. 41. Teaching Collaboration<br />Change it up a bit and teach <br />collaboration through game playing<br />Lego Game<br />Teaches collaboration and teamwork<br />Non musical Chairs<br />Enforce the importance of self organization, communication, simplicity and trust<br />Collaborative Origami<br />Shows that collaboration leads to faster results and better quality<br />The backlog is in the eye of the beholder<br />Demonstrates the importance of identifying and leveraging different views to better manage a  product backlog<br />Marshmallow Challenge<br />Encourages teams to experience simple but profound lessons in collaboration, innovation and creativity<br />Offing the off-site Customer<br /><br /><br /> Slide 34 of 30<br />
  42. 42. You can promote collaboration<br />Stay positive<br />Ask questions<br />Encourage information sharing / don’t become the bottleneck<br />Drive to consensus<br />Make everything highly visible<br />Take away the blame<br />Respect people's views and opinions (even if you don’t agree with them!).<br /> Slide 35 of 30<br />
  43. 43. Additional Information<br />Team Work Video<br /><br />Teleconference Video<br /><br />Game played – Collaborative Origami<br /><br />Website for agile games<br /><br />Or (Type “agile games” into your search engine)<br />36<br />
  44. 44. Thank You<br /> Slide 37 of 30<br />
  45. 45. References<br /><br /><br /><br /><br /><br /><br /><br /><br />Jean Tabaka, Collaboration Explained, Addison Wesley 2009, <br />Luke Hohmann, Innovation Games, Addison Wesley 2010<br />John P. Kotter, Leading Change, Harvard Business Review Press 1996<br />Kent Beck, Extreme Programming Explained, Addison Wesley 2010<br />M Sliger and S Broderick, The Software Project Managers Bridge to Agility, Addison Wesley 2008<br />Lyssa Adkins, Coaching Agile Teams, Addison Wesley 2010<br />Ken Whitaker, Princiiples of Softare Development Leadership, Cengage Learning 2010<br /><br /> Slide 38 of 30<br />