Law Firm Operations
  • Law Firm Operations
  • Law Firm Operations North Star
  • Publications and Articles
    • Agile Law Firm Workbook
    • FAQs Remote Legal Teams
    • Remote Legal Teams - Getting Started and Making it Work
    • GitHub - Legal Text Analytics
    • Agile Law Firm Workbook
      • Introduction 1.1. What this workbook can show you
        • 1.2. When does it make sense to go agile?
          • 1.3. Structure of the workbook
            • 1.4. Who is this workbook for?
              • 1.5. How to use this workbook
                • 1.6. The story
      • 2. People 2.1. Culture
        • 2.2. Roles and Accountabilities
          • 2.2.1. Introduction to Accountabilities
            • 2.2.2. Let’s start with the WHAT
              • 2.2.3. And what about the HOW?
                • 2.2.4. Specifics for the legal context
                  • 2.2.5. How to get started?
          • 2.3. Transparency & Communication
          • 2.4 Stakeholders
        • 3. Processes
          • 3.1. The agile approach: Iterating in sprints
          • 3.2. Responsibilities
      • 4. Elements
        • 4.1. Goal
        • 4.2. Epic
        • 4.3. Items
        • 4.4. Tasks
        • 4.5. User stories
        • 4.6. Acceptance Criteria
        • 4.7. Definition of ready
        • 4.8. Definition of done
        • 4.9. Bringing it together
      • 5. Kanban
        • 5.1. Kanban Board
        • 5.2. Elements on the Board
        • 5.3. The lifecycle of a card
        • 5.4. Complex Boards
          • 5.4.1. Properties and Filters
          • 5.4.2. Swim lanes
        • 5.5. Further Tips
      • 6. Meetings
        • 6.1. Daily Meetings
        • 6.2. Planning
        • 6.3. Reviews
        • 6.4. Retrospectives
        • 6.5. A Sprint Meeting setup for a law firm
      • 7. Outro 7.1. Recap
        • 7.2. Story Epilogue
        • 7.3. Authors
        • 7.4. Contributors
        • 7.5. Index
        • 7.6. Templates and further information
  • Roundtables and Exchange
    • Session 1: What problems do law firms typically face and how can they be met?
    • Session 2: Working Roundtable
    • Session 3: Identifying and Implementing AI Tools For Legal Practices
  • Annex
    • 🙏Acknowledgements
    • 📥Contact
Powered by GitBook
On this page
  • Story
  • Breaking down complexity
Export as PDF
  1. Publications and Articles
  2. Agile Law Firm Workbook
  3. 5. Kanban
  4. 5.4. Complex Boards

5.4.2. Swim lanes

Previous5.4.1. Properties and FiltersNext5.5. Further Tips

Last updated 4 months ago

As an alternative to filtering based on properties, cards can be grouped in rows called “swim lanes” due to their visual appearance. These can reflect team members, projects, topics, or categories of Elements, for example. The advantage compared to filtering is that swim lanes allow for a visual overview. They are equally useful where you cannot use filters, like on a physical Kanban board, or want to break up the board by topic, you might want to use swim lanes: they can represent people, projects, or categories of Elements.

Story

Breaking down complexity

Fiona and Gabriel meet in the kitchen by chance, both having an acute need for caffeine. Their Agile efforts take some additional concentration on top of their work, but they’re both clear they would not want to miss it. But besides that, there’s something else they notice; they have never included Oliver in their discussions, except that they’ve initially used his office and then once given him a Task and card but without much explanation. Somehow that does not feel right, as he’s a valued member of the team. They briefly think about how they could address it and decide to be very frank: they have not thought about this earlier and rather bring him in later than not at all. They’ll suggest having a joint lunch during which they’ll explain their journey and findings so far and will include him in their further Agile endeavours.

But there’s something else their first experiments with the Kanban board have shown them. It quickly gets hard to keep an overview in the “To Do”, “In Progress” and “Wait” columns. They’ll need to figure out a better way—maybe one of the books will give a hint. But first, they want to apologize to Oliver for not having involved him.

As they enter his office, they find his desk empty and decide to come back later but to their surprise, leaving the room, they notice what they have overlooked on their way in: Oliver was standing quietly at the Kanban board, which was temporarily placed at a side in the open space in front of his office. They quickly approach him and note that it’s a perfect coincidence as they wanted to discuss their Agile process with him. After telling their story, Oliver accepts their apology and comments that he is interested to get started. Without much thought, Fiona mentions that she really wants to address the clutter on the board and will dive into the books. Pragmatic as he is, Oliver suggests just adding lines across the columns in which the cards are assigned to people. Not knowing about the swim lanes concept, he has nevertheless described it. Agile is, in fact, a quite pragmatic approach to breaking down complexity.