Law Firm Operations
Agile Law Firm Workbook
Agile Law Firm Workbook
  • Agile Law Firm Workbook
    • 1. 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
  • Annex
    • 🙏Acknowledgements
    • 📥Contact
Powered by GitBook
On this page
Export as PDF
  1. Agile Law Firm Workbook
  2. 7. Outro

7.1. Recap

You now have everything that you need to start your first Agile working setup.

If you find it difficult to get started, we suggest asking yourself what the most relevant problems that you are experiencing right now are and building a deep understanding of these issues. Kanban on its own can be a useful tool to help with that, since it can likely make things visible that are not working well.

It’s all about figuring out what you want to change and building around that by picking things that you believe can help in your specific situation and then validating that assumption. After all, Agile is all about assessing and adapting. This is also why we suggest establishing how you want to organise your work and processes before looking at tools. Build the solution that works for you first and then find the right tool to scale it. Not the other way around.

Of course, once you’ve worked through this book, there is much more to discover in the realm of Agile working. As further steps we would suggest taking a closer look at Agile topics like estimation or self-managing teams. There are lots of books and communities out there, so it should be easy to find relevant literature or like-minded people (like, for example, at the Liquid Legal Institute) to discuss with. Of course, you can always get in touch with each of us if you have more questions.

Previous7. OutroNext7.2. Story Epilogue

Last updated 14 days ago