Share
The Trouble with Jira - The Architecture Gathering 2019
Agile conferences, blogs, twitter – wherever lean and agile people come together it is easy to stir up a tumult with emotions running high just by mentioning Jira. But why is there always such a strong reaction? Is it the quality of the tool? Not in my experience. The problem lies in the actual adoption in many organizations and – to be fair –similar points could be made about other tools as well. This talk will look into the systemic, sociological and organizational issues that make (some) of us wince each time we hear that our clients use Jira. And it will show how to deal with these issues!
This is not meant to be a Jira bashing session, but a talk that aims to provide actual guidance for all agile initiatives challenged with centrally administered systems. After this talk participants will know (more) about
- A better –and more objective– understanding on why so many people in the lean and agile communities object the usage of Jira
- Some Approaches to succeeding with lean and agile initiatives despite centrally administered ticketing systems like the one mentioned in the title
Michael Mahlberg
Transcript
88 slides
-
Slide # 2019 Michael Mahlberg The trouble with Jira 1
Michael Mahlberg – Oktober 2019 -
Slide # 2019 Michael Mahlberg 3 This talk might not
agree with Jira-haters and challenge some precious misconceptions ADVISORY G E N E R A L N o J i r a B a s h i n g -
Slide # 2019 Michael Mahlberg 4 Quelle: Thomas Epping, persönliche
Kommunikation, 2019 Team Process Company Community -
Slide # 2019 Michael Mahlberg The Specialist Specialist know-how and
rights Centralised administration 5 -
Slide # 2019 Michael Mahlberg 6 True Story… Physical board
March 2017 (5 Teams ~ 40 People) Centrally administered tool 3 Month until this version was available electronically Flow-Efficiency: 1,3% … -
Slide # 2019 Michael Mahlberg 7 The means of production
belong in the hands of the people who actually do the work. (paraphrased of course) -
Slide # 2013 Michael Mahlberg PRINCIPLES BEHIND THE AGILE MANIFESTO
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. - Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. - Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. - Business people and developers must work together daily throughout the project. - Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. - The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. - Working software is the primary measure of progress. - Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. - Continuous attention to technical excellence and good design enhances agility. - Simplicity--the art of maximizing the amount of work not done--is essential. - The best architectures, requirements, and designs emerge from self-organizing teams. - At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. 9 -
Slide # 2013 Michael Mahlberg PRINCIPLES BEHIND THE AGILE MANIFESTO
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. - Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. - Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. - Business people and developers must work together daily throughout the project. - Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. - The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. - Working software is the primary measure of progress. - Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. - Continuous attention to technical excellence and good design enhances agility. - Simplicity--the art of maximizing the amount of work not done--is essential. - The best architectures, requirements, and designs emerge from self-organizing teams. - At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. 10 -
Slide # 2013 Michael Mahlberg PRINCIPLES BEHIND THE AGILE MANIFESTO
11 -At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. -
Slide # 2019 Michael Mahlberg 22 True Story… Physical board
March 2017 (5 Teams ~ 40 People) Centrally administered tool 3 Month until this version was available electronically Flow-Efficiency: 1,3% … -
Slide # 2019 Michael Mahlberg 23 T r o u
b l e R e m e d y Use a physical board for the details Use a higher level of abstraction in the tool Have an administrator on every team Loss of adaptability -
Slide # 2019 Michael Mahlberg 24 Quelle: Thomas Epping, persönliche
Kommunikation, 2019 Process Company Community -
Slide # 2019 Michael Mahlberg Sharing is caring? Processes &
Work Item Types 25 -
Slide # 2013 Michael Mahlberg PRINCIPLES BEHIND THE AGILE MANIFESTO
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. - Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. - Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. - Business people and developers must work together daily throughout the project. - Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. - The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. - Working software is the primary measure of progress. - Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. - Continuous attention to technical excellence and good design enhances agility. - Simplicity--the art of maximizing the amount of work not done--is essential. - The best architectures, requirements, and designs emerge from self-organizing teams. - At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. 26 -
Slide # 2013 Michael Mahlberg PRINCIPLES BEHIND THE AGILE MANIFESTO
-Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. -[…] -The best architectures, requirements, and designs emerge from self-organizing teams. - 27 -
Slide # 2019 Michael Mahlberg 28 40 teams 2 week
iterations 2 changes related to process or work item definition per iteration (fostered by the process improvement meeting at the end of each iteration) 15 Minutes to describe the change 15 Minutes to understand it 15 Minutes to implement it. 40(teams) / 2(weeks) * 2 (changes) => 40 Changes per week 30 hours implementing changes not feasible 3 People in admin team Just some assumptions – real life data might be worse -
Slide # 2019 Michael Mahlberg 29 Why is it not
feasible? - Overhead for information sharing between admins - Overhead for “re-learning” the specifics of the model -
Slide # 2019 Michael Mahlberg 36 Why is it not
feasible? - Overhead for information sharing between admins - Overhead for “re-learning” the specifics of the model - Changes would queue up and admins would become the bottleneck for the teams Team 1 2 3 4 (not to scale) (retrospective) (change) -
Slide # 2019 Michael Mahlberg Enter: Economy of scale 37
This is an Anti-Pattern -
Slide # 2019 Michael Mahlberg Let’s have fewer models And
specialized teams to find the best process-models 38 This is an Anti-Pattern -
Slide # 2019 Michael Mahlberg 39 This is an Anti-Pattern
The actual team (doing the work) The way they work Process-team (observing and optimizing) Admin-team (executing what the process team deems right) The implemented process The gap produced by “chinese whispers” and time passing -
Slide # 2019 Michael Mahlberg 40 T r o u
b l e R e m e d y Loss of autonomy Loss of adaptability Have an administrator on every team Use only very few shared objects In case of Jira: allow “Simplified Workflow” Use a physical board for the details Use a higher level of abstraction in the tool Have an administrator on every team -
Slide # 2019 Michael Mahlberg In the beginning… Once upon
a time, Jira was a bug-tracker… 41 -
Slide # 2019 Michael Mahlberg This applies to almost all
electronic ticket systems 51 -
Slide # 2019 Michael Mahlberg People are actuators? or at
least that’s how the systems treat them as opposed to People define their own process … constantly 52 -
Slide # 2019 Michael Mahlberg 53 Quelle: Thomas Epping, persönliche
Kommunikation, 2019 Company Community -
Slide # 2019 Michael Mahlberg Individuals & interactions Assigning someone
a Jira Ticket over… 54 -
Slide # 2019 Michael Mahlberg 58 T r o u
b l e R e m e d y Loss of autonomy Loss of adaptability Have an administrator on every team Use only very few shared objects In case of Jira: allow “Simplified Workflow” Use a physical board for the details Use a higher level of abstraction in the tool Have an administrator on every team -
Slide # 2019 Michael Mahlberg 59 T r o u
b l e R e m e d y Loss of autonomy Loss of adaptability Have an administrator on every team Use only very few shared objects In case of Jira: allow “Simplified Workflow” Use a physical board for the details Use a higher level of abstraction in the tool Have an administrator on every team Loss of motivation Avoid using the tool a primary means of communication. Use it to capture agreements between people. -
Slide # 2019 Michael Mahlberg Visual Management Boards are used
to drive self-organization by displaying relevant information (Layout et. al. & functionality) 60 -
Slide # 2019 Michael Mahlberg 61 Electronic boards: - …
are endless (it makes no difference whether there are two or twohundred items below the edge of the screen) - … usually don’t support free-hand placement of items and/or lanes - … allow for multiple viewpoints (People see the world differently) (Worst offender: Quickfilter “my tickets only”) - … tend to contain too much information -
Slide # 2019 Michael Mahlberg 63 T r o u
b l e R e m e d y Loss of autonomy Loss of adaptability Have an administrator on every team Use only very few shared objects In case of Jira: allow “Simplified Workflow” Use a physical board for the details Use a higher level of abstraction in the tool Have an administrator on every team Loss of motivation Avoid using the tool a primary means of communication. Use it to capture agreements between people. -
Slide # 2019 Michael Mahlberg 64 T r o u
b l e R e m e d y Loss of autonomy Loss of adaptability Have an administrator on every team Use only very few shared objects In case of Jira: allow “Simplified Workflow” Use a physical board for the details Use a higher level of abstraction in the tool Have an administrator on every team Loss of motivation Avoid using the tool a primary means of communication. Use it to capture agreements between people. Loss of flexibility and visibility Use physical boards and/or be creative (e.g. use multiple displays for swimlanes visualize critical data only, etc.) -
Slide # 2019 Michael Mahlberg 65 Quelle: Thomas Epping, persönliche
Kommunikation, 2019 Company Community -
Slide # 2019 Michael Mahlberg Subverting the Community The tool
subverts the efforts of the community => Kanban Board => Epic 66 -
Slide # 2019 Michael Mahlberg Let’s look at Kanban as
an Example 67 -
Slide # 2019 Michael Mahlberg Let’s look at Kanban as
an Example 68 -
Slide # 2018 Michael Mahlberg Fundamental assumption about Vizualizition 69
The intelligence is in front of the Board —— Simon Kühn Limited WIP Society Köln 2012 -
Slide # 2019 Michael Mahlberg 70 T r o u
b l e R e m e d y Loss of autonomy Loss of adaptability Have an administrator on every team Use only very few shared objects In case of Jira: allow “Simplified Workflow” Use a physical board for the details Use a higher level of abstraction in the tool Have an administrator on every team Loss of motivation Avoid using the tool a primary means of communication. Use it to capture agreements between people. Loss of flexibility and visibility Use physical boards and/or be creative (e.g. use multiple displays for swimlanes visualize critical data only, etc.) Loss of initiative Don’t follow the tool, have communities of practice and external exchanges – a lot! -
Slide # 2019 Michael Mahlberg It’s all in the cards
Jira used as a requirement & documentation tool 71 -
Slide # 2019 Michael Mahlberg 73 As returning visitor of
the site, I want the system to recognize me unmaskingly, so that I actually can order the articles in my basket even weeks after my last visit. As returning visitor of the site, I want the system to recognize me unmaskingly, so that I actually can order the articles in my basket even weeks after my last visit. As returning visitor of the site, I want the system to recognize me unmaskingly, so that I actually can order the articles in my basket even weeks after my last visit. As returning visitor of the site, I want the system to recognize me unmaskingly, so that I actually can order the articles in my basket even weeks after my last visit. As returning visitor of the site, I want the system to recognize me unmaskingly, so that I actually can order the articles in my basket even weeks after my last visit. As returning visitor of the site, I want the system to recognize me unmaskingly, so that I actually can order the articles in my basket even weeks after my last visit. As returning visitor of the site, I want the system to recognize me unmaskingly, so that I actually can order the articles in my basket even weeks after my last visit. As returning visitor of the site, I want the system to recognize me unmaskingly, so that I actually can order the articles in my basket even weeks after my last visit. As returning visitor of the site, I want the system to recognize me unmaskingly, so that I actually can order the articles in my basket even weeks after my last visit. As returning visitor of the site, I want the system to recognize me unmaskingly, so that I actually can order the articles in my basket even weeks after my last visit. -
Slide # 2019 Michael Mahlberg 74 T r o u
b l e R e m e d y Loss of autonomy Loss of adaptability Have an administrator on every team Use only very few shared objects In case of Jira: allow “Simplified Workflow” Use a physical board for the details Use a higher level of abstraction in the tool Have an administrator on every team Loss of motivation Avoid using the tool a primary means of communication. Use it to capture agreements between people. Loss of flexibility and visibility Use physical boards and/or be creative (e.g. use multiple displays for swimlanes visualize critical data only, etc.) Loss of initiative Don’t follow the tool, have communities of practice and external exchanges – a lot! -
Slide # 2019 Michael Mahlberg 75 T r o u
b l e R e m e d y Loss of autonomy Loss of adaptability Have an administrator on every team Use only very few shared objects In case of Jira: allow “Simplified Workflow” Use a physical board for the details Use a higher level of abstraction in the tool Have an administrator on every team Loss of motivation Avoid using the tool a primary means of communication. Use it to capture agreements between people. Loss of flexibility and visibility Use physical boards and/or be creative (e.g. use multiple displays for swimlanes visualize critical data only, etc.) Loss of initiative Don’t follow the tool, have communities of practice and external exchanges – a lot! Loss of knowedge Use other tools for documentation and link to them! includes education, training, permissions, autonomy, etc -
Slide # 2019 Michael Mahlberg Working in a post agile
world is… Local decisions (governed by negotiated policies) Adaptive development processes Teams change process all the time 77 -
Slide # 2019 Michael Mahlberg At regular intervals, the team
reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Quote from the Manifesto for Agile Software Development 78 -
Slide # 2019 Michael Mahlberg Centrally administered workflows don’t agree
with self organized teams 79 -
Slide # 2019 Michael Mahlberg During each Sprint Retrospective, the
[…] Team plans ways to increase product quality by improving work processes […] Quote from the Scrum-Guide 80 -
Slide # 2019 Michael Mahlberg Depending on external “mechanics” subverts
the idea of local process improvements 81 -
Slide # 2019 Michael Mahlberg Agree to pursue improvement through
evolutionary change. Quoting the second principle of change management of the Kanban method 82 -
Slide # 2019 Michael Mahlberg Evolutionary change needs experiments –
hard to do with centralized artifacts 83 -
Slide # 2019 Michael Mahlberg 84 The means of production
belong in the hands of the people who actually do the work. (paraphrased of course) -
Slide # 2019 Michael Mahlberg Let The Tool do what
The Tool does best Use The Tool (e.g. Jira) to capture data, but Use physical boards for communication 85 -
Slide # 2019 Michael Mahlberg 86 T r o u
b l e R e m e d y Loss of autonomy Loss of adaptability Have an administrator on every team Use only very few shared objects In case of Jira: allow “Simplified Workflow” Use a physical board for the details Use a higher level of abstraction in the tool Have an administrator on every team Loss of motivation Avoid using the tool a primary means of communication. Use it to capture agreements between people. Loss of flexibility and visibility Use physical boards and/or be creative (e.g. use multiple displays for swimlanes visualize critical data only, etc.) Loss of initiative Don’t follow the tool, have communities of practice and external exchanges – a lot! Loss of knowedge Use other tools for documentation and link to them! includes education, training, permissions, autonomy, etc -
Slide # 2019 Michael Mahlberg Contact Information 88 If you
have questions, don’t hesitate to contact me via mail at: [email protected] You can also find me on Twitter as MMahlberg I blog on http://agile-aspects.michaelmahlberg.com My homepage is http://www.michaelmahlberg.de