Getting started with Dynamite | Agile
A team's path, from the first account to the validated prototype. The complete guide, with an exercise for each tool, is inside the tool itself: Help → the tour of the site, and the DEMO sandbox Space.
- The administrator
- Start with an AI assistant
- The team lead
- Every member
- The PDP in the tool
- The mine names
- Funded project
The administrator: preparing the ground
- Accounts⚙ Admin → Comptes → Règles d'accès: one line per person, with their role, study profile and rights per Space. Dry run first, then “Appliquer”.
- The project's Space⚙ Admin → Spaces: the key (e.g. EQP) becomes the ticket prefix (EQP-1, EQP-2…), never reused.
- ApproversEveryone chooses their approver (the instructor, the team lead) in the menu under their name → Paramètres; the administrator corrects it if needed (“Feuille de temps…”).
- Backups⚙ Admin → Update et sauvegardes: a restore point is taken every day and before every bulk operation.
Start a project with an AI assistant
No need to know in advance which requirements, standards or tests fit your product: an AI assistant suggests them in an interview, one question at a time, and gives you a file to import.
- Copy the prompt⚙ Admin → Spaces → Commencer → "Copy the English prompt" (or open starter.md and copy all the text).
- The interviewPaste it into a new conversation (Claude.ai, ChatGPT, Gemini, Copilot). About 26 questions to click (you only type the product and the names of the team), 30 to 45 minutes: the product, energy, radio, hazards, market, team, calendar, then the needs, requirements, tests, the functional tree and all of Diamond, and the pages it suggests and you correct. "I don't know" is a good answer.
- The fileSave the
.jsonfile it gives (Notepad → Save as, UTF-8 encoding). - The importCommencer → drop the file, read the preview, "Create the Space". Standards arrive "To verify": confirm them one by one before approving a requirement.
The team lead: launching the project
- Needs (Goldmine)Start from the needs of the customer and the stakeholders; the generic catalogue of a consumer product
(
deploy/requis_generiques.csv) imports in one click, then adapts to the CdCF (functional specification). - The plan (Exploration)The phases of the PDP, one MVP loop per phase, the reviews (Lean Canvas, Concept Review, PDR / CDR, Validation Report) and the Gantt; Excel round trip possible.
- Sprints (Agile)Backlog → Sprint → Board; each ticket “implements” a requirement.
- The decision (Tools)Brainwriting ideation, Pugh matrix, Kepner-Tregoe; the name and folder of every document with Generator.
Every member: a typical day
| When | Where | What |
|---|---|---|
| On arrival | Dashboard | My tickets, my requirements, my messages (@mentions), my week. |
| While working | Agile, Goldmine, Dynamite | Move the ticket forward, refine a requirement, write the note or the procedure in the wiki. |
| To prove it | Testing | Pick the test in the Test Base, generate the Test Plan, attach the result: the requirement becomes “Verified”. |
| Before leaving | Timesheet | The day's hours on the steps of the PDP, with a short description; submit on Friday. |
| To learn | Training, Help | Your training plan, the tests, the guided tour and DEMO to practise risk-free. |
The course's PDP in the tool
PDP = product development process. Each phase is a Build → Measure → Learn loop (Lean Startup): an MVP tests the riskiest hypotheses, Agile Sprints pace the hardware and software work, and the phase closes on a review and the decision to persevere or pivot. The loops rise like a tornado, wider and faster, up to the launch.
| Phase | MVP | Time codes | Deliverables (Generator) |
|---|---|---|---|
| A. Discovery | MVP 0: is the problem real? | A-01 to A-06 | Lean Canvas and hypotheses (LCV), market study, preliminary specifications, schedule, risks |
| B. Concept | MVP 1: do users like the concept? | B-07 to B-12 | Concept Review (CRV), needs, functional analysis, CdCF, QFD, morphological matrix, Pugh |
| C. Design | MVP 2: does it work? | C-13 to C-15 | PDR, CDR, subsystems, calculations, FMEA |
| D. Validation et lancement | MVP 3: ready for the market? | D-FAB, D-19 to D-21 | Validation Report (VVR), manufacturing, test protocol and results |
The mine names
| Tool | In the mine | In the project |
|---|---|---|
| DEMO & Training | The test tunnel at the mine entrance: every tool is tried there before going down. | The DEMO Space: the guided tour, a complete example (the Rover), a sandbox and the team's training. |
| Exploration | Prospecting: you study the ground and decide where to dig, in which order. | The product plan: PDP phases (Discovery, Concept, Design, Validation), MVPs, milestones, Gantt. |
| Dynamite | The charge that blasts the rock: raw knowledge is blasted loose and cleared. | The product's wiki: notes, minutes, decisions, procedures, pages drafted with AI. |
| Goldmine | The gold vein: what you came for, sorted nugget by nugget. | The customer needs and requirements, traced to the test that proves them. |
| Tools & Generator | The toolbox and the batch punch: every wagon gets its number. | The design methods (ideation, Pugh, Kepner-Tregoe) and the name of every deliverable. |
| Agile | The drilling crews, in shifts: each one knows which face to work. | Backlog, sprints and Board from one MVP to the next; Change Management when the tunnel drifts. |
| Testing | Assaying the ore: the grade is measured before the vein is declared worth it. | The product's Test Base, its procedures and plans that prove each requirement. |
| Timesheet | The shift log: who worked which face, for how many hours. | The hours per PDP step, vacation, funding claims. |
| Diamond | The diamonds, 1,000 m down: the hardest stone, cut facet by facet. | The functional analysis: function tree, structure, parts, risks and DFMEA, with their owners. |
A funded project: justify every hour
- The Funding SpaceTimesheet → ⚙ Admin → Spaces et organismes: create a Funding Space for the programme, with its Budget Lines (claimable or not), then attach the project's Space, its organism and its contract number.
- Time entryThe team enters its hours on these Budget Lines, with a short description per range; vacation (INT-VAC) and health leave (INT-SAN) from the INT Space are never claimed.
- The claimExcel export (summary, Budget Lines with every range and its justification, detail) or a Word report for the recipient, with the attestation to sign: no retyping.