https://deevnet.github.io/deevnet-docs/docs/standards/project-workflows/Recent content in Project Workflows on Deevnet Infrastructure PlatformHugoen-ushttps://deevnet.github.io/deevnet-docs/docs/standards/project-workflows/embedded-hardware/Mon, 01 Jan 0001 00:00:00 +0000https://deevnet.github.io/deevnet-docs/docs/standards/project-workflows/embedded-hardware/<h1 id="embedded-hardware-workflow"> Embedded Hardware Workflow <a class="anchor" href="#embedded-hardware-workflow">#</a> </h1> <p>Template for hardware projects involving microcontrollers, custom PCBs, firmware, and physical enclosures. Follows the EVT/DVT/PVT hardware development lifecycle.</p> <p><strong>Legend:</strong> ✅ Complete | 🔄 In Progress | ⏳ Planned</p> <hr> <h2 id="project-vision--scope"> Project Vision &amp; Scope <a class="anchor" href="#project-vision--scope">#</a> </h2> <p>Define what the project aims to achieve and establish boundaries.</p> <p><strong>In Scope</strong></p> <ul> <li>Core functionality and features</li> <li>Target hardware platform</li> <li>Key interfaces and protocols</li> <li>Physical form factor requirements</li> </ul> <p><strong>Out of Scope</strong></p> <ul> <li>Features explicitly excluded</li> <li>Integration points deferred to future phases</li> <li>Capabilities beyond project goals</li> </ul> <hr> <h2 id="milestone-requirements--constraints-"> Milestone: Requirements &amp; Constraints ⏳ <a class="anchor" href="#milestone-requirements--constraints-">#</a> </h2> <p>Define what success means before building.</p>https://deevnet.github.io/deevnet-docs/docs/standards/project-workflows/site-iac/Mon, 01 Jan 0001 00:00:00 +0000https://deevnet.github.io/deevnet-docs/docs/standards/project-workflows/site-iac/<h1 id="site-iac-workflow"> Site IaC Workflow <a class="anchor" href="#site-iac-workflow">#</a> </h1> <p>Template for full infrastructure site builds involving bare-metal provisioning, network automation, and end-to-end rebuild validation. Use this for complex, multi-layer infrastructure projects.</p> <p>For simpler automation projects, see <a href="../iac-cac/">IaC/CaC</a>.</p> <p><strong>Legend:</strong> ✅ Complete | 🔄 In Progress | ⏳ Planned</p> <hr> <h2 id="project-vision--scope"> Project Vision &amp; Scope <a class="anchor" href="#project-vision--scope">#</a> </h2> <p>Define the infrastructure domain and automation goals.</p> <p><strong>In Scope</strong></p> <ul> <li>Target infrastructure components</li> <li>Automation tooling</li> <li>Provisioning and configuration scope</li> <li>Operational boundaries</li> </ul> <p><strong>Out of Scope</strong></p>https://deevnet.github.io/deevnet-docs/docs/standards/project-workflows/application-development/Mon, 01 Jan 0001 00:00:00 +0000https://deevnet.github.io/deevnet-docs/docs/standards/project-workflows/application-development/<h1 id="application-development-workflow"> Application Development Workflow <a class="anchor" href="#application-development-workflow">#</a> </h1> <p>Template for software projects including services, tools, libraries, and applications. Covers the common phases of software development lifecycle.</p> <p><strong>Legend:</strong> ✅ Complete | 🔄 In Progress | ⏳ Planned</p> <hr> <h2 id="project-vision--scope"> Project Vision &amp; Scope <a class="anchor" href="#project-vision--scope">#</a> </h2> <p>Define what the application aims to achieve and establish boundaries.</p> <p><strong>In Scope</strong></p> <ul> <li>Core functionality and features</li> <li>Target platforms and environments</li> <li>Key integrations and dependencies</li> <li>User personas and use cases</li> </ul> <p><strong>Out of Scope</strong></p>https://deevnet.github.io/deevnet-docs/docs/standards/project-workflows/iac-cac/Mon, 01 Jan 0001 00:00:00 +0000https://deevnet.github.io/deevnet-docs/docs/standards/project-workflows/iac-cac/<h1 id="iaccac-workflow"> IaC/CaC Workflow <a class="anchor" href="#iaccac-workflow">#</a> </h1> <p>Template for Infrastructure as Code and Configuration as Code projects that automate a single system, appliance, or service. Use this for focused automation projects that don&rsquo;t require full site orchestration.</p> <p>For complex multi-layer infrastructure, see <a href="../site-iac/">Site IaC</a>.</p> <p><strong>Legend:</strong> ✅ Complete | 🔄 In Progress | ⏳ Planned</p> <hr> <h2 id="project-vision--scope"> Project Vision &amp; Scope <a class="anchor" href="#project-vision--scope">#</a> </h2> <p>Define the automation target and goals.</p> <p><strong>In Scope</strong></p> <ul> <li>Target system or service</li> <li>Automation tooling</li> <li>Configuration scope</li> <li>Deployment target</li> </ul> <p><strong>Out of Scope</strong></p>