A rant, with evidence, on why electronic tools in general, and JIRA in particular, are anti-Agile. Participants will use the Agile Manifesto to evaluate the electronic tools they are currently familiar with. JIRA is used as a case study.

NOTE: Scrum asks us to have courage. The Agile Manifesto asks us to value individuals and interactions over processes and tools. I hope the organizing committee will consider this proposal despite the risk that it might offend some tool vendors. If we can't speak freely about our experiences with tools, we will fail as a community.

 
13 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  1. The problem: JIRA is taking over.
  2. The theory: Agile-supportive vs. enterprise-ready.
  3. The practice: evaluate your tool.
  4. The future: an ideal electronic Agile tool.

NOTE: At the end of the workshop I will provide a link to downloadable electronic copies of the presentation and worksheets so that you can re-use them.

Learning Outcome

Participants will learn to:

  • evaluate candidate electronic tools for their Agile teams and organization, and
  • explain to others why JIRA is a bad choice of electronic Agile tool.

Target Audience

managers, project managers, agile coaches, leaders, procurement people, and tool vendors

Prerequisite

Have some hands-on experience working in an Agile team.

schedule Submitted 3 months ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Declan Whelan
    keyboard_arrow_down

    Declan Whelan - Technical Debt is a Systemic Problem - Not a Personal Failing

    Declan Whelan
    Declan Whelan
    Agile Coach
    Leanintuit
    schedule 2 months ago
    Sold Out!
    60 Mins
    Talk
    Intermediate

    You often hear technical debt described as a personal failing. Why didn't you code with greater rigor? By creating technical debt, how could you have made life harder on people working in the code? More often than not, technical debt is the result of bigger, systemic problems.
    Chances are, you're not a bad person. You didn't want this to happen. It's the system, not you, that's chiefly responsible.
    In this talk, we will present some of the conclusions from the Agile Alliance's technical debt working group, which has looked into the systemic causes and consequences of technical debt. While marginal amounts of technical debt will always accrue, that does not explain why substantial technical debt is a widespread phenomenon. The organization in which software development teams work is the much bigger culprit. Many systemic causes, such as deadline pressures, under-investment in skills, and even the unwillingness to measure technical debt, conspire to create a growing burden on software professionals, who would otherwise choose not to create this problem if given the opportunity.
    Just as technical debt has systemic causes, the real cost of technical debt lies at the system level. The increasing drag on software innovation has effects not just on individual and team productivity, but on the software value stream, the portfolio, and the organization as a whole. Sometimes, the cost is obvious, such as the valuation of a start-up company's code; other times, the consequences are far more subtle and insidious.
    During this session, we will use the language and methods of systems theory to better come to grips with the causes and consequences of technical debt. Don't worry if systems thinking is unfamiliar — we will cover the basics during the talk. We will also do an exercise in which you will create a simple systems model of your own challenges with technical debt, and discuss how this model should help you shape a plan of action for dealing with technical debt.
    Ultimately, the goal of this session is to give you the tools to better deal with technical debt. Rather than blaming individual developers, you will be able to show the systemic sources of technical debt, and assess the relative value of addressing each of them. Rather than depending on technical measures to convey the costs of technical debt, we will help you to put the costs of technical debt in stark business terms.

  • Liked Arthur Maltson
    keyboard_arrow_down

    Arthur Maltson / Roderick Randolph - Deep Work: A New Working Model for DevOps Teams

    40 Mins
    Talk
    Beginner

    You come into the office and before you’ve had your morning coffee, someone’s at your desk looking for help with an issue. You spend the day trying to focus on that new feature you’re building for customers, it’s going to make their lives so much easier, but you find that you’re answering questions and firefighting all day. The day ends and you wonder “what did I even do today?”. In our roles on technical teams, we live an interrupt driven life, but how do we make progress on that new feature or author that new tool or investigate that new OSS project? It’s not hopeless!

    This session will introduce the concept of Deep Work and a new way to structure your team to optimize for Deep Work, while at the same time meeting your customers’ needs. The examples will focus on DevOps teams but the lessons are applicable to any team experiencing high levels of interruption. At the end of the talk you will have learnt from our experience implementing the new team structure on DevOps teams in two different organizations, ways to promote the concept, how to visualize people’s availability, and how to find success in an interrupt driven world.

  • Liked Sue Johnston
    keyboard_arrow_down

    Sue Johnston - It's Not About The Tools: Facilitating Effective Meetings Across Distance

    40 Mins
    Talk
    Intermediate

    A face-to-face conversation is the most efficient and effective method of conveying information to and within a development team. So states the sixth principle of the Agile Manifesto.

    Reality comes with a big "however." Work-at-home, outsourcing and inter-company partnerships mean that, more and more, we find ourselves n meetings where other participants are not in the same room. They may be around the corner or around the world. Some organizations invest in powerful tools to make this arrangement work well - or, sometimes, not so well. Others make do with audio only. Are we fooling ourselves when we call these events "meetings?" Maybe. Yet they're part of our world, so why not make the most of them?

    In this lively session, you'll examine a proven pattern for facilitation, discover ways to overcome the challenges of virtual meetings and learn techniques that encourage meaningful participation. Most of these require more focus and ingenuity than expense.

    Sue will share some of the techniques she learned as a teleworking pioneer in the '90s and a trainer of coaches, via distance, since 2003. Join us to explore ways you can bring your meetings with remote participants to life and respect everyone's time - including your own.

  • Liked Sue Johnston
    keyboard_arrow_down

    Sue Johnston - Do Your Product Owners Speak A Foreign Language? Techniques for creating shared understanding

    60 Mins
    Talk
    Intermediate

    Effective interactions, between product owners and designers and team members who develop and make those products real, are key to team, product and organizational success. It's reflected in the first value of the Agile Manifesto.

    Still, one of the chief complaints, from both the product side and the dev side, is poor communication. The list of irritants includes: lack of clarity, lack of understanding, lack of time, lack of access, too many meetings, too much jargon, too many badly written user stories and too many people involved.

    Communication isn''t the only obstacle, but it’s a big one - and it can be overcome with no cost or organizational disruption.

    Regardless of the role we play on the team, part of everyone’s job is to create shared understanding. In this session, Marilyn, an experienced product owner and product manager, and Sue, a communication specialist and coach, will share their research about communication gaps in the product-development relationship and approaches that can close the gap.
    Join them to explore tips and ideas to improve communication flow and help teams move from concept to cash.

    NOTE TO TAC TEAM
    Because we are doing some original research on this topic, I would like to include a co-presenter, Marilyn Powers, PEng, who, at the time of posting, is not yet on confengine. Info about her is available at https://www.linkedin.com/in/marilynpowers

    Here is more biographical info about Marilyn:
    Marilyn has more than 10 years experience bringing products and services to market as a Product Manager. As a licensed professional engineer, she has experience working in a variety of fields, from manufacturing to operations to simulation to SAAS software. Currently, Marilyn is a Product Manager at D2L, a leading Ed-tech company, where she works closely with Product Owners, Dev teams, Designers, Senior Leaders and many other stakeholders to deliver quality software tools to educational institutions and corporations who value learning and development. Her expertise is creating shared understanding between diverse groups, be it external customer advisory groups or internal stakeholders.

    Previous presentations or workshops
    Marilyn has presented at a variety of conferences over the past 20 years, the career highlight of which was a live demo on the main stage keynote at the D2L Fusion 2016 conference. Other conference presentations included Online Learning Conference ( New Orleans, LA 2017), Fusion (2015, 2016), Learning Impact Leadership Institute (San Antonio, TX 2016), Industrial Engineering Student Conference (Kitchener, 2016), ModSim World Canada (Montreal, 2010), Montreal Neurological Institute Day (Montreal, 2009), McGill University invited speaker on Haptics (Montreal, 2006). Prior to these presentations, Marilyn was an Instructor of Engineering at Mount Royal University in Calgary, AB.

  • 40 Mins
    Talk
    Intermediate

    Although self-organizing teams are crucial to carrying out a successful Agile transformation, organizations that implement Agile at scale invariably realize that the introduction of such teams forces the organization to re-engineer numerous aspects of its operating philosophy. In particular, various management layers are often removed. The individuals in these layers are routinely re-purposed or laid off.

    This talk highlights the approaches I used as an Agilist in various organizations to help people in different roles on their journey of transitioning into the world of Agile. Specifically, the talk will focus on 5 key roles: Project Managers, Product Managers, BA Managers, Development Managers, and QA Managers. It will provide insight into how managers can effectively transition to some of the new Agile roles, or redefine their existing role to effectively fit in an Agile world.

    The emphasis in this talk is on pragmatic strategies for managers that are struggling to find their place in this new Agile world. Armed with these strategies, participants will be able to effectively adapt to the Agile transformation, as well as discover potential new career paths for themselves and for the individuals reporting to them.

  • Liked Chris Murman
    keyboard_arrow_down

    Chris Murman - Things Are Broken: A Case Study In Moving Tooooooooo Fast

    Chris Murman
    Chris Murman
    Sr. Agile Consultant
    Solutions IQ
    schedule 4 months ago
    Sold Out!
    60 Mins
    Talk
    Intermediate

    Speed.

    It's been a driver in our industry before it was even an industry. The more Agile becomes more mainstream, the more we think it's part of the package. Books are out promising that certain frameworks can deliver twice as much in half the time. And yet, teams still struggle delivering what's expected of them.

    Once I started asking people of all levels of leadership what they thought speed would give them, it allowed me to develop some experiments around those expectations.

    Please join me for a case study where we discuss the need for speed, the origins of that desire, and the ways it manifests itself into deliverables. My desire is for the audience to take away some powerful learning into their places of work. Only by understanding the expectations around speed can we reset them into an environment built around trust and support for motivated individuals.

  • Liked Scott Ambler
    keyboard_arrow_down

    Scott Ambler - The Executive’s Guide to Disciplined Agile: Business Agility for Established Enterprises

    60 Mins
    Talk
    Intermediate

    An agile enterprise increases value through effective execution and delivery in a timely and reactive manner. Such organizations do this by streamlining the flow of information, ideas, decision making, and work throughout the overall business process all the while improving the quality of the process and business outcomes.   This talk describes, step-by-step, how to evolve from today’s vision of agile software development to a truly disciplined agile enterprise. It briefly examines the state of mainstream agile software development and argues for the need for a more disciplined approach to agile delivery that provides a solid foundation from which to scale. We then explore what it means to scale disciplined agile strategies tactically at the project/product level. We then work through what it means to strategically scale across your IT organization as a whole and discover what a Disciplined DevOps strategy looks like in practice. Your Disciplined Agile IT strategy, along with a lean business strategy, are key enablers of a full-fledged disciplined agile enterprise. The talk ends with advice for how to make this challenging organizational transition.

  • Liked Gillian Lee
    keyboard_arrow_down

    Gillian Lee - Minutes to Pin It: How to Get Your Whole Team Agreeing

    90 Mins
    Workshop
    Intermediate

    What if your team could share new ideas and make unanimous decisions in minutes?

    Agile teams need to create and agree on many things such as a definition of done, a sprint plan, and what changes they’ll try in the next sprint based on the most recent retrospective.

    How often have you participated in a meetings where few decisions were made? Or where the the loudest person in the room made most of the suggestions and dominated your team’s decision making?

    In this interactive workshop, we will practice coming up with new ideas using everybody’s suggestions and making decisions that the whole team agrees on.

    Learn and practice techniques such as Fist-of-Five, Decider Protocol and Resolution Protocol and Shared Visioning with Lego.

    Make group decisions faster, more aligned with the whole team, and more likely to result in follow-through.

  • Liked Ellen Grove
    keyboard_arrow_down

    Ellen Grove - Asking Over Telling: Using Humble Inquiry to Build Great Teams

    90 Mins
    Workshop
    Intermediate

    More asking, less telling. As an agile leader, adopt the approach of humble enquiry to build relationships, increase trust and collaboration, and deal with the challenges of organizational transformations.

    "Humble enquiry is the fine art of drawing someone out, of asking questions to which you do not already know the answer, of building a relationship based on curiosity and interest in the other person." - Edgar H. Schein

    Working in an agile way asks us to rethink how we relate to each other as we tackle complex problems and challenge the traditional structures of our organizations. Humble enquiry - the art of asking instead of telling - is a critical skill for agilists who seek to improve collaboration and address difficult problems head on. Inspired by Edgar H. Schein's book 'Humble Enquiry, this workshop will teach you the fundamentals of how to do more asking and less telling. Through mini-lectures and interactive exercises, we'll discuss the different types of questioning, consider the forces around and within us that inhibit our ability to ask instead of tell, and examine how this powerful technique can improve collaboration within agile teams as well as help to address some of the challenges of agile transformations.

  • Liked Charles Maddox
    keyboard_arrow_down

    Charles Maddox - Success Patterns with Scaling Lean-Agile

    Charles Maddox
    Charles Maddox
    Principal
    The i4 Group
    schedule 3 months ago
    Sold Out!
    40 Mins
    Talk
    Intermediate

    From actual field experience helping organizations with adopting Lean-Agile at scale, I have observed some patterns of success and anti-patterns that I would like to share. These patterns have to do with how Leadership and the Lean-Agile Center of excellence contribute successfully or unsuccessfully for success at scaling. We discuss how they both need to exhibit some fundamental areas of leadership that are referenced directly from the book The Leadership Challenge, by Kouzes and Posner. In the session, we will discuss the areas of leadership referenced in the book and how they come to life successfully and sometimes unsuccessfully in the organization. The examples that are given the session in tandem with the book can be used as a clear guide on scaling success in the large enterprise.

  • Liked Fawzy Manaa
    keyboard_arrow_down

    Fawzy Manaa - How to Lose Dev and Alienate Ops

    Fawzy Manaa
    Fawzy Manaa
    Senior Consultant
    Deloitte
    schedule 3 months ago
    Sold Out!
    40 Mins
    Talk
    Beginner

    As many organizations have adopted agile development and are starting to undertake a DevOps transformation to complete the lifecycle, it is not always easy to keep traditionally alienated back office practitioners engaged. In fact, many organizations go about engaging developers, testers, operators, ... in a way that does not align with the spirit of DevOps. Many enterprise DevOps transformations fail because of this very reason, this session will inform the audience of what it takes to create a strong and sustainable movement within an IT organization in today's world where people who perform different functions that are seemingly at odds can come together in the spirit of improving how work is done and delivered.

    The speaker will approach the topic from an anti-patterns perspective, highlighting the symptoms of transformation failure from structural, procedural, and strategic angles and discussing alternative approaches to enable DevOps transformation success.

  • Liked toddcharron
    keyboard_arrow_down

    toddcharron - Change My View: Moral Foundations Theory and You

    60 Mins
    Talk
    Advanced

    Anyone who doesn't agree with me is wrong and not just wrong, but morally repugnant and evil.

    What do you think? Is it really likely that everyone that disagrees with you is somehow a monster? Or perhaps it's something else...

    Over the last few years we've seen a lot of viewpoint polarization. But why does this happen? And what does this tell us about our approaches to Agile?

    In this session we'll look at Moral Foundations Theory and how what we value and hold dear can influence our views on an issue.

    We'll also play a game developed at the Agile Games conference based on this framework that will challenge you to take yourself out of your normal comfort zone and see the world from another perspective.

  • Liked toddcharron
    keyboard_arrow_down

    toddcharron - I'd Buy That For A Dollar

    60 Mins
    Talk
    Beginner

    What happens if we build it and they don’t come?

    Building features no one cares about is not only bad because the feature isn’t getting used, but is also a wasted opportunity that could have been used to build something truly valuable for your customers.

    But how would we know?

    In many companies, features get prioritized by the HiPPO principle (Highest Paid Person’s Opinion). As it turns out, this is often not the most effective way to prioritize your backlog.

    But if not this, then what?

    In this workshop we explore what value is, how to talk about it, and how we might measure the value we have achieved.

  • Liked Johanne Boyd
    keyboard_arrow_down

    Johanne Boyd / Carlo Rosales - Why can't the business be agile too? How ADP is incorporating business Agile practices to keep up with technology

    40 Mins
    Talk
    Beginner

    Does your business struggle to catch up and understand the technical deliverables from your Sprint Reviews? Is there unnecessary re-work and scope creep because requirements are not properly described by the business? ADP has sought to address these issues by incorporating business Agile practices to keep up with technology. The result? Clearer requirements, strong engagement during Sprint Reviews and a collaborative solution with business readiness aligning with technical deliverables. Join our session to find out more!!

  • Liked Steve Zhang
    keyboard_arrow_down

    Steve Zhang - The Joy Of Functional Programming

    Steve Zhang
    Steve Zhang
    Development Practice Coach
    Scotiabank
    schedule 3 months ago
    Sold Out!
    60 Mins
    Talk
    Intermediate

    The popularity of Functional Programming is booming! Are you still wondering what all of the fuss is about? Come to this session and find out! This is an introduction to the power of functional programming. It covers functional programming's basic concepts, and shows you how functional programming will make software simple, elegant, easy to test, and lead to cleaner code. I will share my experiences learning, so you can avoid some of the pitfalls. So if you enjoy coding, love clean code, then you should start learning Functional Programming right now.

  • Liked Dave Dame
    keyboard_arrow_down

    Dave Dame / Aaron Sampson, PMI-ACP, ITILv3, SMC - Design Thinking for Organizational Change

    40 Mins
    Talk
    Beginner

    We all know how people use design thinking to create better products and deliver delightful experiences to our users. However, design thinking can be an excellent tool to use for organizational change. In the case of organizational change, our product is the change that we are trying to drive, and our customers are those people who are impacted (internally and externally) and have to live with that change. In the same way that design thinking puts the user front-and-centre for products, it can be used to put people in the organization front-and-centre. In this talk we will discuss how design thinking works and, as a case study, how we have applied it at Scotiabank to help drive adoption of the Bank’s NPS customer insights into building solutions that serve our customers. In that program, previous internal processes were ineffective in pushing relevant data to delivery teams at the right time. Using a Lean or Agile approach would have provided some benefit, but taking a design thinking approach uncovered an array of useful insights to make the whole process more purposeful. Learn from this example to explore how you might incorporate design thinking to drive greater effectiveness and relevance for your team’s body of work.

  • Liked James Gifford
    keyboard_arrow_down

    James Gifford - Descaling the Enterprise Instead of Scaling Agility

    90 Mins
    Workshop
    Intermediate

    In spite of all of the nuanced discussions, debates and frequent diatribes, scaling agile is about one thing: getting large groups of teams to deliver value in an organized fashion while maintaining empathy, rapport, trust, safety, and ownership across the enterprise. During this session, we will explore the case study of the Value Steam Container, looking at organization design, challenges and success. Focusing in on topics ranging from

    • Organization designs used by WL Gore, The Dunbar number

    • Delivery Triads - Product, Delivery, Technical Excellence

    • Venture capital style funding

    • Focusing on business value

    The second half of the session is a workshop focused on creating a Value Stream Container and resource based on team funding 

  • Liked James Gifford
    keyboard_arrow_down

    James Gifford - 5 Metrics to Create Safety and High Performing Teams

    60 Mins
    Talk
    Intermediate

    Description:

    I see that a lot of organizations use metrics in inappropriate ways to measure teams. At the heart of these metrics, nine times out of ten, are velocity and story points. These metrics lead to a lot of mistrust, fear, and bad technical practices. This talk will focus on shifting the focus to diagnostic metrics.

     Before shifting focus to diagnostic metrics, we need to understand what inappropriate metrics are. When questioning teams about why their velocity was lower from one sprint to another, teams are more likely to inflate their estimates to avoid questions in the future. This is one of my scenarios. We will explore this case and my other top-ten based on the 165 teams I have interacted with. Focusing on one metric does not provide a balanced view of the team.

    For balance, I promote five metrics. The combination of metrics balances each other. These five metrics are lead time, quality, happiness, agile maturity, and business value. Focusing on these five metric areas can be used as a diagnostic tool to help teams grow and support coaching. During the session, we will use my Excel-based tool and visual model to simulate this balance.

    When you push shorter lead times (how fast) on a team with a lower agile maturity, the first thing to change is quality, followed by happiness and then the delivery of value. Conversely, if a team focuses on TDD, the first thing to change is quality, followed by agile maturity, reduction in lead time, and increased delivery of value.  

    Teaching teams to harness data in a positive way will help them to flourish.

  • Liked John Le Drew
    keyboard_arrow_down

    John Le Drew - Swearing, Nudity and Other Vulnerable Positions

    John Le Drew
    John Le Drew
    Owner
    Wise Noodles
    schedule 5 months ago
    Sold Out!
    60 Mins
    Talk
    Beginner

    Over 3 months John recorded over 75 hours of interviews and spoke to some of the most respected people in the industry to produce an audio documentary that attempts to answer the question “What is safety? And why is it important anyway?”

    This highly interactive talk will present the findings and guide and challenge you through a journey to understanding safety. Including short interactive sessions and role play exercises to cover the following topics:

    • What is safety?
    • What are the elements that make a team effective?
    • Is psychological safety the foundation to team performance?
    • What can we all do to help foster psychological safety in our teams?
    • What is the relationship between safety, stress and engagement?
    • What is the profound impact of a lack of safety and engagement on society?

    This talk has grown as John created the new podcast The Agile Path. The first season on this podcast is about safety in teams. John has interviewed world renowned specialists in the field; Christopher Avery, David Marquet, Jerry Weinberg, Esther Derby, Johanna Rothman, Woody Zuill and many more in over 75 hours of audio. This has been a fascinating deep dive learning experience for John and he hopes to explore these insights with the audience.

    Here is a short preview video I made for the session:

  • Liked thomasjeffrey
    keyboard_arrow_down

    thomasjeffrey - Scaling Agile without the scaling framework

    thomasjeffrey
    thomasjeffrey
    President
    Agile By Design
    schedule 3 months ago
    Sold Out!
    60 Mins
    Talk
    Advanced

    Increasingly Agile adoption has focused on how to operate larger enterprises with agility, and run larger and larger initiatives, at scale.

    In many cases, organizations have turned to explicit agile scaling frameworks to address their needs to coordinate increasingly larger efforts to deliver value in a way of that does not sacrifice feedback and self organization . Often these frameworks attempt to address the complexity that comes with large scale by adding extra process and procedure. Prescriptive advice is prescribed in the form of additional roles, stages, gates, and methods. This approach to scaling bears more than a little similarity to the heavy weight methods of the past, but in this case merging agile terminology with much of the same framework bloat and bureaucracy we have seen in the past.

    As a a result adoptees struggle to understand how to fit these frameworks to their context, and seasoned coaches struggle to wrestle out the good bits.

    During this session I will discuss a different approach to scaling agile, one that places an emphasis on both mindset and practice. I'll pay particular attention to the topic of leadership, organizational design, and the role management has to play in designing a system of work that allows larger efforts to work with an agile mindset without being forced into a one size fits all process framework.

    A key part of the discussion will be to showcase how core agile methods and techniques can be extended and expanded to successfully manage coordinated agile deployments that range from hundreds to thousands of FTEs. I'll present these techniques by using real examples of agile deployments I have been a part of during my work with ScotiaBank's agile journey.

    Key Scaling Practices covered will include:
    - The design components required to structure your organization based on demand
    - How to continuously de-scale your organization
    - "Get Out Of the Boardroom" style governance and leadership
    - Operational cadences and Impediment Escalation Flow
    - Managing the flow of value at the Business Technology Asset level
    - Moving the conversation from stories to domains
    - Streamlining finance and budgeting to align to the agile mindset

    I hope to illustrate ways that both management and knowledge workers can select techniques that allow them to scale agile as needed to support ever larger initiatives without succumbing to a one size fits all framework that does not adapt constant change.