{"id":3152,"date":"2026-06-12T10:00:00","date_gmt":"2026-06-12T10:00:00","guid":{"rendered":"https:\/\/aaxonix.com\/resources\/?p=3152"},"modified":"2026-04-17T12:43:24","modified_gmt":"2026-04-17T12:43:24","slug":"zoho-sprints-agile-guide","status":"publish","type":"post","link":"https:\/\/aaxonix.com\/resources\/zoho-sprints-agile-guide\/","title":{"rendered":"Zoho Sprints: Complete Agile Project Management Guide for Software and Product Teams"},"content":{"rendered":"<style>\n.aax-post{font-family:'Poppins',sans-serif;color:#1a2332;max-width:820px;margin:0 auto;line-height:1.75}\n.aax-post h2{font-size:1.55rem;font-weight:600;margin:2.5rem 0 .9rem;color:#0a1628}\n.aax-post h3{font-size:1.15rem;font-weight:600;margin:1.8rem 0 .6rem;color:#1a2332}\n.aax-post p{margin:0 0 1.1rem}\n.aax-post ul,.aax-post ol{margin:0 0 1.1rem;padding-left:1.5rem}\n.aax-post li{margin-bottom:.45rem}\n.aax-post table{width:100%;border-collapse:collapse;margin:1.5rem 0;font-size:.93rem}\n.aax-post th{background:#0a1628;color:#fff;padding:.6rem 1rem;text-align:left}\n.aax-post td{padding:.55rem 1rem;border-bottom:1px solid #e8edf4}\n.aax-post tr:nth-child(even) td{background:#f5f7fb}\n.aax-post .faq-section{background:#f5f7fb;border-radius:10px;padding:1.8rem 2rem;margin:2.5rem 0}\n.aax-post .faq-item{margin-bottom:1.2rem;border-bottom:1px solid #e0e6ef;padding-bottom:1.2rem}\n.aax-post .faq-item:last-child{border-bottom:none;margin-bottom:0;padding-bottom:0}\n.aax-post .faq-question{font-weight:600;color:#0a1628;margin-bottom:.5rem}\n.aax-post .faq-answer{color:#3a4a5c;line-height:1.65}\n.aax-post .aax-cta{background:linear-gradient(135deg,#0a1628 0%,#1a3a5c 100%);border-radius:12px;padding:1.8rem 2rem;margin:2.5rem 0;text-align:center}\n.aax-post .aax-cta p{color:#e8edf4;margin:0 0 1.2rem;font-size:1.05rem}\n.aax-post .aax-cta a{display:inline-block;background:#fff;color:#0a1628;font-weight:600;padding:.65rem 1.6rem;border-radius:6px;text-decoration:none;font-size:.95rem}\n<\/style><div class=\"sp-toc-wrap\"><nav class=\"sp-blog-toc\" id=\"spBlogToc\" style=\"display:none\"><h4><svg width=\"14\" height=\"14\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><line x1=\"8\" y1=\"6\" x2=\"21\" y2=\"6\"\/><line x1=\"8\" y1=\"12\" x2=\"21\" y2=\"12\"\/><line x1=\"8\" y1=\"18\" x2=\"21\" y2=\"18\"\/><line x1=\"3\" y1=\"6\" x2=\"3.01\" y2=\"6\"\/><line x1=\"3\" y1=\"12\" x2=\"3.01\" y2=\"12\"\/><line x1=\"3\" y1=\"18\" x2=\"3.01\" y2=\"18\"\/><\/svg> On this page<\/h4><ol class=\"sp-toc-list\" id=\"spTocList\"><\/ol><\/nav><\/div>\n<div class=\"aax-post\">\n\n<p>Software and product teams that have outgrown generic task boards often find themselves caught between tools that are either too simple or too heavyweight for iterative development. Zoho Sprints occupies a distinct space in the Zoho ecosystem: a dedicated agile project management platform built specifically for scrum teams running time-boxed sprints, managing backlogs, and measuring velocity over time. This guide walks through every core capability, from initial backlog setup to post-sprint retrospectives, so your team can get the most out of the platform.<\/p>\n\n\n<figure style=\"margin:36px 0;text-align:center;line-height:0;\"><img decoding=\"async\" src=\"https:\/\/aaxonix.com\/resources\/wp-content\/uploads\/2026\/04\/inline_zoho-sprints-agile-guide_1.jpg\" alt=\"Two business professionals brainstorming and planning software development with a whiteboard in an office.\" style=\"width:100%;max-width:820px;height:auto;border-radius:10px;box-shadow:0 4px 20px rgba(10,22,40,.13);\" loading=\"lazy\" \/><\/figure>\n<h2>Zoho Sprints vs Zoho Projects: Understanding the Difference<\/h2>\n\n<p>Many teams land on Zoho Sprints after using <a href=\"https:\/\/aaxonix.com\/resources\/zoho-projects-management-guide\/\" class=\"sp-content-link\">Zoho Projects for broader project management<\/a> and finding that its waterfall-friendly task structures do not map cleanly onto sprints, story points, and backlog grooming. The two products serve genuinely different workflows.<\/p>\n\n<table>\n  <thead>\n    <tr>\n      <th>Feature<\/th>\n      <th>Zoho Projects<\/th>\n      <th>Zoho Sprints<\/th>\n    <\/tr>\n  <\/thead>\n  <tbody>\n    <tr>\n      <td>Work item model<\/td>\n      <td>Tasks and subtasks<\/td>\n      <td>Epics, user stories, tasks<\/td>\n    <\/tr>\n    <tr>\n      <td>Planning model<\/td>\n      <td>Milestones and Gantt<\/td>\n      <td>Sprint backlog and sprint board<\/td>\n    <\/tr>\n    <tr>\n      <td>Estimation<\/td>\n      <td>Hours-based<\/td>\n      <td>Story points + hours<\/td>\n    <\/tr>\n    <tr>\n      <td>Progress tracking<\/td>\n      <td>Percent complete<\/td>\n      <td>Burndown chart, velocity chart<\/td>\n    <\/tr>\n    <tr>\n      <td>Best for<\/td>\n      <td>Agencies, PMO, client delivery<\/td>\n      <td>Software dev, product teams<\/td>\n    <\/tr>\n  <\/tbody>\n<\/table>\n\n<p>If your team plans work in two-week cycles, holds sprint reviews, and tracks velocity across sprints, Zoho Sprints will fit your process far better than a general-purpose project tool.<\/p>\n\n<h2>Setting Up Your Project and Backlog<\/h2>\n\n<p>Every Zoho Sprints project starts with a backlog. The backlog is the single ordered list of all work your team might do, expressed as epics and user stories. Getting this structure right before you run your first sprint pays dividends throughout the product lifecycle.<\/p>\n\n<h3>Epics and User Stories<\/h3>\n\n<p>An epic in Zoho Sprints represents a large body of work that spans multiple sprints, such as &#8220;User Authentication&#8221; or &#8220;Reporting Dashboard.&#8221; User stories sit beneath epics and follow the standard format: As a [user], I want to [action] so that [outcome].<\/p>\n\n<p>To create an epic, navigate to your project backlog, select &#8220;Add Epic,&#8221; and give it a title, description, and color label for visual grouping on the board. User stories can then be created directly in the backlog and linked to an epic via the epic field on the story detail panel.<\/p>\n\n<h3>Story Points and Estimation<\/h3>\n\n<p>Story points measure relative effort rather than calendar time. Zoho Sprints supports Fibonacci-sequence estimation (1, 2, 3, 5, 8, 13) by default, which you can customize per project. Teams typically estimate during a backlog refinement session: the team looks at each story, compares it to a reference story they have already completed, and assigns a point value.<\/p>\n\n<p>To set story points on a backlog item, open the story detail, locate the Story Points field in the right panel, and enter the value. The backlog view shows a running total of points so you can gauge sprint capacity before planning begins.<\/p>\n\n<h3>Acceptance Criteria and Definitions<\/h3>\n\n<p>Each user story in Zoho Sprints has a description field that works well for acceptance criteria. Structuring criteria as a checklist inside the description lets developers and QA verify completion conditions without leaving the item. Clear acceptance criteria reduce back-and-forth during sprint reviews and lower the rate of stories returning to the board after &#8220;completion.&#8221;<\/p>\n\n<h2>Sprint Planning: Creating and Loading Sprints<\/h2>\n\n<p>With a groomed backlog in place, sprint planning is the process of selecting which stories your team commits to delivering in the next sprint cycle, typically one to four weeks.<\/p>\n\n<h3>Creating a Sprint<\/h3>\n\n<p>From the Backlog view, click &#8220;Create Sprint&#8221; at the top of the sprint section. Give the sprint a name (e.g., &#8220;Sprint 14&#8221;), set start and end dates, and add a sprint goal &#8212; a one-sentence statement of what the team aims to achieve. The sprint goal appears prominently on the sprint board, keeping the team focused on outcome over output throughout the cycle.<\/p>\n\n<h3>Capacity Planning<\/h3>\n\n<p>Before dragging stories into the sprint, check team capacity. In Zoho Sprints, each team member has an availability setting (hours per day and working days). The sprint capacity panel shows total available hours and the story points already loaded against average velocity. A practical guideline: load stories totaling 80-90% of your team&#8217;s average velocity to leave buffer for unplanned work and interruptions that appear in every sprint.<\/p>\n\n<p>Drag stories from the backlog into the sprint panel. As you add items, the point total updates in real time. When the sprint is ready, click &#8220;Start Sprint&#8221; to activate the board and begin tracking progress against the burndown.<\/p>\n\n<h3>The Sprint Board<\/h3>\n\n<p>The sprint board is a Kanban-style view showing all stories in the active sprint across customizable columns &#8212; typically To Do, In Progress, In Review, and Done. Team members move cards as work advances. Each card shows story points, assignee avatar, priority indicator, and linked sub-tasks. Clicking a card opens the full story detail with comments, attachments, time logs, and activity history for full context without switching tools.<\/p>\n\n\n<figure style=\"margin:36px 0;text-align:center;line-height:0;\"><img decoding=\"async\" src=\"https:\/\/aaxonix.com\/resources\/wp-content\/uploads\/2026\/04\/inline_zoho-sprints-agile-guide_2.jpg\" alt=\"Overhead view of project management documents and charts on a desk with a pencil.\" style=\"width:100%;max-width:820px;height:auto;border-radius:10px;box-shadow:0 4px 20px rgba(10,22,40,.13);\" loading=\"lazy\" \/><\/figure>\n<h2>Burndown Charts and Sprint Progress Tracking<\/h2>\n\n<p>The burndown chart is the primary real-time indicator of sprint health. Zoho Sprints generates it automatically from story point completions, updating each time a story moves to Done.<\/p>\n\n<h3>Reading the Burndown<\/h3>\n\n<p>The chart plots two lines: the ideal burndown (a straight diagonal from total sprint points to zero) and the actual burndown (the real completion curve). Common patterns and what they signal:<\/p>\n\n<ul>\n  <li><strong>Actual above ideal (slow burn):<\/strong> The team is behind; stories are taking longer than estimated or blockers are slowing progress.<\/li>\n  <li><strong>Actual below ideal (fast burn):<\/strong> Work is completing faster than planned; consider pulling additional backlog items mid-sprint if the team has capacity.<\/li>\n  <li><strong>Flat line mid-sprint:<\/strong> Work has stalled, often indicating blocked stories or dependencies waiting on another team.<\/li>\n  <li><strong>Step-shaped drops:<\/strong> Stories are completing in batches rather than continuously, which may indicate late integration or QA bottlenecks near sprint end.<\/li>\n<\/ul>\n\n<p>Zoho Sprints also provides an <strong>Epic Burndown<\/strong> chart that shows progress across an entire epic spanning multiple sprints, useful for communicating roadmap progress to product stakeholders and leadership.<\/p>\n\n<h3>Sprint Reports<\/h3>\n\n<p>Beyond the burndown, Zoho Sprints generates several sprint-end reports automatically:<\/p>\n\n<ul>\n  <li><strong>Sprint Summary:<\/strong> Completed vs. incomplete stories, total points delivered, and cycle time per story.<\/li>\n  <li><strong>Unplanned Work Report:<\/strong> Stories added to the sprint after it started, which helps calibrate planning accuracy over time and surfaces recurring sources of disruption.<\/li>\n  <li><strong>Time Tracking Report:<\/strong> Logged hours per team member against estimated hours, useful for identifying under- or over-commitment patterns.<\/li>\n<\/ul>\n\n<h2>Velocity Tracking and Team Performance<\/h2>\n\n<p>Velocity is the average story points a team completes per sprint, measured over a rolling window of recent sprints. It is the foundation of reliable release planning because it tells you how much work the team can realistically accomplish in a given period.<\/p>\n\n<h3>The Velocity Chart<\/h3>\n\n<p>Zoho Sprints generates a velocity chart that plots committed vs. completed points for each historical sprint as a bar chart. Key patterns to watch:<\/p>\n\n<ul>\n  <li><strong>Consistent gap between committed and completed:<\/strong> The team is regularly over-committing; reduce sprint load by 10-15% and monitor for improvement.<\/li>\n  <li><strong>High variance sprint-to-sprint:<\/strong> Story sizing is inconsistent; invest more time in backlog refinement and relative estimation calibration.<\/li>\n  <li><strong>Steady upward trend in completed points:<\/strong> The team is improving throughput, which can indicate better tooling, clearer requirements, or reduced technical debt.<\/li>\n<\/ul>\n\n<p>Use the velocity average shown in the chart during sprint planning to set a realistic commitment ceiling. If the last four sprints averaged 42 points completed, loading 44-46 points in the next sprint is a reasonable target that stretches the team without setting them up to miss.<\/p>\n\n<h3>Cumulative Flow Diagram<\/h3>\n\n<p>The cumulative flow diagram (CFD) in Zoho Sprints visualizes the number of stories in each workflow state over time as stacked bands. A widening &#8220;In Progress&#8221; band indicates work in progress is accumulating without completing, often a sign that the team needs to focus on finishing existing work before starting new items. Narrowing bands in Done relative to To Do suggests delivery is accelerating, which is the goal.<\/p>\n\n<h2>Zoho Sprints Integrations for Development Teams<\/h2>\n\n<p>Zoho Sprints connects natively with several tools that development and product teams already use, reducing context-switching and keeping sprint data current without manual updates.<\/p>\n\n<h3>GitHub and Bitbucket Integration<\/h3>\n\n<p>Connecting Zoho Sprints to a code repository allows team members to link commits, branches, and pull requests directly to stories. When a developer commits with a story ID in the message (e.g., ZS-142 Fix login redirect), the commit automatically appears in the story&#8217;s detail view. This creates traceability from user story through code change, which is valuable during sprint reviews and for post-release debugging. Teams using GitHub alongside their sprint workflow may also benefit from the <a href=\"https:\/\/aaxonix.com\/resources\/zoho-projects-github-integration\/\" class=\"sp-content-link\">Zoho Projects GitHub integration<\/a> if they manage client-facing deliverables alongside internal product sprints.<\/p>\n\n<h3>Zoho Cliq Integration<\/h3>\n\n<p>Zoho Sprints sends sprint event notifications to Zoho Cliq channels &#8212; sprint start, story completion, sprint end, and blocker flags. Teams that prefer keeping all communication in Zoho&#8217;s ecosystem benefit from these automated updates without needing a separate notification layer. For teams who also track cross-tool sprint activity, the setup approach for <a href=\"https:\/\/aaxonix.com\/resources\/zoho-cliq-jira-integration-sprint-tracking\/\" class=\"sp-content-link\">sprint tracking in Zoho Cliq<\/a> provides a useful reference for configuring filtered channel alerts by project or sprint.<\/p>\n\n<h3>Zoho Meeting and Retrospectives<\/h3>\n\n<p>Sprint ceremonies &#8212; planning, daily standups, reviews, and retrospectives &#8212; can be scheduled directly from Zoho Sprints using the integrated meeting scheduler. Retrospective notes entered in Zoho Sprints&#8217; built-in retrospective board (Start, Stop, Continue format) attach to the sprint record for future reference, building an institutional knowledge base that new team members can review when onboarding.<\/p>\n\n<h2>Configuring Workflows, Roles, and Permissions<\/h2>\n\n<p>Zoho Sprints allows project admins to customize the sprint board workflow states to match the team&#8217;s actual process. Adding states like &#8220;Ready for QA&#8221; or &#8220;Awaiting Deployment&#8221; between In Progress and Done improves signal fidelity on the board and in reports, making it easier to spot where work is accumulating.<\/p>\n\n<p>Role-based permissions control who can create sprints, modify backlog priority, and access reports. Common role configurations for product and software teams:<\/p>\n\n<table>\n  <thead>\n    <tr>\n      <th>Role<\/th>\n      <th>Typical Permissions<\/th>\n    <\/tr>\n  <\/thead>\n  <tbody>\n    <tr>\n      <td>Scrum Master<\/td>\n      <td>Create and close sprints, manage board columns, view all reports<\/td>\n    <\/tr>\n    <tr>\n      <td>Product Owner<\/td>\n      <td>Manage backlog priority, create and edit epics and stories<\/td>\n    <\/tr>\n    <tr>\n      <td>Developer<\/td>\n      <td>Update story status, log time, add comments and attachments<\/td>\n    <\/tr>\n    <tr>\n      <td>Stakeholder<\/td>\n      <td>View sprint board and reports (read-only access)<\/td>\n    <\/tr>\n  <\/tbody>\n<\/table>\n\n<h2>Best Practices for Running Effective Sprints<\/h2>\n\n<p>The platform handles the mechanics; the practices determine whether your team ships reliably. These habits make a consistent difference for teams running Zoho Sprints:<\/p>\n\n<ul>\n  <li><strong>Groom the backlog weekly.<\/strong> A 45-minute weekly refinement session keeps stories estimated, acceptance criteria current, and the top of the backlog ready to pull into the next sprint. Teams that skip refinement consistently struggle with accurate planning and mid-sprint scope changes.<\/li>\n  <li><strong>Set a sprint goal every sprint.<\/strong> The sprint goal field in Zoho Sprints is easy to skip, but it anchors daily standup conversations and gives the team a clear &#8220;done&#8221; definition beyond individual story completion.<\/li>\n  <li><strong>Use story points, not hours, for planning.<\/strong> Hour-based estimates create false precision and penalize slow days. Story points normalize effort relative to team capacity and improve planning accuracy over time as the team calibrates their estimation.<\/li>\n  <li><strong>Keep work in progress low.<\/strong> Limiting each team member to one or two in-progress stories at a time reduces context-switching and accelerates throughput. The CFD in Zoho Sprints reveals when WIP is creeping up before it becomes a sprint-end crisis.<\/li>\n  <li><strong>Run the retrospective before closing the sprint.<\/strong> Zoho Sprints links retrospective boards to active sprints. Closing the sprint first loses the association. Keep the sprint open until the retrospective is documented and action items are assigned.<\/li>\n  <li><strong>Review the unplanned work report after each sprint.<\/strong> Consistently high unplanned work signals either poor scope definition at planning or a team being pulled into reactive work that needs to be addressed at the team or organizational level.<\/li>\n<\/ul>\n\n<h2>Zoho Sprints Pricing and Getting Started<\/h2>\n\n<p>Zoho Sprints offers a free plan for up to five users with unlimited sprints and basic reports &#8212; enough for a small team to evaluate whether the platform fits their workflow before committing to a paid tier. Paid plans start at a per-user monthly fee and unlock advanced reports, cross-project boards, additional storage, and priority support.<\/p>\n\n<p>Organizations already invested in <a href=\"https:\/\/aaxonix.com\/services\/zoho\/\" class=\"sp-content-link\">Zoho&#8217;s product suite and services<\/a> benefit from native single sign-on, shared contacts, and unified billing. Zoho One subscribers get Zoho Sprints included alongside the broader application stack at no additional per-product cost. For teams evaluating the fit of Zoho Sprints within their existing toolchain, a structured implementation assessment identifies which configuration decisions matter most and which integrations will deliver the fastest return.<\/p>\n\n<div class=\"faq-section\">\n  <h2>Frequently Asked Questions<\/h2>\n\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">What is Zoho Sprints and how is it different from Zoho Projects?<\/p>\n    <p class=\"faq-answer\">Zoho Sprints is a dedicated agile project management tool built for scrum teams running iterative sprints. It uses epics, user stories, and story points as its core work model, and includes sprint boards, burndown charts, and velocity tracking. Zoho Projects is a broader project management platform better suited to milestone-based, waterfall, or agency-style delivery. The two products are complementary: Zoho Projects handles client deliverables and Gantt-based scheduling, while Zoho Sprints handles iterative software and product development cycles.<\/p>\n  <\/div>\n\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">How does story point estimation work in Zoho Sprints?<\/p>\n    <p class=\"faq-answer\">Story points in Zoho Sprints represent the relative effort of a user story compared to other stories the team has completed. The platform supports Fibonacci sequence values (1, 2, 3, 5, 8, 13) by default, though this can be customized. Teams assign points during backlog refinement by comparing each new story to reference stories. Over several sprints, the team&#8217;s average completed points per sprint becomes their velocity, which is used to plan future sprint capacity with increasing accuracy.<\/p>\n  <\/div>\n\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">Can Zoho Sprints connect to GitHub or other code repositories?<\/p>\n    <p class=\"faq-answer\">Yes. Zoho Sprints integrates with GitHub and Bitbucket. Developers can link commits, branches, and pull requests to stories by including the story ID in commit messages. These code events then appear in the story&#8217;s activity timeline, creating full traceability from backlog item to deployed code change without leaving the Zoho Sprints interface.<\/p>\n  <\/div>\n\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">Is there a free plan for Zoho Sprints?<\/p>\n    <p class=\"faq-answer\">Zoho Sprints offers a free tier for teams of up to five users with unlimited sprints, a product backlog, sprint board, and basic reporting. Paid plans unlock advanced reports including the velocity chart and cumulative flow diagram, cross-project boards, additional file storage, and priority customer support. Teams on Zoho One get Zoho Sprints included in their subscription at no additional per-product cost.<\/p>\n  <\/div>\n\n  <div class=\"faq-item\">\n    <p class=\"faq-question\">How do I track team velocity in Zoho Sprints?<\/p>\n    <p class=\"faq-answer\">Velocity is tracked automatically in the Velocity Chart under the Reports section. After completing at least two sprints, the chart displays committed vs. completed story points for each sprint as a bar chart alongside the rolling average. The rolling average is the recommended input for capacity planning in upcoming sprints. Consistent completion close to commitment, without large gaps either way, indicates well-calibrated estimation and reliable planning.<\/p>\n  <\/div>\n<\/div>\n\n<div class=\"aax-cta\">\n  <p>Aaxonix helps software and product teams configure Zoho Sprints from scratch: backlog structure, sprint workflows, GitHub integration, and velocity baselines so your team is running clean agile cycles within days, not weeks.<\/p>\n  <a href=\"https:\/\/aaxonix.com\/contact\/\">Book a free consultation<\/a>\n<\/div>\n\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Master Zoho Sprints: set up your backlog, run sprint planning, track burndown charts, and measure velocity. Complete guide for scrum and product teams.<\/p>\n","protected":false},"author":1,"featured_media":3145,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[826,829,828,827,825],"class_list":["post-3152","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-agile-project-management","tag-product-teams","tag-scrum-tools","tag-sprint-planning","tag-zoho-sprints"],"_links":{"self":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts\/3152","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/comments?post=3152"}],"version-history":[{"count":1,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts\/3152\/revisions"}],"predecessor-version":[{"id":3153,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/posts\/3152\/revisions\/3153"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/media\/3145"}],"wp:attachment":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/media?parent=3152"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/categories?post=3152"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/tags?post=3152"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}