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
  • Practice Tip: Cards with Tasks
  • Story
  • Letting go
  • Example
  • Template
Export as PDF
  1. Publications and Articles
  2. Agile Law Firm Workbook
  3. 5. Kanban

5.2. Elements on the Board

Each individual Element is represented by a separate card placed on the Kanban board. The contents of such card can vary depending on the type of Element, but you can also use Kanban irrespective of these more formalised properties. When you put a single Task as a card on the board, the contents of a card can be quite simple. In a simple version, the contents of the cards could be:

  • Title

  • Due Date

  • Description

  • To-do lists

  • Assignee

Practice Tip: Cards with Tasks

When you work with Items and Tasks, you can use a separate card for every Task within the Item or have a card for the Item including the Tasks as a checklist. In any case, you will want separate Tasks if the responsibility to execute them lies between different people. In practice, it will also depend on the software or tool you are using, if Tasks are separate cards on the board.

Story

Letting go

After a brief feeling of elation, having taken up the challenge, our team quickly gets back down to earth as they start writing down their Items on Post-it notes. They find that it’s quite difficult to get the all the required details written down. Alice has left this to Fiona and Gabriel. As Gabriel intensely scribbles away on the cards, Fiona gives an exhausted sigh and decides to get a coffee. On the way to the kitchen, she doubles back and decides to pick up the Agile guide she has recently bought. She takes it to the whiteboard and, instead of writing cards, she goes to read about Kanban and the management of Items again. That turns out to be a good move, as she finds a key tip in there. The cards only need to be fully detailed when the team decides to move them into their “To Do” column, that is the part of the board containing the cards on which the team wants to work on next. The solution is that they just think about the details of what they will address in the next week. They will place the other Elements as cards on the board, but as mere placeholders, letting go of the details. In the end, they decide to take a different colour and use that for Epics and just note the items they already know on the Epic cards that are not relevant yet. That settled, the team writes all cards for the Items they need.

Example

Our team puts a task from Item 1. Meet the client to get the big picture of the case on the Kanban board.

Title: Set up client meeting
Due Date: April 1st, 2024

Description:

A client meeting needs to be set up before April 14, 2024, consisting of the law firm team (partner and associates), the client and relevant people on their side to get the full picture of the case.

To-Do:

• Arrange date/time with client, no later than April 14, 2024.

• Book a meeting room.

• Set reminder to prepare meeting room.

• Get Agenda from attorney/associate.

• Circulate agenda to all participants.

Assignee: Oliver, Assistant

Template

Title: ...
Due Date: ...

Description:

...

To-Do:

• ...

• ...

• ...

• ...

• ...

Assignee: ...

Previous5.1. Kanban BoardNext5.3. The lifecycle of a card

Last updated 4 months ago