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
  • Of witnesses and other stakeholders
  • Example
  • Template
Export as PDF
  1. Publications and Articles
  2. Agile Law Firm Workbook
  3. 2. People 2.1. Culture
  4. 2.2. Roles and Accountabilities

2.4 Stakeholders

Previous2.3. Transparency & CommunicationNext3. Processes

Last updated 4 months ago

When talking about the people involved in a legal project, those outside the project team should also be considered. Stakeholders are all people or even institutions (e.g. legislature) who have an interest or may affect the project. They consist, for example, of all team members in the law firm and on the client side who are part of the project, suppliers, and the counterparty, if any.

The core message of this chapter is that it is important to deal with stakeholders and assess them, and we want to show how to visualize this process. In practice, you will not map your stakeholders for every tiny case, but the more complex, the more critical and the bigger a case gets, the more important it gets to keep track of all the stakeholders involved and to know how to deal with them.

Even though it is the Product Owner who mainly deals with the stakeholders, it helps to visualize them so that they are transparent for everyone involved. Stakeholders can be shown on a grid which shows their infl uence on one axis and their interest in the project on another. For a more detailed assessment, a table can be fi lled out that deals with each individual stakeholder. On each one, it is noted how big their infl uence on and interest in the project are. From low “-“, through neutral “0”, to positive “+”. The last column consists of a note how to deal with a stakeholder of a particular rating or comments on an individual person.

Story

Of witnesses and other stakeholders

The team’s client, Bob, reacted well to their Agile project and our team is thinking about being even more open. First, they have a meeting with the client’s project manager, Caleb, to introduce more details about the project and the people involved. They already know about the counterparty, Eric, and his company but they neither know much about Horizontal Building’s customer, nor about potential interfaces with other third parties. While they have ample experience in explaining to clients about the challenges of working with witnesses, Gabriel read about stakeholder management when he delved into Agile literature. They decide to implement the stakeholder tools often used in Agile to get a joint understanding with Caleb and Bob about who is directly or indirectly involved in the case and how much infl uence each stakeholder has. The stakeholder map might have an impact on the fl ow of information, based on the actions regarding the different stakeholders. With this you should not forget to inform any important stakeholders.

Example

The team sets up a stakeholder map for the current case:

Name
Influence
Interest
Action

Internal Stakeholder

Partner A

+

+

Inform and use as champion.

Partner B

+

-

Inform and sway.

Marketing

-

+

Inform if there are interesting aspects that can be used.

Secretary

0

0

Keep in the loop.

IT Professional

+

0

Inform and bring on board.

External Stakeholder

Bob

+

+

Focus!

Caleb

-

+

Get information.

Eric

+

+

Focus! Sway

Sara

-

0

Use as expert.

Court

+

0

Inform

Legislator

+

-

Keep up to date with legislative changes

Template

Name
Influence
Interest
Action

Internal Stakeholder

External Stakeholder