---
id: video/9zQZHfXK-PQ
type: video
title: "From Code to Docs: Using GitHub Copilot to Automate Business Central Documentation"
summary: "Spec-driven AL development with GitHub Copilot for Business Central: a docs-to-code workflow using agents, skills and living documentation in a Git repo. The session demos user stories, specs, architecture decisions, change control notices, release notes and SharePoint sync via GitHub Actions."
tier: community
language: en
tags:
  - documentation automation
  - github copilot
  - spec-driven development
  - al development
  - user stories
  - architecture decisions
  - living artifacts
  - version control
  - change control
  - release notes
  - testing documentation
  - agent framework
system: development
review:
  state: reviewed
  by: opus
  at: "2026-10-07T23:17:26.725Z"
  flags: []
generated:
  at: "2026-10-07T23:17:26.811Z"
  pipeline: 0.2.0
  prompts:
    extract-video: 1
    summarize-video: 2
  input_hash: 53d95ab16cd0804ce130a3fd801d81ed4a1f08f003155e4333432c094ec68ca9
evidence:
  - kind: video
    url: https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=235s
    title: "From Code to Docs: Using GitHub Copilot to Automate Business Central Documentation"
    date: "2026-10-01T05:38:51.000Z"
    commit: null
    t: 235
    quote: nobody cares or likes to document me both
  - kind: video
    url: https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=313s
    title: "From Code to Docs: Using GitHub Copilot to Automate Business Central Documentation"
    date: "2026-10-01T05:38:51.000Z"
    commit: null
    t: 313
    quote: yes we are going to stop how a project start. Yeah, when we are starting our project, we have clear requirements.
  - kind: video
    url: https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=551s
    title: "From Code to Docs: Using GitHub Copilot to Automate Business Central Documentation"
    date: "2026-10-01T05:38:51.000Z"
    commit: null
    t: 551
    quote: the point is the problem is not that we are flexible to add to up to the customer's needs. The problem is we do
  - kind: video
    url: https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=591s
    title: "From Code to Docs: Using GitHub Copilot to Automate Business Central Documentation"
    date: "2026-10-01T05:38:51.000Z"
    commit: null
    t: 591
    quote: good solutions need good documentation not just at the beginning but throughout all the journey
  - kind: video
    url: https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=787s
    title: "From Code to Docs: Using GitHub Copilot to Automate Business Central Documentation"
    date: "2026-10-01T05:38:51.000Z"
    commit: null
    t: 787
    quote: with this new approach we capture and approve documentation at the first step of the of the process
links:
  learn: []
  objects:
    - object/enum/18350-in
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
video_id: 9zQZHfXK-PQ
channel: yt-mibuso
source_name: mibuso.com / BC TechDays
url: https://www.youtube.com/watch?v=9zQZHfXK-PQ
published_at: "2026-10-01T05:38:51.000Z"
duration_s: 5001
captions: derived
audience:
  - developer
  - functional consultant
  - decision maker
chapters:
  - t: 0
    title: Introduction and speaker introductions
  - t: 107
    title: Session overview and presentation structure
  - t: 173
    title: The uncomfortable truth about documentation
  - t: 303
    title: How projects evolve and documentation falls behind
  - t: 445
    title: Consequences of lacking documentation
  - t: 591
    title: The comfortable truth and need for documentation throughout lifecycle
  - t: 655
    title: Traditional code-to-docs approach limitations
  - t: 773
    title: New docs-to-code approach with GitHub Copilot
  - t: 909
    title: From docs to code paradigm shift
  - t: 984
    title: Spec-driven development vs rapid coding
  - t: 1099
    title: Problems with AI agents without specifications
  - t: 1243
    title: Main characteristics of spec-driven development
  - t: 1348
    title: Living artifacts and documentation requirements
  - t: 1495
    title: Keeping documentation alive in GitHub
  - t: 1677
    title: Documentation as source of truth for agents
  - t: 1820
    title: Agent framework overview and accountability
  - t: 1969
    title: Business consultant and architect agent roles
  - t: 2099
    title: Analysis documents and customer decision-making
  - t: 2198
    title: Developer agents and sequential workflow
  - t: 2300
    title: Agent skills and documentation consistency
  - t: 2457
    title: Documentation skills and development lifecycle
  - t: 2499
    title: Moving from PowerPoint to code and Visual Studio
  - t: 2615
    title: AL Development Collection extension and baseline
  - t: 2673
    title: Copilot skill collection and open source community
  - t: 2746
    title: Biceps framework and document delivery to SharePoint
  - t: 2823
    title: Symlinks for managing multiple agent frameworks
  - t: 2966
    title: Standardizing agentic framework across teams
  - t: 3087
    title: User story generation and decomposition from requirements
  - t: 3262
    title: Converting requirements to formatted user stories with templates
  - t: 3410
    title: Documentation organization, templates, and SharePoint integration
  - t: 3555
    title: Specifications and architecture decision documentation
  - t: 3671
    title: Feasibility analysis, risk assessment, and quality review process
  - t: 3807
    title: Change control notice creation and customer approval
  - t: 3940
    title: Customer approval handoff and developer phase with AI model selection
  - t: 4051
    title: Phase implementation results, release notes generation, and testing documentation
  - t: 4254
    title: Testing strategy and available resources
  - t: 4403
    title: Recommended tools and GitHub repositories
  - t: 4534
    title: "Q&A: Project management approach"
  - t: 4661
    title: "Q&A: Release notes with screenshots and available tools"
  - t: 4738
    title: "Q&A: Specification branching, integration, and branch management"
  - t: 4805
    title: Branch deletion strategy, commit history tracking, and closing remarks
  - t: 4902
    title: Discussion on prototypes vs documentation and proof of concepts
features:
  - name: Docs-to-code development methodology
    status: unclear
    t: 773
    verified: false
    status_source: video
  - name: Spec-driven development framework
    status: unclear
    t: 937
    verified: false
    status_source: video
  - name: Living artifacts in repositories
    status: unclear
    t: 1348
    verified: false
    status_source: video
  - name: AI agents with specification context
    status: unclear
    t: 984
    verified: false
    status_source: video
  - name: Decision tracking with reviewer attribution
    status: unclear
    t: 1700
    verified: false
    status_source: video
  - name: Documentation as single source of truth for agents
    status: unclear
    t: 1804
    verified: false
    status_source: video
  - name: Business consultant agent
    status: unclear
    t: 1846
    verified: false
    status_source: video
  - name: Architect agent for specs and architecture documents
    status: unclear
    t: 1935
    verified: false
    status_source: video
  - name: Analyst agent with SWAT analysis
    status: unclear
    t: 2076
    verified: false
    status_source: video
  - name: Developer agent with plans
    status: unclear
    t: 2198
    verified: false
    status_source: video
  - name: GitHub Copilot skills for documentation
    status: unclear
    t: 2338
    verified: false
    status_source: video
  - name: Documentation skill
    status: unclear
    t: 2442
    verified: false
    status_source: video
  - name: AL Development Collection extension
    status: unclear
    t: 2601
    verified: false
    status_source: video
  - name: Copilot skill collection
    status: unclear
    t: 2700
    verified: false
    status_source: video
  - name: Biceps framework integration
    status: unclear
    t: 2746
    verified: false
    status_source: video
  - name: Symlinks for agent management
    status: unclear
    t: 2795
    verified: false
    status_source: video
  - name: Multi-department agentic framework standardization
    status: unclear
    t: 2955
    verified: false
    status_source: video
  - name: User story generation from requirements
    status: unclear
    t: 3087
    verified: false
    status_source: video
  - name: Skills-based document formatting with templates
    status: unclear
    t: 3297
    verified: false
    status_source: video
  - name: GitHub Actions integration for SharePoint documentation sync
    status: unclear
    t: 3526
    verified: false
    status_source: video
  - name: Architecture decision documentation with human-in-the-loop
    status: unclear
    t: 3577
    verified: false
    status_source: video
  - name: Feasibility analysis and risk assessment in specifications
    status: unclear
    t: 3725
    verified: false
    status_source: video
  - name: Change Control Notice with approval workflow
    status: unclear
    t: 3827
    verified: false
    status_source: video
  - name: AI model selection strategy for task complexity
    status: unclear
    t: 3993
    verified: false
    status_source: video
  - name: Release notes generation with AI
    status: unclear
    t: 4121
    verified: false
    status_source: video
  - name: Testing documentation in release notes
    status: unclear
    t: 4210
    verified: false
    status_source: video
  - name: Feature limitation documentation
    status: unclear
    t: 4238
    verified: false
    status_source: video
  - name: Test-driven development integration
    status: unclear
    t: 4302
    verified: false
    status_source: video
  - name: AL Copilot Skills
    status: unclear
    t: 4438
    verified: false
    status_source: video
  - name: OpenSpec framework
    status: unclear
    t: 4464
    verified: false
    status_source: video
  - name: Automated video-to-script generation for release notes
    status: unclear
    t: 4706
    verified: false
    status_source: video
  - name: Screenshot automation in documentation workflows
    status: unclear
    t: 4720
    verified: false
    status_source: video
  - name: Jira integration with specification documents
    status: unclear
    t: 4783
    verified: false
    status_source: video
  - name: Branch-based specification management
    status: unclear
    t: 4760
    verified: false
    status_source: video
  - name: Proof of concept approach for validation
    status: unclear
    t: 4925
    verified: false
    status_source: video
objects_mentioned:
  - codeunit codeunit
  - other user story generator skill
  - other technical spec generator skill
  - other MADM file
  - enum enum
  - table related table
  - enum status
quotes:
  - t: 235
    text: nobody cares or likes to document me both
    check: exact
  - t: 313
    text: yes we are going to stop how a project start. Yeah, when we are starting our project, we have clear requirements.
    check: exact
  - t: 551
    text: the point is the problem is not that we are flexible to add to up to the customer's needs. The problem is we do
    check: exact
  - t: 591
    text: good solutions need good documentation not just at the beginning but throughout all the journey
    check: exact
  - t: 787
    text: with this new approach we capture and approve documentation at the first step of the of the process
    check: fuzzy
---

# From Code to Docs: Using GitHub Copilot to Automate Business Central Documentation

> Spec-driven AL development with GitHub Copilot for Business Central: a docs-to-code workflow using agents, skills and living documentation in a Git repo. The session demos user stories, specs, architecture decisions, change control notices, release notes and SharePoint sync via GitHub Actions.

[Watch on YouTube](https://www.youtube.com/watch?v=9zQZHfXK-PQ) · mibuso.com / BC TechDays · 2026-10-01 · 1:23:21 · tier community · reviewed (checked by Opus)

## Overview

The session argues that documentation usually falls behind as projects evolve, and that this causes misunderstandings between customer and team. The speakers propose a docs-to-code approach: requirements, user stories, specifications and architecture decisions are captured and approved first, kept in a GitHub repository, and used as the source of truth for Copilot agents. They stress that the agents have no accountability, so humans must review and own every document.

The demo walks through a sequential agent framework (business consultant, architect, analyst, developer) and Copilot skills that enforce output structure. It covers user story generation, Word templates filled by a Python script, SharePoint delivery with GitHub Actions, a change control notice with customer approval, model selection, release notes and testing steps. The speakers say the framework is not perfect and should be adapted to each organization. The Q&A covers Jira, branching, screenshots and proof of concepts.

## Key points

- Documentation is kept in the Git repository, updated before development starts and changed with each commit, so decisions are traceable to who made them and when.
- The agent workflow is sequential: business consultant (checks Microsoft Learn for existing functionality), architect, analyst (SWOT analysis), then developer agents working from atomic task plans. All generated documents need human review.
- Copilot skills give structured, consistent output where plain prompting does not. The demo includes skills for user stories, technical specs, architecture documents, feasibility analysis, change control, phase plans and release notes.
- A change control notice summarizes architecture decisions, specs, feasibility and risk, and needs customer sign-off before implementation begins.
- Suggested model use: strong models such as Opus for consultant, architect, analyst and skill creation, and cheaper models such as Haiku for development and review once tasks are well specified.
- Symlinks let several repositories share a standard agentic framework kept in a central repo with a protected main branch, and you can switch branches to test framework changes. A GitHub Action syncs user story documents to SharePoint when changes are pushed to main.
- Release notes are generated from repository context and include testing steps and limitations. Screenshots still need manual capture.

## Chapters

- [0:00](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=0s) Introduction and speaker introductions
- [1:47](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=107s) Session overview and presentation structure
- [2:53](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=173s) The uncomfortable truth about documentation
- [5:03](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=303s) How projects evolve and documentation falls behind
- [7:25](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=445s) Consequences of lacking documentation
- [9:51](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=591s) The comfortable truth and need for documentation throughout lifecycle
- [10:55](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=655s) Traditional code-to-docs approach limitations
- [12:53](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=773s) New docs-to-code approach with GitHub Copilot
- [15:09](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=909s) From docs to code paradigm shift
- [16:24](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=984s) Spec-driven development vs rapid coding
- [18:19](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=1099s) Problems with AI agents without specifications
- [20:43](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=1243s) Main characteristics of spec-driven development
- [22:28](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=1348s) Living artifacts and documentation requirements
- [24:55](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=1495s) Keeping documentation alive in GitHub
- [27:57](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=1677s) Documentation as source of truth for agents
- [30:20](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=1820s) Agent framework overview and accountability
- [32:49](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=1969s) Business consultant and architect agent roles
- [34:59](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2099s) Analysis documents and customer decision-making
- [36:38](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2198s) Developer agents and sequential workflow
- [38:20](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2300s) Agent skills and documentation consistency
- [40:57](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2457s) Documentation skills and development lifecycle
- [41:39](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2499s) Moving from PowerPoint to code and Visual Studio
- [43:35](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2615s) AL Development Collection extension and baseline
- [44:33](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2673s) Copilot skill collection and open source community
- [45:46](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2746s) Biceps framework and document delivery to SharePoint
- [47:03](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2823s) Symlinks for managing multiple agent frameworks
- [49:26](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2966s) Standardizing agentic framework across teams
- [51:27](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3087s) User story generation and decomposition from requirements
- [54:22](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3262s) Converting requirements to formatted user stories with templates
- [56:50](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3410s) Documentation organization, templates, and SharePoint integration
- [59:15](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3555s) Specifications and architecture decision documentation
- [1:01:11](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3671s) Feasibility analysis, risk assessment, and quality review process
- [1:03:27](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3807s) Change control notice creation and customer approval
- [1:05:40](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3940s) Customer approval handoff and developer phase with AI model selection
- [1:07:31](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4051s) Phase implementation results, release notes generation, and testing documentation
- [1:10:54](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4254s) Testing strategy and available resources
- [1:13:23](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4403s) Recommended tools and GitHub repositories
- [1:15:34](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4534s) Q&A: Project management approach
- [1:17:41](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4661s) Q&A: Release notes with screenshots and available tools
- [1:18:58](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4738s) Q&A: Specification branching, integration, and branch management
- [1:20:05](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4805s) Branch deletion strategy, commit history tracking, and closing remarks
- [1:21:42](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4902s) Discussion on prototypes vs documentation and proof of concepts

## Features

| Feature | Status | At |
|---|---|---|
| Docs-to-code development methodology | status not stated | [12:53](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=773s) |
| Spec-driven development framework | status not stated | [15:37](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=937s) |
| Living artifacts in repositories | status not stated | [22:28](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=1348s) |
| AI agents with specification context | status not stated | [16:24](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=984s) |
| Decision tracking with reviewer attribution | status not stated | [28:20](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=1700s) |
| Documentation as single source of truth for agents | status not stated | [30:04](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=1804s) |
| Business consultant agent | status not stated | [30:46](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=1846s) |
| Architect agent for specs and architecture documents | status not stated | [32:15](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=1935s) |
| Analyst agent with SWAT analysis | status not stated | [34:36](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2076s) |
| Developer agent with plans | status not stated | [36:38](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2198s) |
| GitHub Copilot skills for documentation | status not stated | [38:58](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2338s) |
| Documentation skill | status not stated, demoed | [40:42](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2442s) |
| AL Development Collection extension | status not stated, demoed | [43:21](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2601s) |
| Copilot skill collection | status not stated, demoed | [45:00](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2700s) |
| Biceps framework integration | status not stated | [45:46](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2746s) |
| Symlinks for agent management | status not stated, demoed | [46:35](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2795s) |
| Multi-department agentic framework standardization | status not stated, demoed | [49:15](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2955s) |
| User story generation from requirements | status not stated, demoed | [51:27](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3087s) |
| Skills-based document formatting with templates | status not stated, demoed | [54:57](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3297s) |
| GitHub Actions integration for SharePoint documentation sync | status not stated, demoed | [58:46](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3526s) |
| Architecture decision documentation with human-in-the-loop | status not stated, demoed | [59:37](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3577s) |
| Feasibility analysis and risk assessment in specifications | status not stated, demoed | [1:02:05](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3725s) |
| Change Control Notice with approval workflow | status not stated, demoed | [1:03:47](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3827s) |
| AI model selection strategy for task complexity | status not stated | [1:06:33](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3993s) |
| Release notes generation with AI | status not stated, demoed | [1:08:41](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4121s) |
| Testing documentation in release notes | status not stated, demoed | [1:10:10](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4210s) |
| Feature limitation documentation | status not stated, demoed | [1:10:38](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4238s) |
| Test-driven development integration | status not stated | [1:11:42](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4302s) |
| AL Copilot Skills | status not stated | [1:13:58](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4438s) |
| OpenSpec framework | status not stated | [1:14:24](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4464s) |
| Automated video-to-script generation for release notes | status not stated | [1:18:26](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4706s) |
| Screenshot automation in documentation workflows | status not stated | [1:18:40](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4720s) |
| Jira integration with specification documents | status not stated | [1:19:43](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4783s) |
| Branch-based specification management | status not stated | [1:19:20](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4760s) |
| Proof of concept approach for validation | status not stated | [1:22:05](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4925s) |

## AL objects mentioned

As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.

- codeunit "codeunit" at [4:52](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=292s)
- other "user story generator skill" at [40:57](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2457s)
- other "technical spec generator skill" at [40:57](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2457s)
- other "MADM file" at [52:48](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3168s)
- enum "enum" at [1:00:27](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3627s)
- table "related table" at [1:00:27](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3627s)
- [enum 18350 "Status (IN)"](../objects/enum/18350-in.md) at [1:10:38](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4238s)

Not found in BC28-30: codeunit "codeunit", enum "enum", table "related table".

## Quotes

- [3:55](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=235s) "nobody cares or likes to document me both"
- [5:13](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=313s) "yes we are going to stop how a project start. Yeah, when we are starting our project, we have clear requirements."
- [9:11](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=551s) "the point is the problem is not that we are flexible to add to up to the customer's needs. The problem is we do"
- [9:51](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=591s) "good solutions need good documentation not just at the beginning but throughout all the journey"
- [13:07](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=787s) "with this new approach we capture and approve documentation at the first step of the of the process"

## Disclaimers in the video

- [2:53](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=173s) preview: a live demo no video. So let's see if everything works well.
- [31:09](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=1869s) other: this is a framework we have been developing is good for us. Doesn't need to be hood for you. You can adapt it to your organization.
- [33:37](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=2017s) other: we are providing a framework that we are working. It fit all operations doesn't need to fit yours. You can rethink this.
- [1:05:24](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=3924s) other: all of these I'm showing you is not perfect you can adapt it to your organizations and provide more value to your customers
- [1:08:29](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4109s) other: It works. Is it maintainable? uh perhaps not that much but it's something you need to try and you need to do it in a control way before you moving into your day by day use
- [1:11:08](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4268s) other: making it this way instead of putting your developer to just gr it down or having it without the skill ...
- [1:18:13](https://www.youtube.com/watch?v=9zQZHfXK-PQ&t=4693s) other: this firmware is not perfect and I can say it many times. Uh you can add it manually

Presenters (as heard): Fernando Espano, Raul, Fernando, Aresto, Jeremy.