Pactical case of Atlassian Tools implementation
Download as PPTX, PDF4 likes1,271 views
This document summarizes a presentation about choosing project management tools. It discusses the client's initial request for help with their tools, an audit of the client's current process, and a proposed solution using Jira and Confluence. The proposed solution includes restructuring the organization and product hierarchies, formalizing workflows for epics, stories, and tasks, and setting up boards and reporting. It acknowledges some challenges with scaling Jira and considers VersionOne as an alternative. In the end, it recommends choosing tools to match the project processes and needs.
Pactical case of Atlassian Tools implementation
- 1. CIKLUM CONSULTING 1 How Cossacks have chosen tools Ciklum Consulting, March 26, 2014
- 2. 2 Purpose of the speech
- 3. AGENDA 3 • Why listen to me? • Initial request • Our approach • Solution • Challenges • Alternative tools
- 4. 4 Why Listen To Me? Yuri Kudin • More than 8 years in IT • Technical background • Last few years working with Distributed Agile teams • Consulting experience • Practical experience with Atlassian products during the last 6 years
- 5. 5 Client Automotive parts web shop • US based • 400+ people in UA entity • 30+ people in development unit
- 7. 7 Approach TOOLS TRAINING AUDIT WORKSHOP TOOLS CONFIGURATION WORKSHOP WITH THE TEAM
- 9. 9 Org and Product Structure CAT Catalogues teams Order team 3rd party Providers ORDER IMPORT-EXPORT 3rd party Providers INTERNAL Internal team
- 10. 10 Project Workflow Formalization Preparation Development Publishing
- 11. 11 Backlog Items Project Epic • Story • Bug • Technical Debt • Investigation • Task • Technical Task Product Project Task
- 12. 12 Theory VS Practice Portfolio Program Team Business epics Arch Epics Features Arch Features Theory Our Case High level epics Technical Epics Stories, Sub-tasks Spikes, Refact. etc Epics Stories, Sub-tasks Tech Debt, Tasks
- 14. 14 Boards Structure Epics Portfolio Management Confluence Team Team Team Link Team Parallel Sprints CAT board ORDERD & INTERNAL board
- 16. 16 Confluence
- 17. 17 Epic workflow
- 18. 18 Epic workflow
- 19. 19 Epics Board Status Mapping
- 20. 20 Epics Board Status Mapping
- 21. 21 Epics Board
- 22. 22 Reporting
- 25. 25 Task Board
- 26. 26 Task board: Priority issue
- 28. 28 JIRA restrictions in scaled agile • Challenges with multi-level hierarchy visualization • No automated update of linked items • Limited amount of columns • Lack out of box reporting for scaled agile
- 30. 30 JIRA vs V1 JIRA VS V1
- 31. 31 JIRA vs V1 Advantages • Suitable for scaled Agile (SAFe support) • Out of the box supports all aspects of Agile Software development • Great relation visualization Disadvantages • Less flexible • Restriction with reporting (incl. V1 Analytics) Advantages • Powerful workflow engine • Great user experience • Flexible reporting • Huge amount of plugins Disadvantages • Lack of flexibility in extending items hierarchy • Lack of out of box preconfigured templates
- 32. 32 Official comparison • https://www.atlassian.com/software/ jira/agile/agile-comparison#!greenhopper-versionone • http://www.versionone.com/vs/versionone-vs-altassian-jira-agile/
- 33. 33 Summary • Often, a wish to change a tool is a wish to change a process • Match tools to the process • Choose the tool according to needs
- 34. www.ciklum.com/consulting 34 Yuri Kudin Technical Consultant Consulting Office (CSC) P +38 044 545 77 45 (ext. 2348) M +38 097 922 76 79 E yuk@ciklum.com W www.ciklum.com/consulting S ykudin We would be glad to answer your questions! Contacts