Using JIRA and Confluence in distributed Agile teams
Download as PPTX, PDF2 likes1,362 views
This document discusses using JIRA and Confluence for agile project management in distributed teams. It provides tips such as using meeting notes and wallboards to communicate effectively across teams. It also warns that JIRA can overcomplicate user story management for some users and teams, and recommends training people on the concepts before using the systems. The document advocates co-locating teams periodically and using video conferencing to maintain relationships when distributed. It concludes that the right tools are important for collaboration across distributed teams and stakeholders.
Using JIRA and Confluence in distributed Agile teams
- 1. JIRA and Confluence for Agile in distributed teams And the many, many pitfalls….
- 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
- 3. Can’t you just email it to me? No.
- 4. This guy is your enemy Don’t let him sabotage your project
- 5. Wallboards save lives But remember some teams work differently…
- 7. Summary of all tasks Single page view accessible to all teams
- 8. JIRA or Confluence? Which system should I create my stories in?
- 9. JIRA can confuse people User stories want to live in Confluence until they’re signed off and ready for development
- 10. –Supplier Project Manager at the end of Sprint 4 “You know I wasn’t convinced, but this JIRA thing is awesome”
- 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
- 12. Create JIRA issue This is awesome! Works on tables, will save you a heap of time
- 13. Training is a challenge Make sure dev teams understand the concepts before letting them loose on the system…
- 14. Before training… How not to manage a burn down chart…
- 15. Getting better… (apart from the time spent line)
- 16. Communicating information In a controlled and collaborative manner
- 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
- 18. Wallboards again Seriously, they’re really important! (and can be used for a Nerf gun scoreboard and sweepstakes…)
- 19. Governance Painful but necessary, stakeholders from all teams
- 20. Co-location If you can, do it once a week… …then go to the pub, relationships count.
- 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
- 22. Questions?