If you came to Scrum Board through a single complex case rather than through deliberate study, you’re in the company of most practitioners who eventually built real expertise in the area. Reverse-engineering depth from a hard case is a common career path.
Intended for guardians ad litem comparing their current approach to Scrum Board with what experienced practitioners in the area actually do.
GAL work on Scrum Board usually requires interviews with the parents, the child (age-appropriate), the school, and any treating providers. The triangulation across sources produces findings that any single source could not. GALs who rely primarily on parent interviews produce work that doesn’t survive vigorous cross-examination.
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.
The analytical work itself
Communication discipline during the middle phase prevents most of the problems that show up at the deliverable. Practitioners who send the client weekly or biweekly written updates — even short ones — maintain trust and surface issues early. Practitioners who go silent during the analytical work leave the client to imagine what might be happening, which is rarely productive.
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. For deeper reference, see IRS Publication 504 (Divorced or Separated Individuals).
The deliverable
Walk the client through the deliverable before they take it to the attorney or court. The presentation matters; the same report explained well lands differently than the same report dropped over email without context. The walk-through is also where the client’s last questions surface; addressing them in real time prevents follow-up cycles weeks later.
The deliverable for a Scrum Board engagement is the work product everyone will reference for years afterward. It needs to be defensible (your analysis can withstand scrutiny), readable (the client and any non-specialist can understand it), and complete (it addresses what the engagement was scoped to address). The deliverable usually takes 20-40% of the engagement hours; underestimating this consistently produces matters that run over time.
Matter-specific considerations
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.
Matters with unsophisticated clients require more explanation, slower pacing, and more deliverable walk-through time than matters with sophisticated clients. Practitioners who run the same engagement structure regardless of client sophistication produce uneven outcomes; calibrating to the client is part of professional judgment.
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 helps guardians ad litem build the operational backbone Scrum Board engagements require — engagement letters that handle the scoping conversation in writing, case files that stay organized across long matters, communication tools that keep the broader case team coordinated, and the infrastructure that lets the practitioner focus on the analytical work rather than the administrative drag.
If you’re a guardian ad litem building a focus on Scrum Board and looking for the operational backbone, visit VennBoard.com to see how it fits into your practice.
Further reading
ABA Family Law Section resources
IRS Publication 504 (Divorced or Separated Individuals)