In the bustling world of Agile, where the dance of development unfolds in sprints and increments, guiding stars are essential. Every agile team knows the significance of clear directives and well-defined finish lines. Yet, many still grapple in the twilight of ambiguity, wondering when a task truly earns its ‘done’ badge. This not only strains the rhythm of progress but casts a shadow on the ensemble’s harmony.
As an Agile coach, I’ve seen countless teams pivot, falter, and rediscover their pace. The most consistent compass that has guided them?
A robust ‘Definition of Done’ (DoD) template.
Before delving into the template, let’s understand its essence. The DoD is not merely a checklist; it’s a symphony of commitment, clarity, and collaboration. It’s the golden thread that weaves through every stage of development, ensuring that when a task claims completion, it stands tall, tested, and triumphant.
Not Just for Software: The ‘Definition of Done’ in Mining
While this framework originated in Agile software development, the “Definition of Done” is increasingly critical in Junior Mining and Capital Markets.
In an exploration company, releasing data before it is “Done” isn’t just a bug—it’s a potential regulatory breach. For a Junior Miner, a drill result is not “Done” when the assays arrive from the lab. It is only “Done” when:
- QA/QC Verified: Blanks and standards have passed inspection.
- Geology Model Updated: The data has been contextualized within the wider deposit model.
- Competent Person (CP/QP) Signed: The release meets JORC or NI 43-101 standards.
- Market Narrative Aligned: The Investor Relations strategy is ready to translate the technical grade into shareholder value.
If you are a Mining Executive looking to bring Agile discipline to your exploration workflow, skip to our Mining-Specific Checklist below.
What goes into the DoD template?
- Code produced (all ‘to do’ items in code completed); commented and checked in
- Peer reviewed (or produced with pair programming) and meeting development standards
- Builds without errors … Unit tests written and passing
- Deployed to system test environment and passed system tests
- Passed UAT (User Acceptance Testing) and signed off as meeting requirements
- Any build / deployment / configuration changes are implemented / documented / communicated
- Relevant documentation / diagrams produced and / or updated
- Remaining hours for task set to zero and task closed
The Definition of Done may also be changed at any time to reflect what a team can complete within each sprint. However, changing the DoD should be an infrequent occurrence, and never something done prior to each sprint.
In the software world, if you ship a bug, you can patch it in the next sprint. In Capital Markets, you cannot “patch” a misleading RNS or news release without severe reputational damage.
For our mining clients, we adapt the DoD template to ensure technical and communication milestones are met simultaneously. Here is what a “Definition of Done” looks like for a high-grade intercept:
- Lab Data: Assays received, imported to the database, and QA/QC blanks/standards verified.
- Visual Verification: Assays checked against visual core logs (no major discrepancies).
- Visualisation: Cross-sections updated to show true width vs. apparent width.
- Compliance: Draft News Release/RNS reviewed and signed off by the Nomad and Qualified Person (QP/CP).
- Narrative: CEO quote finalized and “Key Takeaways” bullet points drafted for investors.
- Distribution: Social media assets (core photos, maps) are cropped, branded, and scheduled.
Only when all six are checked is the result “Done.”
Beyond the DoD Template
Having a ‘Definition of Done’ template is akin to having a magical score for your Agile orchestra. But remember, while the score is vital, the magic truly lies in how it’s interpreted and executed by each musician.
This template is just a starting point. Modify it, adapt it, and make it resonate with your team’s unique rhythm. And as you march ahead, stay tuned. The Agile journey is replete with lessons, tools, and techniques. In upcoming blog posts, we’ll uncover more gems to enrich your Agile repertoire, from sprint rituals to retrospective revelations.
So, set your pace, find your rhythm, and let the Agile symphony play on.
Last Updated on by GaryPine
