Over the weekend I read a post over on the www.pmhut.com website by Chuck Snead – An Agile Primer: Agile Estimating and the “MoSCoW Process” – which contained an interesting process that I would like to share with you today.

Although the www.pmhut.com website (the “pm” here standing for “Project Management”) doesn’t do posts that relate directly to either law firm business development or marketing, I enjoy reading their posts as I find many of the concepts they cover can easily be applied to the industry. As was the case this weekend, with a guest post by Snead which threw up a very interesting acronym and concept that I had not previously heard of – the “MoSCoW Process”  – and which I now believe should be tailored to form part of any law firm costing/engagement/fee proposal letter process with your client.

So here goes.

Snead stipulates that:

MoSCoW is an acronym for prioritizing feature development along the following guidelines:

• MUST have features that are required for the project to be called a success.
• SHOULD have features that have a high priority, but are not required for success.
• COULD have features which would be nice to have, but are not high priority.
• WON’T have features that stakeholders agree should be in a future release.

Now let’s apply this to the law firm costing/engagement/fee proposal letter process you go through with your client and agree that your next costing/engagement/fee proposal will include the following:

• a section in the letter setting out all of the actions/tasks that MUST be done in order for the client’s objective to be met [Category 1 critical]. Here, assign who will be given the task and either the fixed or estimated cost to achieve these tasks; next
• a section in the letter setting out the actions/tasks that would it would be ‘nice’ (SHOULD) if they were done, but they are not critical to the achievement of the client’s objective(s)[Category 2 critical]. Again, assign who would be given the task if there is sufficient time/budget/desire, etc and either the fixed or estimated cost to achieve these tasks; next
• a section in the letter setting out the actions/tasks that are [remote] ‘possibles’ (COULD) that may arise out of the client undertaking the action they are planning to take. It should be noted that this should be remote variables/possibilities [Category 3 – variables]. Again, assign who would be given the task if one of these remote variables were to arise and wherever possible attach a fixed fee or estimate against the task; finally
• set out clearly in the letter those actions the law firm WON’T be taking (is not instructed to take). Now it could be the case that these actions are still needed in order for the client’s objectives to be met, but they will be undertaken elsewhere (eg, in-house or through an LPO) [Category 4 – won’t dos]. Note, this is not a ‘disclaimer’ or limitation on liability section per se, but assigning tasks so that each party knows exactly what is and what is not required of them.

Anyone else out there think we may just have a few less angry client complaints if we went through a process like this each time we took on a new matter?

This process might not be perfect, and it could well need a tweak here and there, but I do think it will go a long way to helping lawyers fully understand the scope and nature of the instruction(s) they receive from their client(s) and lead to less misunderstanding in the industry.

And if that’s the case, the result is a win-win all round.