Most practitioners encounter Scrum Board as a passing question from a referral source before they treat it as a practice area. The ones who eventually own the area in their market did the opposite.
This piece is for divorce financial coaches who already have the basics and are deciding whether to make Scrum Board a focus area.
For divorce financial coaches, Scrum Board sits at the intersection of financial analysis and client communication. The technical work matters but the client-facing translation matters as much. Coaches who can explain a complex Scrum Board finding to a non-financial client in plain language produce engagements that drive better client decisions than coaches whose deliverables only the attorney can interpret.
How Scrum Board engagements begin
Document the intake. Either contemporaneous notes you keep in the file or a follow-up summary email to the client. Scrum Board engagements involve enough small decisions across long timelines that working from memory six months in produces errors.
The intake conversation for Scrum Board matters does most of the work of the engagement. Practitioners who run a structured intake — covering the client’s objectives, the timeline they’re working with, the co-professionals on the case, the data and documents needed, and the form the deliverable will take — produce engagement letters that hold their shape through the matter. Practitioners who run an unstructured intake produce engagement letters that get rewritten or absorb scope creep silently.
What happens in the middle phase
Analytical work during the middle phase often produces interim findings that affect the engagement scope. A finding the client didn’t anticipate may open new questions; a finding consistent with expectations may close lines of inquiry. The engagement letter should anticipate these scope adjustments and provide a path for handling them without requiring full re-papering.
The middle phase of a Scrum Board engagement is mostly about data gathering, analysis, and coordination. The data gathering involves requesting documents from the client and (often) from third parties through subpoenas or formal requests. The analysis involves working through what the documents reveal. The coordination involves keeping the attorney and other co-professionals informed.
Producing the work product
Most Scrum Board deliverables follow a consistent format that practitioners refine over multiple matters. An executive summary at the top. Background and scope. Methodology. Findings. Conclusions and recommendations. Appendices with supporting documentation. Practitioners who maintain a template they refine engagement by engagement produce stronger deliverables faster than those who reinvent the format each time.
Review the deliverable with a peer before it goes out, especially in your first dozen Scrum Board matters. A senior practitioner or a peer who has done similar work will catch things you didn’t notice — both substantive issues in the analysis and presentation issues that affect how the deliverable lands.
When the standard doesn’t apply
Scrum Board engagements vary along a few predictable dimensions: client sophistication (institutional client vs. unsophisticated individual), case complexity (single straightforward question vs. multiple intertwined issues), opposing-side cooperation (cooperative vs. adversarial), and timeline pressure (negotiated timeline vs. court-imposed deadlines). Each dimension affects how the standard engagement pattern needs to adjust. For deeper reference, see ABA Family Law Section resources.
High-conflict matters require different communication and documentation discipline than cooperative ones. In high-conflict Scrum Board engagements, every communication may eventually be reviewed by opposing counsel or a judge; the practitioner needs to write as if the matter will be litigated, even when it won’t be.
If you’re considering Scrum Board as a focus area and you want one concrete commitment to make: pick the upcoming family-law conference closest to you and commit to attending every year for the next five years.
How VennBoard fits in
VennBoard supports the kind of case-management discipline Scrum Board engagements benefit from: organized case files, integrated communication with co-professionals, deliverable versioning, and the kind of operational consistency that makes the difference between burning out at twenty matters and running a sustainable practice at fifty.
Practitioners interested in seeing VennBoard’s case-management infrastructure for Scrum Board work can learn more at VennBoard.com.
Further reading
Federal Office of Child Support Enforcement
National Center for State Courts