Community resources
Community resources
Community resources
Jira Ways of Working – Showcase & Enablement Sessions
Event Name:
Jira Ways of Working – Showcase & Enablement Sessions
Atlassian Products Featured:
Jira Software, Confluence
🎯 Event Goal
As part of a wider improvement to delivery ways of working within a large "Central Government Department", I hosted a series of internal Jira showcase and enablement sessions. The goal was to help teams understand the new Jira setup, introduce more consistent ways of managing work, and show how better Jira practices can improve transparency, collaboration and programme-level reporting.
📚 Agenda & Format
Rather than running a single large training event, we used a combination of role-based showcases and smaller team sessions:
Context – why we were changing our Jira ways of working
Walkthrough of the new Jira structure and team boards
Practical examples covering Epics, Stories and Tasks
Workflow, status and backlog management guidance
Demonstration of programme reporting and visibility
Open Q&A around real team challenges
Follow-up 1:1 sessions with individual feature teams
I also introduced Jira Walk-in sessions and Lunch & Learn sessions to provide continued support.
🔑 Key Takeaways
Consistency does not mean removing team autonomy. Teams can retain flexibility while adopting a small number of common standards.
Good Jira practices can significantly improve programme reporting without requiring additional manual reporting.
Clear definitions of Epics, Stories, Tasks, statuses and ownership make it easier for teams to understand and collaborate around delivery.
Jira adoption works better when teams understand the reason behind a standard rather than simply being given a new process to follow.
🙌 Engagement Highlights
One of the best discussions was around the balance between autonomy and standardisation.
Teams were using different statuses, labels and ticket structures which, individually, often made sense but collectively made programme reporting difficult. Showing how a small amount of standardisation could improve cross-team visibility without dictating how teams run their day-to-day delivery created a genuine “aha” moment.
The smaller 1:1 sessions were particularly valuable because teams could immediately apply the principles to their own boards rather than discussing Jira in the abstract.
📎 Resources & Materials
I developed and used a mixture of internal guidance and Atlassian best practices, including:
Jira Ways of Working guidance
Epic, Story and Task definitions
Definition of Ready and Definition of Done guidance
Standard workflow and status guidance
Example Jira boards and configurations
Jira governance and reporting guidance
Confluence-based supporting documentation
Atlassian Jira learning and best-practice resources
Some materials contain information specific to the Department and therefore cannot be shared publicly, but the underlying principles are reusable across large, complex, multi-team environments.
📈 Early Signs of Impact
The MVP of the new Jira setup has been completed.
Showcase sessions have been delivered across Product Managers, Product Owners, Delivery Leads, PMO, leadership and other programme roles.
Most feature teams have received dedicated 1:1 support to configure and improve their Jira boards.
Teams are increasingly challenging unnecessary statuses, labels and ticket structures rather than creating additional variations.
Programme data is becoming more consistent, improving the potential for automated and transparent leadership reporting.
Follow-up questions and requests for additional Jira support have increased, helping identify further opportunities for enablement.
✅ What Went Well
Combining broad showcases with team-level support worked particularly well.
The larger sessions helped establish common principles, while smaller sessions allowed us to translate those principles into each team's real-world Jira setup.
Live demonstrations also generated much better engagement than presentation-only training. People could see their own delivery challenges reflected in the examples and immediately discuss how they could improve them.
🔄 What You’d Improve Next Time
I would establish a baseline measures before starting the enablement, such as workflow variation, backlog quality, reporting completeness and Jira hygiene. This would allow us to demonstrate the impact of the sessions quantitatively as adoption develops - while the users are playing with the tool through the session, so that they can see how behaviours impact data and ultimately the reporting. Also, this should help them address their own concerns and reduce their frustration be it for visibility, synchronisation or simply planning, tracking and managing their/their team's work.
📸 Photos & Screenshots
Cannot be provided