際際滷

際際滷Share a Scribd company logo

[Jira Day 2018] Requirements Management Automation with Atlassian Stack

Deviniti
Deviniti

At Jira Day 2018, Tarun Sapra from Ingenico presented their implementation of Spotify Agile model, and explained how Atlassian tools helped them achieve consistent results and automate requirements management. The setup included Jira, Confluence and Marketplace apps like eazyBI, Tempo Timesheets, Portfolio for Jira and Comala Workflows. Watch the whole presentation recording: https://www.youtube.com/watch?v=ZdWDCe8TMGk

1 of 10
Downloaded 17 times
Requirement Management Automation with Atlassian Stack Tarun Sapra, Atlassian Architect at Ingenico, Mar18
Why tools ? Why automate ? ! Requirements located in a centralized location and easily accessible via a set of decentralized well connected Atlassian Apps. ! Leveraging the tools to give structure to the requirements. ! Achieving Traceability by linking requirements to development items, test cases and release plans. ! Advance dashboards which act as information radiators for everyone involved in the product development lifecycle. ! Globally distributed Scrum teams cant function without the right tools. ! Atlassian marketplace has thousands of plugins to support the automation process and plug in the gaps in the default functionality. ! Use of permission schemes helps in implementing ubiquitous security mechanism across various systems.
Spotify Agile Model Scaling Agile @ Spotify - Henrik Kniberg & Anders Ivarsson
Giving structure to requirements Portfolio Tribe Squad
Delivery rhythms Strategy Product stream / High level roadmap Release Release Plan/High-Level Estimates Sprint Sprint Plan/ Estimation/ Story points CI/CD Integration/Release/Builds Initiative Epics/Features Stories
Mapping requirements - recommended structure in JIRA & Confluence One Tribe One JIRA Project One Squad One Scrum Board A Release Roadmap Set of Epics over time A Product Stream / Business Roadmap Set of Initiatives over time A Release Version FixVersion Sprint backlog Sprint backlog Stories Requirements tasks hierarchy Portfolio/JIRA Requirements content hierarchy Confluence
Reporting Essentials Keep it lean: make reporting a dashboard, not an activity! ! Effective dashboards giving an insight to tribe leads about the progress of issues across the full production chain. ! Display the historical velocity of all sprints instead of the just one sprint and the velocity achieved per release cycle. ! Shows evolution of product backlog over a period of time. ! Indicates the features to be released in upcoming release cycle. ! and the ones released in latest release cycle. ! Show the number and the list of defects created and resolved per release cycle. ! Tracks progress of Initiatives across tribes and squads at story level using the ratio of story points completed. ! Tracking progress of epics at tribe level by grouping stories across the epics (applicable for a specific set of epics, typically for a specific customer project) ! Issues removed (de-scoped) from release cycle.
Plugin essentials ! Arsenale dataplane / eazyBI Reporting plugin for creating reports and embedding the reports onto dashboards using gadgets. ! Script Runner Automation of various business processes & enforcing certain project governance regulations for consistency in workflow and reporting across tribes ! Tempo Timesheets Extracting reports about worklogs ! JIRA Portfolio Portfolio level view of things across tribes and squads ! Better excel reporting extracting reports in excel using custom templates ! Gliffy Creating Architecture/Business flow diagrams in confluence ! Comala workflows Approvals and Reviews for created content.
Confluence and JIRA essentials ! Requirements hierarchy split across JIRA IssueTypes Story, Epic and Initiative ! Each type having its workflow and thus definition of done varies across types based on the business requirements. ! Leveraging combination of Scrum & Kanban boards for the feature lifecycle. ! Creating advance dashboards using filters and plugins and sharing with the management. ! Setting up the content hierarchy structure in Confluence. ! Displaying JIRA tickets and charts in Confluence using JIRA macros and charts macros. ! Creation on sprint and release notes in confluence and linking it back to JIRA.
DEMO TIME!

More Related Content

[Jira Day 2018] Requirements Management Automation with Atlassian Stack

  • 1. Requirement Management Automation with Atlassian Stack Tarun Sapra, Atlassian Architect at Ingenico, Mar18
  • 2. Why tools ? Why automate ? ! Requirements located in a centralized location and easily accessible via a set of decentralized well connected Atlassian Apps. ! Leveraging the tools to give structure to the requirements. ! Achieving Traceability by linking requirements to development items, test cases and release plans. ! Advance dashboards which act as information radiators for everyone involved in the product development lifecycle. ! Globally distributed Scrum teams cant function without the right tools. ! Atlassian marketplace has thousands of plugins to support the automation process and plug in the gaps in the default functionality. ! Use of permission schemes helps in implementing ubiquitous security mechanism across various systems.
  • 3. Spotify Agile Model Scaling Agile @ Spotify - Henrik Kniberg & Anders Ivarsson
  • 4. Giving structure to requirements Portfolio Tribe Squad
  • 5. Delivery rhythms Strategy Product stream / High level roadmap Release Release Plan/High-Level Estimates Sprint Sprint Plan/ Estimation/ Story points CI/CD Integration/Release/Builds Initiative Epics/Features Stories
  • 6. Mapping requirements - recommended structure in JIRA & Confluence One Tribe One JIRA Project One Squad One Scrum Board A Release Roadmap Set of Epics over time A Product Stream / Business Roadmap Set of Initiatives over time A Release Version FixVersion Sprint backlog Sprint backlog Stories Requirements tasks hierarchy Portfolio/JIRA Requirements content hierarchy Confluence
  • 7. Reporting Essentials Keep it lean: make reporting a dashboard, not an activity! ! Effective dashboards giving an insight to tribe leads about the progress of issues across the full production chain. ! Display the historical velocity of all sprints instead of the just one sprint and the velocity achieved per release cycle. ! Shows evolution of product backlog over a period of time. ! Indicates the features to be released in upcoming release cycle. ! and the ones released in latest release cycle. ! Show the number and the list of defects created and resolved per release cycle. ! Tracks progress of Initiatives across tribes and squads at story level using the ratio of story points completed. ! Tracking progress of epics at tribe level by grouping stories across the epics (applicable for a specific set of epics, typically for a specific customer project) ! Issues removed (de-scoped) from release cycle.
  • 8. Plugin essentials ! Arsenale dataplane / eazyBI Reporting plugin for creating reports and embedding the reports onto dashboards using gadgets. ! Script Runner Automation of various business processes & enforcing certain project governance regulations for consistency in workflow and reporting across tribes ! Tempo Timesheets Extracting reports about worklogs ! JIRA Portfolio Portfolio level view of things across tribes and squads ! Better excel reporting extracting reports in excel using custom templates ! Gliffy Creating Architecture/Business flow diagrams in confluence ! Comala workflows Approvals and Reviews for created content.
  • 9. Confluence and JIRA essentials ! Requirements hierarchy split across JIRA IssueTypes Story, Epic and Initiative ! Each type having its workflow and thus definition of done varies across types based on the business requirements. ! Leveraging combination of Scrum & Kanban boards for the feature lifecycle. ! Creating advance dashboards using filters and plugins and sharing with the management. ! Setting up the content hierarchy structure in Confluence. ! Displaying JIRA tickets and charts in Confluence using JIRA macros and charts macros. ! Creation on sprint and release notes in confluence and linking it back to JIRA.