Abstract image of a woman sitting on books and studying on a laptop

The Trouble with Jira – TAG 2019

Michael Mahlberg, profile picture
Michael Mahlberg

The presentation discusses challenges with using Jira for project management, particularly its impact on team autonomy and adaptability. It advocates for using physical boards and having an administrator on each team to facilitate better communication and process management. The document emphasizes the importance of self-organizing teams and adapting workflows to improve efficiency and effectiveness.

Engineering
1 of 87
Download to read offline
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
Slide #2019 Michael Mahlberg The trouble with Jira 1 Michael Mahlberg – Oktober 2019
Slide #2019 Michael Mahlberg 2 Source:Wikipedia https://en.wikipedia.org/wiki/The_Trouble_with_Harry#/media/File:The_Trouble_with_Harry.jpg JIRA
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:ThomasEpping,persönlicheKommunikation,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 (5Teams ~ 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 #2019 Michael Mahlberg 8
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 12
Slide #2019 Michael Mahlberg 13
Slide #2019 Michael Mahlberg 14
Slide #2019 Michael Mahlberg 15
Slide #2019 Michael Mahlberg 16
Slide #2019 Michael Mahlberg 17
Slide #2019 Michael Mahlberg 18
Slide #2019 Michael Mahlberg Two weeks later 19
Slide #2019 Michael Mahlberg 20
Slide #2019 Michael Mahlberg 21 True Story… Physical board March 2017 (5Teams ~ 40 People) Centrally administered tool 3 Month until this version was available electronically Flow-Efficiency: 1,3% …
Slide #2019 Michael Mahlberg 22 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 23 Quelle:ThomasEpping,persönlicheKommunikation,2019 Process Company Community
Slide #2019 Michael Mahlberg Sharing is caring? Processes & Work ItemTypes 24
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. 25
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. - 26
Slide #2019 Michael Mahlberg 27 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 28 Why is it not feasible? - Overhead for information sharing between admins - Overhead for “re-learning” the specifics of the model
Slide #2019 Michael Mahlberg 29Source: Google Image Search 2019-10-15
Slide #2019 Michael Mahlberg 30
Slide #2019 Michael Mahlberg 31
Slide #2019 Michael Mahlberg 32
Slide #2019 Michael Mahlberg 33
Slide #2019 Michael Mahlberg 34
Slide #2019 Michael Mahlberg 35 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 36 This is an Anti-Pattern
Slide #2019 Michael Mahlberg Let’s have fewer models And specialized teams to find the best process-models 37 This is an Anti-Pattern
Slide #2019 Michael Mahlberg 38 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 39 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… 40
Slide #2019 Michael Mahlberg What is Jira, actually? 41
Slide #2019 Michael Mahlberg 42 Bugzilla
Slide #2019 Michael Mahlberg Jira was an Issue-Tracker, too 43
Slide #2019 Michael Mahlberg Jey-ra vs. Jee-ra [/ˈdʒaɪˈrə/] [/ˈdʒiːrə/] 44
Slide #2019 Michael Mahlberg 45 Source:Wikipedia https://en.wikipedia.org/wiki/Godzilla#/media/File:Godzilla_1954-2014_incarnations.jpg
Slide #2019 Michael Mahlberg Then came GreenHopper About 2007 46
Slide #2019 Michael Mahlberg 47 Source: https://wiki.base22.com/btg/agile-or-no-agile-greenhopper-s-good-for-jira-34963523.html
Slide #2019 Michael Mahlberg Later GreenHopper became JiraAgile 48
Slide #2019 Michael Mahlberg Workflow-Engine with biomechanical actuators 49
Slide #2019 Michael Mahlberg This applies to almost all electronic ticket systems 50
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 51
Slide #2019 Michael Mahlberg 52 Quelle:ThomasEpping,persönlicheKommunikation,2019 Company Community
Slide #2019 Michael Mahlberg Individuals & interactions Assigning someone a JiraTicket over… 53
Slide #2019 Michael Mahlberg 54
Slide #2019 Michael Mahlberg 55
Slide #2019 Michael Mahlberg 56
Slide #2019 Michael Mahlberg 57 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 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 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) 59
Slide #2019 Michael Mahlberg 60 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 61
Slide #2019 Michael Mahlberg 62 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 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. 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 64 Quelle:ThomasEpping,persönlicheKommunikation,2019 Company Community
Slide #2019 Michael Mahlberg Subverting the Community The tool subverts the efforts of the community => Kanban Board => Epic 65
Slide #2019 Michael Mahlberg Let’s look at Kanban as an Example 66
Slide #2019 Michael Mahlberg Let’s look at Kanban as an Example 67
Slide #2018 Michael Mahlberg Fundamental assumption about Vizualizition 68 The intelligence is in front of the Board —— Simon Kühn Limited WIP Society Köln 2012
Slide #2019 Michael Mahlberg 69 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 70
Slide #2019 Michael Mahlberg 71
Slide #2019 Michael Mahlberg 72 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, Iwant the system to recognize meunmaskingly, so that I actually canorder the articles in my basket evenweeks 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 73 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 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! Loss of knowedge Use other tools for documentation and link to them! includes education, training, permissions, autonomy, etc
Slide #2019 Michael Mahlberg Recap Troubles and Remedies 75
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 76
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 77
Slide #2019 Michael Mahlberg Centrally administered workflows don’t agree with self organized teams 78
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 79
Slide #2019 Michael Mahlberg Depending on external “mechanics” subverts the idea of local process improvements 80
Slide #2019 Michael Mahlberg Agree to pursue improvement through evolutionary change. Quoting the second principle of change management of the Kanban method 81
Slide #2019 Michael Mahlberg Evolutionary change needs experiments – hard to do with centralized artifacts 82
Slide #2019 Michael Mahlberg 83 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 84
Slide #2019 Michael Mahlberg 85 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 Questions? 86
Slide #2019 Michael Mahlberg Contact Information 87 If you have questions, don’t hesitate to contact me via mail at: mm@michaelmahlberg.com You can also find me on Twitter as MMahlberg I blog on http://agile-aspects.michaelmahlberg.com My homepage is http://www.michaelmahlberg.de

More Related Content

PDF
Fundamentals of Agile Software Development
Lagos Agile and Craftsmanship Meetup
 
PPTX
Agile Fundamentals
Dennis Stevens
 
PDF
Anglea Johnson - Transforming or confusing the world of work
Paul Ellarby
 
PPTX
Strategies to Reduce Conflict in the Virtual Workplace
Cynthia Clay
 
PDF
152-3 Lean six sigma gets you from coping to solving operational problems
Francisco Pulgar-Vidal, MBA, Lean Six Sigma MBB
 
PDF
Addressing Cultural Anti-patterns in Enterprise transformations
Gautham Pallapa
 
PPTX
Robust Hybrid rather than Agile or Waterfall
Agile Austria Conference
 
PDF
Enterprise Social Networks: Evolving Models for Success
Enterprise Knowledge
 
Fundamentals of Agile Software Development
Lagos Agile and Craftsmanship Meetup
 
Agile Fundamentals
Dennis Stevens
 
Anglea Johnson - Transforming or confusing the world of work
Paul Ellarby
 
Strategies to Reduce Conflict in the Virtual Workplace
Cynthia Clay
 
152-3 Lean six sigma gets you from coping to solving operational problems
Francisco Pulgar-Vidal, MBA, Lean Six Sigma MBB
 
Addressing Cultural Anti-patterns in Enterprise transformations
Gautham Pallapa
 
Robust Hybrid rather than Agile or Waterfall
Agile Austria Conference
 
Enterprise Social Networks: Evolving Models for Success
Enterprise Knowledge
 

What's hot (14)

PDF
Finding Lean in Agile by Adam Parker
Washington DC Scrum User Group
 
PPTX
DCSUG - Finding Lean in Agile
Excella
 
PDF
What is DevOps?
Knowledge Train
 
PPTX
12 agile principles
Steve Ngo
 
PDF
India General Election: A Great Display of Planning, Execution
Project Management Institute (PMI) India
 
PPTX
The 12 Agile Principles
Agile201
 
PPTX
Agile principles & culture
Raymond Baziwane
 
PPTX
Build it Right: Digital Governance for Product Managers
Lisa Welchman
 
PDF
Kanban vs Gantt (webinar)
Association for Project Management
 
PDF
Summit 2013 - Scott Brinker Presentation
Marketo
 
PDF
Basics of agile
SwapnilPrabhavalkar
 
PDF
Breaking Through with Agile Change Management
Enterprise Knowledge
 
PPTX
AAC2018_We're all just doing waterfall really with Iain McKenna
Agile Austria Conference
 
PPTX
Understanding Agile Project Management
Mike Cottmeyer
 
Finding Lean in Agile by Adam Parker
Washington DC Scrum User Group
 
DCSUG - Finding Lean in Agile
Excella
 
What is DevOps?
Knowledge Train
 
12 agile principles
Steve Ngo
 
India General Election: A Great Display of Planning, Execution
Project Management Institute (PMI) India
 
The 12 Agile Principles
Agile201
 
Agile principles & culture
Raymond Baziwane
 
Build it Right: Digital Governance for Product Managers
Lisa Welchman
 
Kanban vs Gantt (webinar)
Association for Project Management
 
Summit 2013 - Scott Brinker Presentation
Marketo
 
Basics of agile
SwapnilPrabhavalkar
 
Breaking Through with Agile Change Management
Enterprise Knowledge
 
AAC2018_We're all just doing waterfall really with Iain McKenna
Agile Austria Conference
 
Understanding Agile Project Management
Mike Cottmeyer
 
Ad

Similar to The Trouble with Jira – TAG 2019 (20)

PDF
Agile,lean, and kanban – friends or foes
Michael Mahlberg
 
PDF
Game Change 100% Agile: Our Journey to a 100% Agile IT Organisation
Marcus Raitner
 
PPTX
PMI CH AMM2023 - Bye Bye Project Manager - SwissQ.pptx
Christoph Wolf
 
PDF
Becoming Agilely Innovative
Steven Palmer
 
PPTX
Agile Leadership 2018 #ALNU18 Game Change 100% Agile
Marcus Raitner
 
PPTX
Maximising likelihood of success: Applying Product Management to AI/ML/DS pr...
Kevin Wong
 
PPTX
Six Sigma
Dashiya Foundation
 
PDF
[Webinar Slides] Planning for Change: How to Map and Model Your Enterprise Pr...
AIIM International
 
DOCX
Presentation by namit
PMI_IREP_TP
 
PDF
Agile Fundamentals for Project Managers.pdf
Borja ARRIZABALAGA URIARTE
 
PPTX
Professional Project Manager Should Be Proficient in Agile
Nitor
 
PPTX
Everybody Wins: How to Collaborate with Engineers and Product Managers
yip_ux
 
PPTX
Digital Event 2023 Survey Report.pptx
PMIUKChapter
 
PDF
Lern- und Beteiligungsformate "42 - New Work Style"
Sebastian Hollmann
 
PDF
An overview of agile practices
Dr. Padmavathi Roy
 
PPTX
Bringing value to the business and for your customer through DevOps
Eficode
 
PDF
How to Go Agile Without Going Crazy – Webinar Slides
Aprimo
 
PPTX
Agile project management - a deep dive 2.2
Mohammad Faiz
 
PDF
Scrum Framework Explained
Nacho Montoya
 
PPTX
Agile Project Management
DigitalCatapultDevelopmentPractices
 
Agile,lean, and kanban – friends or foes
Michael Mahlberg
 
Game Change 100% Agile: Our Journey to a 100% Agile IT Organisation
Marcus Raitner
 
PMI CH AMM2023 - Bye Bye Project Manager - SwissQ.pptx
Christoph Wolf
 
Becoming Agilely Innovative
Steven Palmer
 
Agile Leadership 2018 #ALNU18 Game Change 100% Agile
Marcus Raitner
 
Maximising likelihood of success: Applying Product Management to AI/ML/DS pr...
Kevin Wong
 
Six Sigma
Dashiya Foundation
 
[Webinar Slides] Planning for Change: How to Map and Model Your Enterprise Pr...
AIIM International
 
Presentation by namit
PMI_IREP_TP
 
Agile Fundamentals for Project Managers.pdf
Borja ARRIZABALAGA URIARTE
 
Professional Project Manager Should Be Proficient in Agile
Nitor
 
Everybody Wins: How to Collaborate with Engineers and Product Managers
yip_ux
 
Digital Event 2023 Survey Report.pptx
PMIUKChapter
 
Lern- und Beteiligungsformate "42 - New Work Style"
Sebastian Hollmann
 
An overview of agile practices
Dr. Padmavathi Roy
 
Bringing value to the business and for your customer through DevOps
Eficode
 
How to Go Agile Without Going Crazy – Webinar Slides
Aprimo
 
Agile project management - a deep dive 2.2
Mohammad Faiz
 
Scrum Framework Explained
Nacho Montoya
 
Agile Project Management
DigitalCatapultDevelopmentPractices
 
Ad

More from Michael Mahlberg (20)

PDF
Heavyweight agile Processes? Let's make them leaner!
Michael Mahlberg
 
PDF
Skaliert Arbeiten statt zu skalieren - 2022.pdf
Michael Mahlberg
 
PDF
Agile Tuesday München: Was ist eigentlich aus Lean geworden?
Michael Mahlberg
 
PDF
Process-Tinder – Wenn ich mich nur nach den schönen Bildern entscheide…
Michael Mahlberg
 
PDF
Was ist aus dem L-Wort (in Lean Kanban) geworden?
Michael Mahlberg
 
PDF
Immer Ärger mit Jira - LWIPCGN#118 (2021)
Michael Mahlberg
 
PDF
Continuous Integration - I Don't Think That Word Means What You Think It Means
Michael Mahlberg
 
PDF
Flow – DAS Ziel von Kanban?
Michael Mahlberg
 
PDF
What's in a Story? Drei Ansätze, um mit Anforderungen gemeinsam erfolgreich z...
Michael Mahlberg
 
PDF
Lwipcgn#110 2020-die agilekeuleueberleben
Michael Mahlberg
 
PDF
Michael Mahlberg - Leichtgewichtige Kanban-Metriken auf der LKCE 2018
Michael Mahlberg
 
PDF
Stances of Coaching - OOP2018
Michael Mahlberg
 
PDF
From ceremonies to events
Michael Mahlberg
 
PDF
The Product Owner's Survival Kit - ein Überblick [DE]
Michael Mahlberg
 
PDF
What coaching stances can do for you in Kanban settings...
Michael Mahlberg
 
PDF
A3 thinking - background, process and examples
Michael Mahlberg
 
PDF
Lws cologne leansoftwaredevelopment
Michael Mahlberg
 
PDF
Team models-t4 at2015
Michael Mahlberg
 
PDF
Ökonomie und Architektur als effektives Duo
Michael Mahlberg
 
PDF
Arbeitsorga2014 06-25-welcher hammer-handout
Michael Mahlberg
 
Heavyweight agile Processes? Let's make them leaner!
Michael Mahlberg
 
Skaliert Arbeiten statt zu skalieren - 2022.pdf
Michael Mahlberg
 
Agile Tuesday München: Was ist eigentlich aus Lean geworden?
Michael Mahlberg
 
Process-Tinder – Wenn ich mich nur nach den schönen Bildern entscheide…
Michael Mahlberg
 
Was ist aus dem L-Wort (in Lean Kanban) geworden?
Michael Mahlberg
 
Immer Ärger mit Jira - LWIPCGN#118 (2021)
Michael Mahlberg
 
Continuous Integration - I Don't Think That Word Means What You Think It Means
Michael Mahlberg
 
Flow – DAS Ziel von Kanban?
Michael Mahlberg
 
What's in a Story? Drei Ansätze, um mit Anforderungen gemeinsam erfolgreich z...
Michael Mahlberg
 
Lwipcgn#110 2020-die agilekeuleueberleben
Michael Mahlberg
 
Michael Mahlberg - Leichtgewichtige Kanban-Metriken auf der LKCE 2018
Michael Mahlberg
 
Stances of Coaching - OOP2018
Michael Mahlberg
 
From ceremonies to events
Michael Mahlberg
 
The Product Owner's Survival Kit - ein Überblick [DE]
Michael Mahlberg
 
What coaching stances can do for you in Kanban settings...
Michael Mahlberg
 
A3 thinking - background, process and examples
Michael Mahlberg
 
Lws cologne leansoftwaredevelopment
Michael Mahlberg
 
Team models-t4 at2015
Michael Mahlberg
 
Ökonomie und Architektur als effektives Duo
Michael Mahlberg
 
Arbeitsorga2014 06-25-welcher hammer-handout
Michael Mahlberg
 

Recently uploaded (20)

PPT
INTRODUCTION -Data Warehousing and Mining-M.Tech- VTU.ppt
Subramanyam Natarajan
 
PPTX
Fundamentals of Mechanical Engineering.pptx
MdMowdudAhmed
 
PDF
BIO-INSPIRED ARCHITECTURE FOR PARSIMONIOUS CONVERSATIONAL INTELLIGENCE : THE ...
ijaia
 
PPTX
Current and future trends in Computer Vision.pptx
Subramanyam Natarajan
 
PPTX
ASME PCC-02 TRAINING -DESKTOP-NLE5HNP.pptx
laxmikantvjawale
 
PPTX
Graph Data Structures with Types, Traversals, Connectivity, and Real-Life App...
usham61
 
PDF
distributed database system" (DDBS) is often used to refer to both the distri...
Hemlathadhevi Annadhurai
 
PPTX
Sorting and Hashing in Data Structures with Algorithms, Techniques, Implement...
usham61
 
PPTX
AUTOMOTIVE ENGINE MANAGEMENT (MECHATRONICS).pptx
joanaabban6
 
PDF
Artificial Superintelligence (ASI) Alliance Vision Paper.pdf
SonaliPatil325517
 
PDF
UNIT no 1 INTRODUCTION TO DBMS NOTES.pdf
pawarbhaktiit
 
PPTX
Software Engineering and software moduleing
deepikame6
 
PDF
A SYSTEMATIC REVIEW OF APPLICATIONS IN FRAUD DETECTION
IJNSA Journal
 
PDF
III.4.1.2_The_Space_Environment.p pdffdf
sittiporn2
 
PDF
August 2025 - Top 10 Read Articles in Network Security & Its Applications
IJNSA Journal
 
PDF
Improvement effect of pyrolyzed agro-food biochar on the properties of.pdf
LasFernandaJuchem
 
PPTX
Chemical Technological Processes, Feasibility Study and Chemical Process Indu...
Raihan87
 
PPTX
introduction to high performance computing
JuanDavid747466
 
PDF
Soil Improvement Techniques Note - Rabbi
rahmatideal000
 
PPTX
Feature types and data preprocessing steps
deepalishinkar1
 
INTRODUCTION -Data Warehousing and Mining-M.Tech- VTU.ppt
Subramanyam Natarajan
 
Fundamentals of Mechanical Engineering.pptx
MdMowdudAhmed
 
BIO-INSPIRED ARCHITECTURE FOR PARSIMONIOUS CONVERSATIONAL INTELLIGENCE : THE ...
ijaia
 
Current and future trends in Computer Vision.pptx
Subramanyam Natarajan
 
ASME PCC-02 TRAINING -DESKTOP-NLE5HNP.pptx
laxmikantvjawale
 
Graph Data Structures with Types, Traversals, Connectivity, and Real-Life App...
usham61
 
distributed database system" (DDBS) is often used to refer to both the distri...
Hemlathadhevi Annadhurai
 
Sorting and Hashing in Data Structures with Algorithms, Techniques, Implement...
usham61
 
AUTOMOTIVE ENGINE MANAGEMENT (MECHATRONICS).pptx
joanaabban6
 
Artificial Superintelligence (ASI) Alliance Vision Paper.pdf
SonaliPatil325517
 
UNIT no 1 INTRODUCTION TO DBMS NOTES.pdf
pawarbhaktiit
 
Software Engineering and software moduleing
deepikame6
 
A SYSTEMATIC REVIEW OF APPLICATIONS IN FRAUD DETECTION
IJNSA Journal
 
III.4.1.2_The_Space_Environment.p pdffdf
sittiporn2
 
August 2025 - Top 10 Read Articles in Network Security & Its Applications
IJNSA Journal
 
Improvement effect of pyrolyzed agro-food biochar on the properties of.pdf
LasFernandaJuchem
 
Chemical Technological Processes, Feasibility Study and Chemical Process Indu...
Raihan87
 
introduction to high performance computing
JuanDavid747466
 
Soil Improvement Techniques Note - Rabbi
rahmatideal000
 
Feature types and data preprocessing steps
deepalishinkar1
 

The Trouble with Jira – TAG 2019

  • 1. Slide #2019 Michael Mahlberg The trouble with Jira 1 Michael Mahlberg – Oktober 2019
  • 2. Slide #2019 Michael Mahlberg 2 Source:Wikipedia https://en.wikipedia.org/wiki/The_Trouble_with_Harry#/media/File:The_Trouble_with_Harry.jpg JIRA
  • 3. 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
  • 4. Slide #2019 Michael Mahlberg 4 Quelle:ThomasEpping,persönlicheKommunikation,2019 Team Process Company Community
  • 5. Slide #2019 Michael Mahlberg The Specialist Specialist know-how and rights Centralised administration 5
  • 6. Slide #2019 Michael Mahlberg 6 True Story… Physical board March 2017 (5Teams ~ 40 People) Centrally administered tool 3 Month until this version was available electronically Flow-Efficiency: 1,3% …
  • 7. Slide #2019 Michael Mahlberg 7 The means of production belong in the hands of the people who actually do the work. (paraphrased of course)
  • 8. Slide #2019 Michael Mahlberg 8
  • 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. 9
  • 10. 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
  • 11. 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.
  • 12. Slide #2019 Michael Mahlberg 12
  • 13. Slide #2019 Michael Mahlberg 13
  • 14. Slide #2019 Michael Mahlberg 14
  • 15. Slide #2019 Michael Mahlberg 15
  • 16. Slide #2019 Michael Mahlberg 16
  • 17. Slide #2019 Michael Mahlberg 17
  • 18. Slide #2019 Michael Mahlberg 18
  • 19. Slide #2019 Michael Mahlberg Two weeks later 19
  • 20. Slide #2019 Michael Mahlberg 20
  • 21. Slide #2019 Michael Mahlberg 21 True Story… Physical board March 2017 (5Teams ~ 40 People) Centrally administered tool 3 Month until this version was available electronically Flow-Efficiency: 1,3% …
  • 22. Slide #2019 Michael Mahlberg 22 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
  • 23. Slide #2019 Michael Mahlberg 23 Quelle:ThomasEpping,persönlicheKommunikation,2019 Process Company Community
  • 24. Slide #2019 Michael Mahlberg Sharing is caring? Processes & Work ItemTypes 24
  • 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. 25
  • 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. - 26
  • 27. Slide #2019 Michael Mahlberg 27 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
  • 28. Slide #2019 Michael Mahlberg 28 Why is it not feasible? - Overhead for information sharing between admins - Overhead for “re-learning” the specifics of the model
  • 29. Slide #2019 Michael Mahlberg 29Source: Google Image Search 2019-10-15
  • 30. Slide #2019 Michael Mahlberg 30
  • 31. Slide #2019 Michael Mahlberg 31
  • 32. Slide #2019 Michael Mahlberg 32
  • 33. Slide #2019 Michael Mahlberg 33
  • 34. Slide #2019 Michael Mahlberg 34
  • 35. Slide #2019 Michael Mahlberg 35 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)
  • 36. Slide #2019 Michael Mahlberg Enter: Economy of scale 36 This is an Anti-Pattern
  • 37. Slide #2019 Michael Mahlberg Let’s have fewer models And specialized teams to find the best process-models 37 This is an Anti-Pattern
  • 38. Slide #2019 Michael Mahlberg 38 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
  • 39. Slide #2019 Michael Mahlberg 39 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
  • 40. Slide #2019 Michael Mahlberg In the beginning… Once upon a time, Jira was a bug-tracker… 40
  • 41. Slide #2019 Michael Mahlberg What is Jira, actually? 41
  • 42. Slide #2019 Michael Mahlberg 42 Bugzilla
  • 43. Slide #2019 Michael Mahlberg Jira was an Issue-Tracker, too 43
  • 44. Slide #2019 Michael Mahlberg Jey-ra vs. Jee-ra [/ˈdʒaɪˈrə/] [/ˈdʒiːrə/] 44
  • 45. Slide #2019 Michael Mahlberg 45 Source:Wikipedia https://en.wikipedia.org/wiki/Godzilla#/media/File:Godzilla_1954-2014_incarnations.jpg
  • 46. Slide #2019 Michael Mahlberg Then came GreenHopper About 2007 46
  • 47. Slide #2019 Michael Mahlberg 47 Source: https://wiki.base22.com/btg/agile-or-no-agile-greenhopper-s-good-for-jira-34963523.html
  • 48. Slide #2019 Michael Mahlberg Later GreenHopper became JiraAgile 48
  • 49. Slide #2019 Michael Mahlberg Workflow-Engine with biomechanical actuators 49
  • 50. Slide #2019 Michael Mahlberg This applies to almost all electronic ticket systems 50
  • 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 51
  • 52. Slide #2019 Michael Mahlberg 52 Quelle:ThomasEpping,persönlicheKommunikation,2019 Company Community
  • 53. Slide #2019 Michael Mahlberg Individuals & interactions Assigning someone a JiraTicket over… 53
  • 54. Slide #2019 Michael Mahlberg 54
  • 55. Slide #2019 Michael Mahlberg 55
  • 56. Slide #2019 Michael Mahlberg 56
  • 57. Slide #2019 Michael Mahlberg 57 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
  • 58. 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 Loss of motivation Avoid using the tool a primary means of communication. Use it to capture
 agreements between people.
  • 59. Slide #2019 Michael Mahlberg Visual Management Boards are used to drive self-organization by displaying relevant information (Layout et. al. & functionality) 59
  • 60. Slide #2019 Michael Mahlberg 60 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
  • 61. Slide #2019 Michael Mahlberg 61
  • 62. Slide #2019 Michael Mahlberg 62 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.
  • 63. 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. Loss of flexibility and visibility Use physical boards and/or be creative (e.g. use multiple displays for swimlanes visualize critical data only, etc.)
  • 64. Slide #2019 Michael Mahlberg 64 Quelle:ThomasEpping,persönlicheKommunikation,2019 Company Community
  • 65. Slide #2019 Michael Mahlberg Subverting the Community The tool subverts the efforts of the community => Kanban Board => Epic 65
  • 66. Slide #2019 Michael Mahlberg Let’s look at Kanban as an Example 66
  • 67. Slide #2019 Michael Mahlberg Let’s look at Kanban as an Example 67
  • 68. Slide #2018 Michael Mahlberg Fundamental assumption about Vizualizition 68 The intelligence is in front of the Board —— Simon Kühn Limited WIP Society Köln 2012
  • 69. Slide #2019 Michael Mahlberg 69 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!
  • 70. Slide #2019 Michael Mahlberg It’s all in the cards Jira used as a requirement & documentation tool 70
  • 71. Slide #2019 Michael Mahlberg 71
  • 72. Slide #2019 Michael Mahlberg 72 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, Iwant the system to recognize meunmaskingly, so that I actually canorder the articles in my basket evenweeks 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.
  • 73. Slide #2019 Michael Mahlberg 73 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!
  • 74. 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! Loss of knowedge Use other tools for documentation and link to them! includes education, training, permissions, autonomy, etc
  • 75. Slide #2019 Michael Mahlberg Recap Troubles and Remedies 75
  • 76. 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 76
  • 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 77
  • 78. Slide #2019 Michael Mahlberg Centrally administered workflows don’t agree with self organized teams 78
  • 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 79
  • 80. Slide #2019 Michael Mahlberg Depending on external “mechanics” subverts the idea of local process improvements 80
  • 81. Slide #2019 Michael Mahlberg Agree to pursue improvement through evolutionary change. Quoting the second principle of change management of the Kanban method 81
  • 82. Slide #2019 Michael Mahlberg Evolutionary change needs experiments – hard to do with centralized artifacts 82
  • 83. Slide #2019 Michael Mahlberg 83 The means of production belong in the hands of the people who actually do the work. (paraphrased of course)
  • 84. 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 84
  • 85. Slide #2019 Michael Mahlberg 85 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
  • 86. Slide #2019 Michael Mahlberg Questions? 86
  • 87. Slide #2019 Michael Mahlberg Contact Information 87 If you have questions, don’t hesitate to contact me via mail at: mm@michaelmahlberg.com You can also find me on Twitter as MMahlberg I blog on http://agile-aspects.michaelmahlberg.com My homepage is http://www.michaelmahlberg.de