When transforming teams, processes & tools, organisations face a lot of challenges. Daniel talks about how his team has transformed their operating model and migrated from Mingle to Jira; will also share some insights on how Jira helped them support this transformation.

1. DANIEL MOLINARD | DELIVERY LEAD | TABCORP
Continuous Transformation
Embracing the journey

2. Agenda
whoami
Tabcorp Overview
Digital Sydney Team History
Problem Statement
Migrating to JIRA
Key Takeaway / Q&A

3. whoami
Daniel Molinard
• Tabcorp since 2016
• Delivery Lead for Content &
Platform Tribes
• OpenBet 2006 – 2016
• Development Manager
• Tech Lead
• Developer / software engineer
• Ops
• BA
• Project Manager
• Tester
• University
• 

4. Agenda
whoami
Tabcorp
Digital Sydney Team History
Problem Statement
Migrating to JIRA
Key Takeaway / Q&A

5. Tabcorp Overview
ASX Top 50
Started Victoria TAB – 1964
Technology Team > 1K
Offices in Sydney, Brisbane,
Melbourne, London
Members with over 30 years
experience
~200K concurrent users at peak
High transactional volumes
Highly regulated across all states
and territories ( except WA)

6. Agenda
whoami
Tabcorp
Digital Sydney Team Journey
Problem Statement
Migrating to JIRA
Key Takeaway / Q&A

7. Digital Sydney – Team Journey
2013 - 10
members
2014 - 30
members
2016 - 100
members

8. Digital Sydney – Guiding Principles

9. Digital Sydney – Ways of Working

10. Digital Sydney – Ways of Working

11. Digital Sydney – Ways of Working

12. Digital Sydney Team – Tools
Mingle
• Epic / Story Tracking
• Release management
• Defect tracking
• Story mapping
• Delivery Health
Tracking
• ISO9001 compliance
Pivotal Tracker (prior to
2015)
Spreadsheet
• Portfolio View
• Capacity Management
• Budgeting /
Forecasting
Harvest
• Timesheeting
• Forecast / Actuals
Trello
• Product ideas
• Product prioritisation

13. Agenda
whoami
Tabcorp
Digital Sydney Team History
Problem Statement
Migrating to JIRA
Key Takeaway / Q&A

14. Let’s pause and review our relationship with the
broader business… it started like this

15. Then…

16. Eventually there…

17. Agenda
whoami
Tabcorp
Digital Sydney Team History
Problem Statement
Migrating to JIRA
Key Takeaway / Q&A

18. Tools shortlist..
Mingle
• Very simple, too simple?
• Lack of integration, build everything
Trello
• Lack of ability to plan / track work for the teams that build, run
and support the software

19. Why JIRA
• Portfolio view and Business owning backlog
• Wagering Tech already use JIRA
• Easy project dependency management & reporting
• Widely used across the industry – small learning curve
• Wide array of integration / plugins available – no need to
custom build solutions
• Managed tool - SSO, centralised team management

20. Digital Sydney Team – Switching
to JIRA
Mingle - JIRA
• Epic / Story Tracking
• Release management
• Defect tracking
• Story mapping
• Delivery Health Tracking
• ISO9001 compliance
• (new) Github integration
• (new) CI / CD integration
• (new) Slack integration
• (new) Product ideation
• (new) Business prioritisation
• (new) Capacity Management
Spreadsheet
• Portfolio View
• Capacity Management
• Budgeting / Forecasting
Harvest
• Timesheeting
• Forecast / Actuals
Trello
• Product ideation
• Product prioritisation

21. The plan can be simple, just keep planning…

22. Unfortunately there is very little sharing of how to
best model your delivery in JIRA…

23. High Level Portfolio Framework

24. High Level Epic & Stories Framework

25. High Level Release Management

26. Stories Workflow

27. Ticket Types Fields Matrix

28. Tribe’s Portfolio Priorities

29. Tribe’s Portfolio Plan

30. Agenda
whoami
Tabcorp
Digital Sydney Team History
Problem Statement
Migrating to JIRA
Key Takeaway / Q&A

31. Summary
• Understand the problem statement (Why)
• Understand the journey of you team / organisation
• Be clear on what success looks like – not a transition
• Start simple and small
• Get stuck into it / do it quickly
• Embrace change

32. DANIEL MOLINARD | DELIVERY LEAD | TABCORP
Thank you!