You absolutely can use Agile for post-implementation support, and in fact, many teams find it very effective for managing ongoing support, enhancement, and optimization after an ERP or software system goes live.
Here is how and why
Why Agile Works for Post-Implementation Support
After go-live, users often identify:
- Minor bugs or configuration issues
- New requirements or enhancement requests
- Process improvements or training needs
Agile is iterative and flexible approach helps prioritize and deliver these changes quickly in short, controlled cycles (sprints), rather than waiting for a large periodic update.
How to Apply Agile in Support
| Area | Agile Practice | Example |
| Issue Intake | Use a product backlog to track and prioritize tickets (bugs, change requests, improvements). | Log tickets in Azure DevOps or Jira, with business impact and priority. |
| Prioritization | The Product Owner (or support lead) works with stakeholders to decide what goes into each sprint. | Fix critical bugs first, then enhancements. |
| Work Planning | Use sprints (1–2 weeks) for delivering small batches of fixes or improvements. | Sprint 1: Resolve top 5 finance bugs; Sprint 2: Add new approval workflow. |
| Communication | Conduct daily stand-ups (short check-ins) to monitor progress. | “Yesterday I resolved X; today I’m testing Y.” |
| Continuous Improvement | Hold retrospectives after each sprint to identify process improvements. | “We need clearer acceptance criteria from users.” |
Agile Roles in a Support Context
| Role | Responsibility |
| Product Owner | Prioritizes and defines support items. |
| Scrum Master / Support Lead | Facilitates sprint meetings and removes blockers. |
| Support Team (Consultants/Developers) | Implements fixes and enhancements. |
| Users / Stakeholders | Provide feedback and acceptance testing. |
Benefits
Faster turnaround for fixes and improvements
Transparent prioritization and progress tracking
Continuous feedback loop with users
Easier workload management for the support team
When Agile Might Need Adjustment
- For critical incidents (system down), you’ll still need an incident management process outside of normal sprints.
- If your organization prefers a ticket-based SLA model, Agile can complement it (e.g., use Kanban for ongoing flow instead of strict sprints).
Tip
Many post-implementation teams use Agile + ITIL hybrid,
- Agile for continuous improvement and enhancements
- ITIL (or a helpdesk model) for incident management and SLAs
Which Agile tool should I use for post implementation support?
There are several Agile / ITSM tools that work well for post‐implementation support.
The best choice depends on what you already have in place, your team size, budget, and how much you need to integrate with other systems.
Key criteria to consider
Before choosing a tool, think through:
| Feature | Why it matters for support / post‐implementation |
| Ticket / issue tracking + SLAs | You’ll need to manage incidents, prioritize, escalate, and measure response/resolution times. |
| Backlog / change request tracking | Not all tickets are incidents; many are enhancements or bugs , you’ll want to backlog them, groom & plan them. |
| Workflow customisation | Different ticket types (incidents, support request, bug, enhancement) may follow different workflows. |
| Integration with existing systems | E.g. linking to your development tools, version control, monitoring, possibly ERP or BC (if using Business Central). |
| Dashboards & reporting | To track metrics (volume, age, types, SLA compliance, velocity of enhancements, etc.). |
| User access & permissions | Support teams, developers, business stakeholders, maybe external users. |
| Ease of use / minimal overhead | In support, you want to be quick; tool complexity slows you down. |
| Cost & scalability | Number of users, users who only view vs. act; cloud vs. on-premise; licensing. |
Top tools & how they compare
Here are some of the strong contenders, with what they offer in a post-implementation support use case.
| Tool | Strengths for support / post-go-live | Trade-offs / Weaknesses |
| Jira Software + Jira Service Management (Atlassian) | Very popular. Powerful backlog, sprints/kanban. Jira SM adds good incident & request management, SLAs, integration with Confluence for KB. Lots of plugins. Good for teams already familiar with Atlassian. | Can get expensive with many users or many add-ons. Setup/customization may take time. Over-customizing can lead to complexity. |
| Azure DevOps | Strong if your dev team is already using Microsoft stack. Integrated code, pipelines, board/backlog. You can track bugs and enhancements well. | Less strong on formal SLA/ticketing vs classic ITSM tools. Can require extra work to integrate with a support ticket system. Might not be the best “help desk” experience for non-dev users. |
| ServiceNow | Very strong for enterprise support & ITSM + Agile hybrid. If you need unified backlog across incidents/problems/changes/enhancements, ServiceNow’s Agile / DevOps / Unified Backlog features are good. | More costly. More overhead. Steeper learning curve. Heavier config / admin work. If your support volume is modest, may be overkill. |
| Taiga | Open source, simpler, more lightweight. Good if you want Kanban/sprint boards without heavy cost. | Not as feature-rich for enterprise support, or for linking deeply into operations / monitoring / SLAs. Fewer integrations/out-of-the-box enterprise features. |
| ClickUp / Monday / Trello etc. | Very easy to use, good for smaller teams or lighter change/enhancement/backlog management. Visual boards, flexible workflows. | Less strong for formal ITSM / SLA / large scale support. Reporting & integration may be weaker. If many concurrent tickets, complexity increases. |
Suggested tools based on common scenarios
Here are my suggestions depending on your context:
| Scenario | Tool I’d Recommend |
| You’re a mid-to-large org, already using Atlassian products, want robust support + enhancements + KB + good metrics | Jira + Jira Service Management |
| You’re using Microsoft stack (Azure DevOps, .NET, maybe Office / Azure), want dev/support integration, want minimal tool proliferation | Azure DevOps + possibly augment with a light help desk or integrate with ticketing tool for incidents |
| You need enterprise ITSM, lots of integrations, large support load, want unified management of incidents, changes, enhancements, maybe compliance, etc. | ServiceNow |
| You’re a small team, lower budget, want simple backlog + ticket tracking, want quick wins | ClickUp or Trello or Taiga |
| Hybrid: you need ITSM for incidents/SLA + Agile for enhancements; maybe mix of tools or integrated suite | Evaluate Jira + JSM, or ServiceNow Agile + ServiceNow ITSM so you can get both in one system |
Can you compare three tools side-by-side with cost estimates for a team of 10 people?
Here is a side-by-side comparison of Jira Service Management (JSM) vs Azure DevOps vs ServiceNow for a scenario of ~10‐user support / post-implementation team.
Tools compared
| Tool | Best suited for | Key features helpful in post-implementation support |
| Jira + Jira Service Management | When your team wants a strong help-desk + request/incidents + change management + backlog + you prefer Atlassian ecosystem. | SLA management, portals, incident/problem/change tracking, workflow automation, dashboards. |
| Azure DevOps | If your development team already uses Microsoft tools, want tight integration of support tickets/bugs with backlog and dev work. Less of a traditional ticketing/help desk portal. | Boards, repos, pipelines, work items, ability to link fixes/enhancements directly with code, test plans. |
| ServiceNow | Large scale, multiple modules, enterprise features, complex workflows, many integrations, possibly strong compliance/regulatory requirements. | Full ITSM suite, ITOM, advanced analytics, large-scale automation, enterprise SLAs, CMDB etc. |
Cost comparison for ~10-user scenario
Here are estimates for a small post-implementation setup with ~10 active users (these would be the people acting on tickets / fulfilling / dev/support roles). Note: requester users (people only submitting tickets) often are free or low-cost in many tools; I’m focusing on “active agents/fulfillers”.
| Tool | License / Subscription Cost | Setup / Implementation / One-Time Costs | Likely Ongoing & Hidden Costs |
| Jira Service Management | – Standard plan: ~$19.04 per agent/month. For 10 agents: ~ $190-200/month. Premium is ~$47.82 per agent/month. Free plan exists (up to 3 agents) but too limited for 10. | Implementation cost is generally modest compared to ServiceNow. Might include setup of request types/portals, workflows, integration with other tools, perhaps training. Could be $5,000-$20,000 depending on scope. | Add-on costs (e.g. assets, configuration management), storage, premium support, possible cost of apps/plugins, training. Also account for scaling: price per agent stays same but total cost grows. Maintenance of processes & workflows can add admin overhead. |
| Azure DevOps | – Basic users: first 5 free, then $6/user/month for more. For 10 users: you’d pay for 5 extra beyond free, so ~$30/month just for basic access. If you need test management, Basic + Test Plans is $52/user/month. | Implementation cost could be low if you’re mostly using out-of-box; configuring Boards, linking bug/increment workflows, setting up pipelines etc. Perhaps $3,000-$15,000, depending on integrations and customizations. | If you need more parallel pipelines, more build agents, more storage/artifacts use, more advanced test planning, those add costs. Also, integration with help-desk if you want a portal vs dev ticket workflow. Support costs if you need premium support. |
| ServiceNow | Subscription/licensing is much higher. Rough benchmark for ITSM fulfiller user is ~$90-$150 per user/month depending on contract, module, size. For 10 users: expect $900-$1,500+/month just for licensing (for basic ITSM) without advanced modules. | Setup/implementation tends to be substantial: tooling, workflows, training, maybe data migration, setting up CMDB, integrations. For SMBs: $20,000-$50,000+ often. For larger or complex needs, much more. | Modules cost extra (if you want change-management, operations, ITOM etc.). High admin overhead. Customization, integrations, training, support services can add significantly. Also possibly minimum spend contracts. Hidden user types/licensing roles may complicate cost. |
Example: 3 Scenarios & Estimated Total Cost (1st Year)
To help you see the big picture, here are 3 possible small team scenarios (10 users) and rough 1st-year cost (licensing + setup + some cushion for hidden items).
These are estimates; your actual will vary.
| Scenario | Tool | Year-1 Estimated Cost | Break-down |
| Low complexity / lightweight support | Azure DevOps | ~$6/user × (10-5 free users) = ~$30/mo → $360/year + maybe $5,000 for setup/integrations/training & some buffer → **$6,000-$8,000** | You keep things simple: basic work item tracking, perhaps a simple portal or incoming email mapping, no heavy modules. |
| Moderate complexity, need full help-desk + SLA + workflows | Jira Service Management Standard | 10 agents × $19.04/mo ≈ $2,300/year + setup cost say $10,000 + plugins/training/support buffer (say $2,000) → **$14,000-$20,000/year** | Enough to support a decent support process; some custom workflows, maybe knowledge base, maybe asset management. |
| High complexity, enterprise grade | ServiceNow | Licensing 10 users at $100/month = $12,000/year + setup/integration/customization $30,000-$50,000 + annual training/support etc (say $5-10,000) → ~$50,000-$75,000+ for year-1 | Good if you’re expecting growth, needing enterprise features, lots of integrations, etc. |
What to watch out for / what influences cost most
- User roles/types: Active agents (fulfillers) cost more; people who only view or approve may be cheaper or even free, depending on the tool. Choosing the right types matters.
- Modules / functional scope: e.g. change management, asset management, monitoring, knowledge base, integrations, test plans, etc. The more you add, the more complexity and cost.
- Integrations: If you need to tie into monitoring tools, ERP, IAM, email systems, etc., that can add implementation time and possibly licensing.
- Storage & data volume: If ticket history, attachments, logs grow, you may need more storage or pay for add-ons.
- Support & SLA requirements: If you need 24/7, faster response times, or enterprise support, expect higher subscription fees.
- Customization & administration: Who will maintain workflows, update the system, train new users? If this is done by an external partner, it costs; if in-house, you still need staff time.
- Minimum contract sizes / annual commitments: Tools like ServiceNow often expect minimum spends. Discounts are often negotiated.
Can you create a sample Agile support framework tailored specifically for Dynamics 365 Business Central post-implementation support.
Here is a sample Agile support framework tailored specifically for Dynamics 365 Business Central post-implementation support.
Agile Support Framework Overview
After go-live, your goal is to manage:
- Incidents (bugs, errors, data issues)
- Service Requests (user access, configuration help)
- Enhancements (new fields, reports, or process improvements)
An Agile framework organizes all this into manageable sprints, ensuring continuous improvement without disrupting daily operations.
1. Structure of the Support Model
| Layer | Description | Agile Tool Element |
| Ticket Intake | Users log issues or requests via a portal or email. | Jira Service Management / Azure DevOps Work Items |
| Triage & Prioritization | Support lead classifies (Incident, Service Request, Enhancement) and prioritizes by impact. | Backlog Grooming |
| Sprint Planning | Every 2–3 weeks, the team reviews the backlog and selects top-priority items for the sprint. | Sprint Planning Meeting |
| Execution | The team works on fixes/enhancements during the sprint. Urgent issues may bypass the sprint via a “Hotfix lane.” | Active Sprint Board |
| Testing & Review | Fixes go to a sandbox/UAT for user sign-off. | Definition of Done (DoD) Checklist |
| Deployment | Approved changes deployed to production following change management controls. | Change Request Workflow |
| Retrospective | Team reflects on what went well, what didn’t, and improves processes. | Sprint Retrospective |
2. Sample Sprint Board Setup
| Column | Description |
| Backlog | All new issues and requests (unprioritized). |
| Selected for Sprint | Items chosen for the current sprint. |
| In Progress | Assigned and actively being worked on. |
| In Testing | Awaiting or undergoing UAT validation. |
| Ready for Deployment | Passed testing; queued for release. |
| Done | Deployed and validated in production. |
(You can use Kanban instead of Scrum if you have continuous incoming tickets.)
3. Example Roles
| Role | Responsibilities |
| Product Owner / Support Lead | Prioritizes tickets, communicates with stakeholders, approves sprint content. |
| Scrum Master / Support Coordinator | Facilitates sprints, removes blockers, ensures Agile discipline. |
| Support Consultants / Developers | Analyze, configure, test, and deploy fixes/enhancements. |
| Key Users / Business SMEs | Validate fixes, provide feedback, and define acceptance criteria. |
4. Example Sprint Metrics
| Metric | Purpose |
| Ticket Resolution Time | Measure responsiveness and efficiency. |
| Customer Satisfaction (CSAT) | Gather user feedback post-resolution. |
| Velocity (Story Points Completed) | Track team throughput over time. |
| Defect Reopen Rate | Monitor quality of fixes and user acceptance. |
Tip: Combine Agile + ITIL
For Business Central support, the most effective setup is Agile + ITIL Hybrid:
- ITIL processes for incidents, SLAs, and change control
- Agile sprints for enhancements and process improvements
That balance keeps governance intact while staying flexible and fast-moving.