Agile as a comprehensive methodology is fairly new. Although many concepts that are now considered Agile predate the term, we can trace the unified theory to a gathering of software developers and technology managers in early 2001. Frustrated by traditional methods for managing software projects, they gathered in Snowbird, Utah to adopt a Manifesto for Agile Software Development:
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
Individuals and interactions over processes and tools;
Working software over comprehensive documentation;
Customer collaboration over contract negotiation;
Responding to change over following a plan.
That is, while there is value in the items on the right, we value the items on the left more.
Agile adoption spread rapidly in the tech sector and is gaining traction in other business settings. By 2016, 94 percent of respondents to the annual State of Agile Survey reported using Agile in their enterprise. Those companies credit Agile for improvements in their:
The cover story of the May 2018 Harvard Business Review highlights how Agile has spread throughout the enterprise to areas such as “product development, marketing, and even HR.” And a 2016 Lexpert magazine article highlights successful Agile implementations in law firms and corporate legal teams.
Today, there are a number of specific methodologies that fall under the Agile umbrella. Some are primarily software and technology focused; examples include eXtreme Programming, Crystal, and DevOps. Others – like Scrum, Kanban, their hybrid ScrumBan, and the Scaled Agile Framework (SAFe – are often used throughout an organization.
I first became interested in applying Agile methods in a legal setting shortly after earning my J.D. in 2007. Before law school I spent nearly a decade in the technology sector, most of that with a single company, Getty Images. Over that time I participated in a number of technology projects, all of them using what we now think of as traditional, or waterfall, project management techniques.
My first legal job working for Getty Images as in-house counsel, a company where I’d spent over seven years before going to law school. It was great to be working again with many of the same teams and people I knew well. While I was away studying, however, Getty’s technology managers had shifted from a traditional, waterfall project management style to Agile management methods. I’d been vaguely aware of Agile prior to then (my wife works in technology), but being back at Getty was the first time I’d seen it in action. I quickly recognized one thing: it was WAY better.
It wasn’t perfect, of course, but the teams were delivering their projects more quickly and with less back-and-forth among constituents (who also seemed to get along better). It yielded results, too: Getty at the time was responding to the rise of social image sharing and a corresponding shift in the photography marketplace. Agile development helped the company to adapt its strategies and stay ahead of shifting customer expectations.
When I transitioned to private practice, I experimented with Agile methods in my own IP boutique. I wrote my first article on Agile for Lawyers for the ABA’s Law Practice Today in 2015. Eventually I began to teach Agile methods to other legal professionals informally, then professionally. In the process, I’ve learned how to translate and adapt Agile concepts so they work well for legal teams.
Today I’ve taught Agile – plus complementary management methods like Lean, Jobs To Be Done, Lean Startup, and Design Thinking – to thousands of legal professionals on teams of all types and sizes. Over the course of my work, and of observing Agile’s evolution in other industries, I’ve come to recognize four core principles for an Agile legal practice:
Stay tuned for additional posts diving into each one of these principles in more detail.
Note: This article is adapted from a chapter I contributed to the ARK Group book, Tipping Point: Transformation and Innovation in the Legal Department.
The whole book is $195, but you can now get my entire chapter for free by clicking here.
Here’s how it came to be:
I was at ABA Techshow a few weeks ago watching Jess Birken & Charity Anastasio deliver a talk about Kanban for Lawyers, which I think is great. My goal has always been to start a movement around Agile tools for legal professionals, so I love that others are spreading the gospel. Jordan Couch was in the room, who has also been teaching Kanban a fair bit lately.
Here’s the thing: I know I taught Kanban to Jess and Jordan, and I’m pretty sure Jordan taught Charity (or maybe it was Greg McLawsen, I’m not sure).
So I was standing in the back with the amazing Aastha Madaan (also an agile attorney) and I jokingly whispered to her, “I should start a video library of other people teaching my stuff.” Her response surprised me: Continue reading
Quality standards prevent mistakes.
As a standalone sentiment it seems like a no-brainier. Lawyers strive for quality: how often have you seen lawyer marketing with claims like “We provide our clients with the highest quality legal work,” or “We do quality work at an outstanding value”?
Of course we strive for quality. It’s why people hire professionals like us, and it’s what we’re trained to do (especially when it is drilled into us by our superiors).
Why, then, do lawyers keep messing up?Continue reading
Unless you’re a lone wolf, your project is going to have hand-offs.
Sorry, did I say “project?” I forgot for a moment that this is a legal blog. I meant “matter.” Or “case.” Or whatever else you call that “individual or collaborative enterprise that is carefully planned and designed to achieve a particular aim.”1 For consistency with the rest of the business world, let’s call it a project.Continue reading
A few weeks ago I woke up on a Saturday to a small explosion on my Twitter feed (when you write on an arcane topic like legal operations, small explosions seem significant). Turns out Joshua Lenon from Clio was presenting at the LegalLean conference in Toronto, where he was liberally and admittedly teaching from this very blog*. His presentation is great, and you can watch it below.
Stealing back from Joshua, I really like one of the things he talks about at the end pertaining to legal process/project management and I want to try to expand on it a little.Continue reading
[getty src=”456501701?et=r-qTYgCKT6Z9NXgfwpEQ1A&sig=Q0a2IK7BXklNSQs8J23lAC_2h8dh-WYylj8onTsfhdc=” width=”507″ height=”387″]
Legal Project Management is quite the buzzword these days. Of course the concept has been around for years, but the recent publication of the ABA’s The Power of Legal Project Management has renewed the push for lawyers to adopt the project management techniques that have been used in the business world for decades.
Here’s the problem: the project management methodology being marketed to lawyers—whether by the ABA book, an upcoming ALI CLE, or any number of consulting firms—is outdated. Not only that, it isn’t especially well-suited to the dynamic and sometimes volatile nature of legal work.Continue reading