<h2 class="compact-content-heading">How we deliver projects — <span class="handbook-highlight-pink">structured, transparent, on-time</span>.</h2>
<p class="compact-content-paragraph">A clear methodology built for <span class="handbook-highlight-blue">smooth delivery</span>, open communication, and successful business transformation. Whether your workflows are fixed or fast-changing, we have a delivery model that fits.</p>
<div class="handbook-onboarding-metric-cards">
<div class="handbook-metric-card"><strong>2</strong><span>delivery models: Agile and Waterfall</span></div>
<div class="handbook-metric-card"><strong>1</strong><span>dedicated SPOC per project</span></div>
<div class="handbook-metric-card"><strong>2-wk</strong><span>bi-weekly Agile sprint cycles</span></div>
<div class="handbook-metric-card"><strong>100%</strong><span>sign-off and checkpoint driven</span></div>
</div>
<h3 class="compact-content-heading">Our ERPNext Implementation Methodology</h3>
<h4 class="compact-content-heading">Two proven delivery models. One picked for you.</h4>
<p class="compact-content-paragraph">We follow a <span class="handbook-highlight-black">structured, transparent methodology</span> and work comfortably with both <span class="handbook-highlight-blue">Agile and fixed-cost Waterfall models</span>, chosen based on your requirements, project complexity, and engagement preference.</p>
<div class="handbook-delivery-recommendation">
<div class="handbook-delivery-recommendation-heading">
<span aria-hidden="true">i</span>
<strong>Which model we recommend</strong>
</div>
<table><tbody>
<tr><th>Model</th><th>Recommendation</th></tr>
<tr><td>Fixed-cost Waterfall</td><td>For organizations working with us for the first time or operating in a low-trust outsourcing environment, with clearly defined scope, timelines, deliverables, and approval checkpoints.</td></tr>
<tr><td>Agile</td><td>For businesses with evolving workflows, changing operational requirements, and fast-paced growth, allowing flexibility, faster iterations, and continuous improvement throughout the project lifecycle.</td></tr>
</tbody></table>
</div>
<div class="handbook-delivery-toggle" role="tablist" aria-label="Delivery model sections">
<p>Switch between the two models to see how each one runs</p>
<div>
<button type="button" class="is-active" data-delivery-model="agile">Agile</button>
<button type="button" data-delivery-model="waterfall">Waterfall</button>
</div>
</div>
<div class="handbook-delivery-panel is-active" data-delivery-panel="agile">
<h3 class="compact-content-heading">Agile ERPNext Development Methodology</h3>
<p class="compact-content-paragraph">Our Agile process is based on <span class="handbook-highlight-blue">collaborative planning</span>, <span class="handbook-highlight-black">continuous feedback</span>, and incremental delivery.</p>
<h4 class="compact-content-heading">Sprint Structure</h4>
<p class="compact-content-paragraph">We work in <span class="handbook-highlight-blue">bi-weekly ERPNext development sprints</span>. At the beginning of every sprint, tasks and development stories are prioritised based on <span class="handbook-highlight-pink">business impact</span> and implementation goals. Tap any step to see what happens in it.</p>
<div class="handbook-agile-card-flow">
<div class="handbook-agile-flow-card">
<span class="handbook-agile-flow-icon" aria-hidden="true">🎯</span>
<strong>Plan</strong>
<p>Align priorities and business goals.</p>
</div>
<div class="handbook-agile-flow-card">
<span class="handbook-agile-flow-icon" aria-hidden="true">📋</span>
<strong>Discover</strong>
<p>Understand requirements and expected outcomes.</p>
</div>
<div class="handbook-agile-flow-card">
<span class="handbook-agile-flow-icon" aria-hidden="true">📏</span>
<strong>Estimate</strong>
<p>Commit to realistic deliverables.</p>
</div>
<div class="handbook-agile-flow-card">
<span class="handbook-agile-flow-icon" aria-hidden="true">⚙️</span>
<strong>Build</strong>
<p>Develop and configure solutions.</p>
</div>
<div class="handbook-agile-flow-card">
<span class="handbook-agile-flow-icon" aria-hidden="true">🧪</span>
<strong>Validate</strong>
<p>Ensure quality and reliability.</p>
</div>
<div class="handbook-agile-flow-card">
<span class="handbook-agile-flow-icon" aria-hidden="true">🎥</span>
<strong>Demonstrate</strong>
<p>Show working functionality.</p>
</div>
<div class="handbook-agile-flow-card">
<span class="handbook-agile-flow-icon" aria-hidden="true">✅</span>
<strong>Deliver</strong>
<p>Collect feedback and close sprint.</p>
</div>
<div class="handbook-agile-flow-card">
<span class="handbook-agile-flow-icon" aria-hidden="true">🚀</span>
<strong>Continuous Improvement</strong>
<p>Move approved enhancements to the next sprint.</p>
</div>
</div>
<div class="handbook-agile-feedback">
<p><strong>Sprint Planning:</strong> Sprint goals are set and the backlog is prioritised by <span class="handbook-highlight-blue">business impact</span> and implementation goals. Customer feedback feeds directly into the next sprint's planning.</p>
</div>
<h4 class="compact-content-heading">Deliverables for Each Sprint</h4>
<div class="handbook-delivery-recommendation">
<div class="handbook-delivery-recommendation-heading handbook-delivery-recommendation-heading-black">
<strong>At the end of every sprint, customers receive:</strong>
</div>
<table><tbody>
<tr><th>#</th><th>Sprint Deliverable</th></tr>
<tr><td>1</td><td>Completed ERPNext features and modules</td></tr>
<tr><td>2</td><td>Workflow customizations</td></tr>
<tr><td>3</td><td>Reports and dashboards</td></tr>
<tr><td>4</td><td>Bug fixes and improvements</td></tr>
<tr><td>5</td><td>Sprint demo and progress update</td></tr>
<tr><td>6</td><td>Updated task tracker and implementation status</td></tr>
</tbody></table>
</div>
<div class="handbook-onboarding-kickoff-summary">
<div class="handbook-onboarding-kickoff-summary-card">
<span>Why it works</span>
<strong>Faster, more adaptive delivery</strong>
<p>This Agile delivery approach helps businesses <span class="handbook-highlight-blue">adapt quickly to operational changes</span> while ensuring faster implementation cycles.</p>
</div>
</div>
</div>
<div class="handbook-delivery-panel" data-delivery-panel="waterfall">
<h3 class="compact-content-heading">Waterfall ERPNext Implementation Methodology</h3>
<p class="compact-content-paragraph">In a fixed-cost waterfall model, we follow a structured phase-wise delivery process. Tap a phase to jump to its checklist.</p>
<div class="handbook-agile-card-flow handbook-waterfall-card-flow">
<div class="handbook-agile-flow-card">
<span class="handbook-agile-flow-icon" aria-hidden="true">📋</span>
<strong>Scope Definition</strong>
<p>Define and sign off the plan.</p>
</div>
<div class="handbook-agile-flow-card">
<span class="handbook-agile-flow-icon" aria-hidden="true">✅</span>
<strong>UAT Process</strong>
<p>Validate real business scenarios.</p>
</div>
<div class="handbook-agile-flow-card">
<span class="handbook-agile-flow-icon" aria-hidden="true">🚀</span>
<strong>Go-Live Ready</strong>
<p>Close UAT and prepare launch.</p>
</div>
</div>
<h3 class="compact-content-heading">Scope definition and sign-off</h3>
<p class="compact-content-paragraph"><span class="handbook-highlight-black">Before development begins:</span></p>
<ul class="handbook-onboarding-check-list">
<li>Detailed Business Requirements Document (BRD) is prepared.</li>
<li>Process flows and ERPNext solution mapping are finalised.</li>
<li>Deliverables, timelines, and responsibilities are defined.</li>
<li>Formal customer approval and sign-off is taken.</li>
</ul>
<div class="handbook-agile-feedback handbook-waterfall-scope-callout">
<p><span aria-hidden="true">⚠️</span> <strong>Scope control:</strong> Any requirement outside the approved scope is managed through a <span class="handbook-highlight-black">formal ERPNext change request process</span>.</p>
</div>
<h3 class="compact-content-heading">UAT (User Acceptance Testing) process</h3>
<table><tbody>
<tr class="handbook-table-section-heading"><th colspan="2">Once development is completed:</th></tr>
<tr><th>#</th><th>UAT Step</th></tr>
<tr><td>1</td><td>Features are deployed on the UAT environment</td></tr>
<tr><td>2</td><td>Customer teams perform ERPNext user acceptance testing</td></tr>
<tr><td>3</td><td>Business scenarios and workflows are validated</td></tr>
<tr><td>4</td><td>Bugs and issues are reported through the issue tracking system</td></tr>
<tr><td>5</td><td>Required fixes are completed before final approval</td></tr>
</tbody></table>
<h3 class="compact-content-heading">UAT closure process</h3>
<table><tbody>
<tr class="handbook-table-section-heading"><th colspan="2">The UAT phase is considered complete when:</th></tr>
<tr><th>#</th><th>Closure Requirement</th></tr>
<tr><td>1</td><td>All critical and major issues are resolved</td></tr>
<tr><td>2</td><td>Approved workflows are tested successfully</td></tr>
<tr><td>3</td><td>Customer sign-off is received</td></tr>
<tr><td>4</td><td>Final go-live readiness checklist is completed</td></tr>
</tbody></table>
</div>
<h3 class="compact-content-heading">Team Roles and Responsibilities</h3>
<h4 class="compact-content-heading">Single Point of Contact (SPOC)</h4>
<p class="compact-content-paragraph">For every ERPNext implementation project, we assign a dedicated Single Point of Contact (SPOC) or Functional Lead to ensure <span class="handbook-highlight-blue">smooth coordination and clear communication</span> throughout the project. Your SPOC acts as the <span class="handbook-highlight-pink">primary contact between your team and our implementation team</span>, helping manage discussions, track project progress, monitor dependencies, schedule meetings, and handle priorities or escalations whenever required.</p>
<div class="handbook-spoc-diagram" aria-label="Single point of contact communication flow">
<div class="handbook-spoc-node">
<span>Your Team</span>
<p>Business users, owners, and client-side stakeholders</p>
</div>
<div class="handbook-spoc-arrow" aria-hidden="true">⇆</div>
<div class="handbook-spoc-node handbook-spoc-node-primary">
<span>SPOC / Functional Lead</span>
<p>Single point for coordination, priorities, and escalations</p>
</div>
<div class="handbook-spoc-arrow" aria-hidden="true">⇆</div>
<div class="handbook-spoc-node">
<span>Hybrowlabs Implementation Team</span>
<p>Functional, technical, QA, DevOps, and support specialists</p>
</div>
</div>
<p class="compact-content-paragraph">This structured communication approach helps avoid confusion, speeds up decision-making, and ensures your project moves forward efficiently and transparently.</p>
<h4 class="compact-content-heading">ERPNext implementation team roles</h4>
<p class="compact-content-paragraph"><span class="handbook-highlight-black">Depending on the project scope, your team may include:</span></p>
<ul class="handbook-onboarding-check-list">
<li>ERPNext Functional Lead</li>
<li>ERPNext Technical Developer Lead</li>
<li>DevOps and Deployment Engineer (if required)</li>
</ul>
<p class="compact-content-paragraph">Each team member plays a defined role in ensuring successful ERPNext implementation and support.</p>
<h3 class="compact-content-heading">Communication & Reporting Structure</h3>
<table class="handbook-service-table"><tbody>
<tr><th>#</th><th>Communication Method</th></tr>
<tr><td>01</td><td><p class="handbook-service-copy"><span class="handbook-service-name">Daily standups:</span> For Agile projects, we may conduct short daily standup meetings to review completed tasks, <span class="handbook-highlight-pink">discuss blockers</span>, <span class="handbook-highlight-blue">align priorities</span>, and track ongoing development activities. These quick check-ins help keep the project moving smoothly and ensure <span class="handbook-highlight-black">better coordination between teams</span>.</p></td></tr>
<tr><td>02</td><td><p class="handbook-service-copy"><span class="handbook-service-name">Weekly sync meetings:</span> For Waterfall projects, weekly sync meetings are conducted to review project progress, discuss pending tasks, <span class="handbook-highlight-blue">share completed deliverables</span>, address business concerns, and align on upcoming priorities. These meetings help ensure <span class="handbook-highlight-black">smooth communication</span> and <span class="handbook-highlight-pink">timely project execution</span>.</p></td></tr>
<tr><td>03</td><td><p class="handbook-service-copy"><span class="handbook-service-name">Status reporting:</span> Regular ERPNext project status reports are shared through these channels, and each report covers a <span class="handbook-highlight-blue">consistent set of information</span> for <span class="handbook-highlight-black">clear project visibility</span>.</p></td></tr>
</tbody></table>
<table><tbody>
<tr><th>Reporting channel</th><th>Status report content</th></tr>
<tr><td>Project management platforms</td><td>Completed tasks</td></tr>
<tr><td>Task tracking systems</td><td>Pending activities</td></tr>
<tr><td>Weekly review calls</td><td>Risks and blockers</td></tr>
<tr><td>Email updates and meeting notes</td><td>Timeline updates</td></tr>
<tr><td>Bug and issue status</td><td>Current issue state and next actions</td></tr>
</tbody></table>
<img class="handbook-wide-image" src="/files/communication-report-1.jpg" width="1025" height="652" alt="ERPNext communication report for project tracking" />
<img class="handbook-wide-image" src="/files/communication-report-2.jpg" width="1025" height="652" alt="ERPNext issue and bug tracking communication report" />
<h3 class="compact-content-heading">Issue and Bug Tracking Process</h3>
<p class="compact-content-paragraph">All ERPNext bugs, issues, and enhancement requests are tracked through a <span class="handbook-highlight-blue">centralised issue tracking system</span>. This structured process helps ensure faster resolution and better accountability. Each reported issue includes:</p>
<div class="handbook-issue-detail-list">
<div class="handbook-issue-detail-card"><strong>Priority level</strong><span>How urgent the issue is</span></div>
<div class="handbook-issue-detail-card"><strong>Issue description</strong><span>What's happening</span></div>
<div class="handbook-issue-detail-card"><strong>Screenshots or recordings</strong><span>Supporting evidence</span></div>
<div class="handbook-issue-detail-card"><strong>Assigned owner</strong><span>Who's responsible</span></div>
<div class="handbook-issue-detail-card"><strong>Resolution status</strong><span>Current state</span></div>
<div class="handbook-issue-detail-card"><strong>Expected closure timeline</strong><span>When it'll be resolved</span></div>
</div>
<img class="handbook-wide-image" src="/files/erpnext-bug-tracking.png" width="1025" height="652" alt="ERPNext bug tracking process overview" />
<h3 class="compact-content-heading">Change Request Process</h3>
<p class="compact-content-paragraph">Any requirement outside the approved project scope is managed through a <span class="handbook-highlight-black">formal Change Request (CR) process</span>. This maintains project transparency and scope control during ERPNext implementation.</p>
<div class="handbook-cr-rail">
<div class="handbook-cr-rail-step"><span class="handbook-cr-rail-dot">1</span><strong>Requirement analysis</strong><p>Understand what is changing and why.</p></div>
<div class="handbook-cr-rail-step"><span class="handbook-cr-rail-dot">2</span><strong>Effort estimation</strong><p>Estimate the work and delivery impact.</p></div>
<div class="handbook-cr-rail-step"><span class="handbook-cr-rail-dot">3</span><strong>Timeline impact</strong><p>Assess how the change affects schedule.</p></div>
<div class="handbook-cr-rail-step"><span class="handbook-cr-rail-dot">4</span><strong>Cost evaluation</strong><p>Share cost impact, if applicable.</p></div>
<div class="handbook-cr-rail-step"><span class="handbook-cr-rail-dot">5</span><strong>Customer approval</strong><p>Approve before implementation begins.</p></div>
</div>
<img class="handbook-wide-image" src="/files/project-transparency.png" width="1025" height="652" alt="ERPNext project transparency and scope control overview" />
<h3 class="compact-content-heading">User Acceptance Testing</h3>
<p class="compact-content-paragraph">UAT is conducted once the key ERPNext modules, workflows, and features are ready for validation. During this phase, we define clear <span class="handbook-highlight-blue">test scenarios and acceptance criteria</span> based on the approved business requirements and process flows.</p>
<p class="compact-content-paragraph">Client users are encouraged to test <span class="handbook-highlight-pink">real-life business workflows</span> in the UAT environment to ensure the system functions as expected. Any bugs, issues, or feedback identified during testing are logged through the issue tracking process and resolved by our implementation team.</p>
<p class="compact-content-paragraph">Once all critical feedback is addressed and the system is validated successfully, the customer provides <span class="handbook-highlight-black">final UAT sign-off</span>, confirming that the implementation is ready for go-live and production usage.</p>
<img class="handbook-wide-image" src="/files/UAT-Acceptance-criteria.png" width="1025" height="652" alt="UAT acceptance criteria and ERPNext sign-off process" />
<h3 class="compact-content-heading">Go-Live Process</h3>
<p class="compact-content-paragraph">Before the system goes live, we carefully prepare and validate everything to ensure a <span class="handbook-highlight-blue">smooth transition from testing to actual business usage</span>:</p>
<ul class="handbook-onboarding-check-list">
<li>Final UAT verification</li>
<li>User training sessions</li>
<li>Data validation and migration checks</li>
<li>Backup planning</li>
<li>A complete go-live readiness review with all stakeholders</li>
</ul>
<p class="compact-content-paragraph">Our team works closely with your users to make sure they are comfortable with the system, <span class="handbook-highlight-pink">key workflows</span> are tested properly, and <span class="handbook-highlight-blue">critical business data</span> is migrated accurately before deployment.</p>
<p class="compact-content-paragraph">During the go-live phase, our implementation team remains actively involved to provide <span class="handbook-highlight-pink">deployment support</span>, monitor critical issues, and assist users with any immediate concerns or questions. We closely track system performance and ensure quick resolution of any <span class="handbook-highlight-pink">high-priority issues</span> that may arise during the initial usage period.</p>
<div class="handbook-onboarding-kickoff-summary">
<div class="handbook-onboarding-kickoff-summary-card">
<strong>Outcome</strong>
<p>This structured go-live support process helps minimise disruptions, improve user confidence, and ensure a smooth and successful transition to the live production environment.</p>
</div>
</div>
<img class="handbook-wide-image" src="/files/Go-Live-checklist.png" width="1025" height="652" alt="ERPNext go-live checklist and production readiness" />
<h3 class="compact-content-heading">Frequently Asked Questions</h3>
<div class="handbook-faq-list">
<div class="handbook-faq-item"><button class="handbook-faq-question" type="button" aria-expanded="false"><span>Which delivery model is right for my business?</span><span class="handbook-faq-chevron" aria-hidden="true"></span></button><div class="handbook-faq-answer"><p>First-time clients or low-trust outsourcing setups usually fit Waterfall. Businesses with evolving workflows and fast-paced growth usually fit Agile.</p></div></div>
<div class="handbook-faq-item"><button class="handbook-faq-question" type="button" aria-expanded="false"><span>How often will I see progress?</span><span class="handbook-faq-chevron" aria-hidden="true"></span></button><div class="handbook-faq-answer"><p>Agile projects get sprint demos and progress updates every two weeks. Waterfall projects are reviewed in weekly sync meetings, with reports shared through project channels.</p></div></div>
<div class="handbook-faq-item"><button class="handbook-faq-question" type="button" aria-expanded="false"><span>What happens if requirements change mid-project?</span><span class="handbook-faq-chevron" aria-hidden="true"></span></button><div class="handbook-faq-answer"><p>Anything outside approved scope goes through the Change Request process: analysis, effort estimate, timeline impact, cost evaluation where needed, and approval before implementation.</p></div></div>
<div class="handbook-faq-item"><button class="handbook-faq-question" type="button" aria-expanded="false"><span>Who is my main point of contact?</span><span class="handbook-faq-chevron" aria-hidden="true"></span></button><div class="handbook-faq-answer"><p>Every project has a dedicated SPOC / Functional Lead who coordinates between your team and ours, tracks progress, monitors dependencies, and handles escalations.</p></div></div>
<div class="handbook-faq-item"><button class="handbook-faq-question" type="button" aria-expanded="false"><span>What support do we get during go-live?</span><span class="handbook-faq-chevron" aria-hidden="true"></span></button><div class="handbook-faq-answer"><p>During go-live we provide deployment support, monitor critical issues, track performance, and resolve high-priority issues quickly during the initial usage period.</p></div></div>
</div>