Agile in distributed teams - London Atlassian User Group
•
1 j'aime•733 vues
Experiences using Atlassian tools with distributed agile teams by Kevin Smith
Recommandé
Recommandé
Contenu connexe
Similaire à Agile in distributed teams - London Atlassian User Group
Similaire à Agile in distributed teams - London Atlassian User Group (20)
Plus de Matthew Cobby
Plus de Matthew Cobby (14)
Dernier
Dernier (20)
Agile in distributed teams - London Atlassian User Group
- 1. JIRA and Confluence for Agile in distributed teams And the many, many pitfalls…. Friday, 4 July 14
- 2. Key points • Information wants to be free • Meeting notes are your friend • JIRA can over-complicate user story management • Make sure external users have training • How to effectively communicate Friday, 4 July 14
- 3. Can’t you just email it to me? No. Friday, 4 July 14
- 4. This guy is your enemy Don’t let him sabotage your project Friday, 4 July 14
- 5. Wallboards save lives But remember some teams work differently… Friday, 4 July 14
- 6. Friday, 4 July 14
- 7. Summary of all tasks Single page view accessible to all teams Friday, 4 July 14
- 8. JIRA or Confluence? Which system should I create my stories in? Friday, 4 July 14
- 9. JIRA can confuse people User stories want to live in Confluence until they’re signed off and ready for development Friday, 4 July 14
- 10. –Supplier Project Manager at the end of Sprint 4 “You know I wasn’t convinced, but this JIRA thing is awesome” Friday, 4 July 14
- 11. Confluence can work better Stories are simpler to edit in confluence and people tend to prefer to update them more here rather than in JIRA Friday, 4 July 14
- 12. Create JIRA issue This is awesome! Works on tables, will save you a heap of time Friday, 4 July 14
- 13. Training is a challenge Make sure dev teams understand the concepts before letting them loose on the system… Friday, 4 July 14
- 14. Before training… How not to manage a burn down chart… Friday, 4 July 14
- 15. Getting better… (apart from the time spent line) Friday, 4 July 14
- 16. Communicating information In a controlled and collaborative manner Friday, 4 July 14
- 17. Daily stand-up • Every day • Same time • Same location • No excuses • No disruptive team members! • Keep it to the point • No whinging • Take it offline Friday, 4 July 14
- 18. Wallboards again Seriously, they’re really important! (and can be used for a Nerf gun scoreboard and sweepstakes…) Friday, 4 July 14
- 19. Governance Painful but necessary, stakeholders from all teams Friday, 4 July 14
- 20. Co-location If you can, do it once a week… …then go to the pub, relationships count. Friday, 4 July 14
- 21. Biggest learnings • The tools do matter, having 3rd parties in a single system helps, a lot! • Relationships can be neglected when teams are separated, co- locate, video-conference. • Page restrictions cause pain - use only for commercially sensitive information • Get people on-board. Some people don’t like JIRA, those people sometimes need a cattle prod… • Sometimes JIRA is overkill, particularly for non-technical teams, use what’s appropriate for the audience Friday, 4 July 14
- 22. Questions? Friday, 4 July 14