# Quantify

> Quantify turns Jira board activity into automatic timesheets — re-align engineering with the business through capex/opex, R&D, and time-spent reporting, with no manual logging.

## Pages
- [About Quantify](https://www.quantifyhq.com/about): Quantify's mission is a new way to track digital work — Lean and Agile by design, with no manual time tracking. Proudly headquartered in Vancouver, Canada.
- [Best Agile Training and Certification](https://www.quantifyhq.com/agile-training-certification): An overview of the leading Agile certification providers and the credentials they offer — Scrum Alliance and more — to help you choose where to get certified.
- [Automatic Time-Tracking for Jira - Quantify](https://www.quantifyhq.com/automatic-time-tracking): Automatic time-tracking for Jira that fills timesheets from board activity — no manual logging. See time spent per user, status, issue, and epic across any workflow.
- [How a software company solved capex reporting challenges and increased visibility into actual work allocation](https://www.quantifyhq.com/case-study/sambasafety): How SambaSafety solved capex reporting and gained visibility into real work allocation — translating Agile story points into accurate, audit-ready time data with Quantify.
- [Contact](https://www.quantifyhq.com/contact): Get in touch with the Quantify team — tell us about your team and how you report on software development work. We read every message.
- [chakra-ui](https://www.quantifyhq.com/jesko-chakra-ui): chakra-ui is an accessible, themeable React component library with built-in theming and dark mode. Jesco Wüster is a contributor to the chakra-ui project.
- [Automatic work quantification for Jira - Quantify](https://www.quantifyhq.com/jira-integration): The Quantify app for Jira automatically quantifies work from board activity — no manual time tracking. Install to see time spent per user, status, issue, and epic.
- [Jira Time Spent Reporting](https://www.quantifyhq.com/jira-time-spent): Jira time spent reporting without manual work logging — see time by task, epic, user, and status to understand effort and workflow efficiency across your projects.
- [Kanban Community of Practice](https://www.quantifyhq.com/kanbancop): The Kanban Community of Practice — an online peer group hosted by Quantify where practitioners share delivery-performance metrics, practices, and experiments.
- [Partner Integrations - Quantify](https://www.quantifyhq.com/partners): Quantify integrates with the tools your teams already use — Atlassian Jira, GitHub Projects, and more across your Agile project management stack.
- [Time-tracking that works without wasting people's time - Quantify](https://www.quantifyhq.com/pricing): Quantify pricing — automatic Jira time-tracking from a free tier up, with more data retention, data sources, and reporting as your teams scale.
- [Privacy Policy](https://www.quantifyhq.com/privacy): Quantify's privacy policy — what personal data we collect, how we use and protect it, and the rights you have over your information.
- [Privacy Statement for Atlassian Products](https://www.quantifyhq.com/privacy-atlassian): Privacy statement for Quantify's apps on Atlassian — what Jira data we access (read-only), how it is processed, and how it is safeguarded.
- [Security](https://www.quantifyhq.com/security): How Quantify protects customer data — Cloud Security Alliance self-assessment, the Atlassian Cloud Security Program, and read-only access to your Jira data.
- [Service Level Agreement](https://www.quantifyhq.com/sla): Quantify's service level agreement — uptime commitments, support response targets, and the remedies available to customers.
- [Capitalization of software development costs](https://www.quantifyhq.com/software-capex): Capitalize software development costs in Jira — align GAAP CAPEX reporting with Agile by classifying dev work as capitalized or expensed, with no manual time logging.
- [SR&ED Time Sheets from Jira](https://www.quantifyhq.com/sred-time-sheets): Generate CRA-ready SR&ED timesheets from Jira ticket history — quantify eligible work without manual time tracking, and recover prior-year numbers from data you already have.
- [R&D Tax Credits - Quantify](https://www.quantifyhq.com/tax-credit-tracking): Track R&D expenditures from Jira to substantiate R&D tax credit claims — audit-ready timesheets and contemporaneous documentation, calculated without manual time tracking.
- [Terms of Service](https://www.quantifyhq.com/terms): The terms of service governing your use of Quantify's apps and website.
- [Sub-processors](https://www.quantifyhq.com/trust/sub-processors): The third-party sub-processors Quantify relies on to deliver its services, and the role each one plays in processing data.

## Blog
- [Agile Isn't Dead — It Just Grew Up](https://www.quantifyhq.com/blog/agile-isnt-dead-it-just-grew-up): The word "agile" has become persona non grata in many organizations — but what died wasn't agile, just a bloated, overly prescriptive version of it. The principles didn't fail; they grew up into business agility.
- [What ASU 2025-06 Means for Auditors](https://www.quantifyhq.com/blog/asu-2025-06-for-auditors): ASU 2025-06 trades rigid stages for judgment — capitalization now turns on a probability threshold, and auditors have to evaluate management's calls and the evidence behind them.
- [What ASU 2025-06 Means for CFOs and Controllers](https://www.quantifyhq.com/blog/asu-2025-06-for-cfos): ASU 2025-06 can lower capitalized software balances and shift expense earlier — with knock-on effects on EBITDA, debt covenants, disclosures, and the metrics your investors watch.
- [What ASU 2025-06 Means for SaaS Companies](https://www.quantifyhq.com/blog/asu-2025-06-for-saas-companies): SaaS development is internal-use software, so ASU 2025-06 hits it head-on — expect more early expensing on novel features, and a higher bar on documenting when capitalization starts.
- [What ASU 2025-06 Means for Startups](https://www.quantifyhq.com/blog/asu-2025-06-for-startups): Startups build unproven things, so ASU 2025-06's uncertainty test often defers capitalization — more early expensing, with effects on burn optics, diligence, and the R&D tax angle.
- [Compliance Risks from Manual Software Capitalization Cost Tracking](https://www.quantifyhq.com/blog/compliance-risks-from-manual-software-capitalization-cost-tracking): Plenty of companies still track software-capitalization costs by hand — and every spreadsheet error is a compliance exposure: fines, restatements, lost trust. Here's the case for automating it.
- [Cost Center vs Profit Center](https://www.quantifyhq.com/blog/cost-center-vs-profit-center): Cost centers manage expenses; profit centers own revenue and the costs behind it. Knowing the difference — and when to use each — is fundamental to how you structure financial accountability.
- [The Need for Financial Accountability in Software Development](https://www.quantifyhq.com/blog/financial-accountability-in-software-development): Financial accountability in software development means managing the money across a product's lifecycle — estimating, budgeting, allocating, and reporting — so funds are used efficiently and transparently.
- [How Security Debt is different from Technical Debt](https://www.quantifyhq.com/blog/how-security-debt-is-different-from-technical-debt): Technical debt slows you down; security debt can sink you. Both come from shortcuts — but security debt threatens data integrity, invites fines, and, as Equifax learned, can expose millions.
- [The Benefits of Using Kanban for Project Management](https://www.quantifyhq.com/blog/kanban-vs-project-management): Kanban brings flow, flexibility, and continuous improvement to project management — a sharp contrast to the linear plans and fixed deadlines of traditional methods. Here's why teams are adopting it.
- [Understanding the McKinsey Three Horizons Model: A Strategic Guide](https://www.quantifyhq.com/blog/mckinsey-three-horizons-model): The McKinsey Three Horizons Model is a framework for balancing growth across three time frames — the core business today, emerging bets, and long-term possibilities — so you fund the future out of the present instead of being blindsided by it.
- [Guide to Responsibility Centers in Managerial Accounting](https://www.quantifyhq.com/blog/responsibility-centers-accounting): Responsibility centers are organizational units that hold managers accountable for specific financial outcomes. They come in four types — cost, revenue, profit, and investment — each widening the scope of what a manager owns.
- [R&D Tax Credits for Internal Use Software](https://www.quantifyhq.com/blog/rnd-tax-credits-for-internal-use-software): R&D tax credits aren't just for breakthrough products — internal-use software you build to run your own business can qualify too. Here's how the credits work, who's eligible, and how to claim them.
- [Are you SredReady?](https://www.quantifyhq.com/blog/sredready): We've launched SredReady.ca, a dedicated resource for Canada's SR&ED program — the country's largest R&D tax incentive, worth up to a 35% refundable credit for small CCPCs. Here's what it covers.
- [What is a Cost Center? (with examples)](https://www.quantifyhq.com/blog/what-is-a-cost-center): A cost center is a department that incurs expenses but doesn't directly generate revenue. Understanding them is essential for financial planning and control — and for telling them apart from profit centers.
- [What is a Profit Center?](https://www.quantifyhq.com/blog/what-is-a-profit-center): A profit center is a segment responsible for generating revenue, evaluated on its profitability rather than just its costs. Here's how they work, how they differ from cost centers, and how to measure one.
- [What is an Investment Center?](https://www.quantifyhq.com/blog/what-is-an-investment-center): An investment center is responsible for profits and the capital decisions behind them, evaluated on return on investment. It's the third responsibility-center type — distinct from cost and profit centers.
- [What is DevFinOps?](https://www.quantifyhq.com/blog/what-is-devfinops): DevFinOps merges development, finance, and operations into one framework — making cost visible in the workflow so engineering decisions carry their financial weight, in real time.
- [Why Dependencies Kill Your Deadlines](https://www.quantifyhq.com/blog/why-dependencies-kill-your-deadlines): We suspected dependencies were the silent killer behind missed deadlines, so we put numbers on it across tens of thousands of real work items. The compounding is real — but it's sub-linear and organization-specific, not the coin-flip catastrophe you've heard about.

## Kanban
- [Blockers: Kanban Explained](https://www.quantifyhq.com/kanban/blockers): Kanban is a popular methodology for managing workflows and increasing efficiency, widely used in software development, manufacturing, and other industries. This article explains what blockers are, how they impact workflow, and strategies for managing them.
- [How to identify blockers in Kanban](https://www.quantifyhq.com/kanban/how-to-identify-blockers): Kanban emphasizes visualizing work and limiting work in progress to improve efficiency, but blockers can still slow down the workflow. This article explores how to identify blockers in Kanban and strategies for addressing them.
- [Kanban Cards Explained: How They Drive Workflow](https://www.quantifyhq.com/kanban/kanban-cards-explained): A card on a kanban board isn't just a sticky note with a task name scribbled on it. It's a self-contained information packet that tells anyone on the team exactly what needs to happen, who's responsible, and how urgent it is.
- [Remote Work: Achieving Work Life Balance with Personal Kanban](https://www.quantifyhq.com/kanban/remote-work-balance-personal-kanban): In an era where remote work has become the norm, the need for effective productivity tools is more crucial than ever. Personal Kanban is a visual management method that helps individuals manage their tasks and workflows efficiently, enabling remote workers to achieve a better work-life balance.
- [What is a Kanban Board? Your Visual Guide to Workflow Management](https://www.quantifyhq.com/kanban/what-is-a-kanban-board): Every team has a workflow, but most of it stays invisible — living in email threads, chat messages, and people's heads. A kanban board makes all of that visible in one place, and that visibility alone changes how teams operate.
- [What is Personal Kanban: A Comprehensive Guide](https://www.quantifyhq.com/kanban/what-is-personal-kanban): One method that has gained popularity is Personal Kanban, a visual approach to workflow management. This guide delves into the principles, benefits, and practical implementation of Personal Kanban for anyone looking to enhance their productivity.

## Software-capitalization
- [Capitalizing Software Development Costs in Agile](https://www.quantifyhq.com/software-capitalization/agile): How to capitalize software development costs in Agile — mapping sprints, epics, and Jira workflows to ASC 350-40 stages, with a worked example and an audit-ready approach that needs no manual timesheets.
- [Capitalizing AI and Machine Learning Development Costs](https://www.quantifyhq.com/software-capitalization/ai-development-costs): Whether AI and ML development costs are capitalized or expensed depends on what the AI is for and how it's delivered — and ASU 2025-06's uncertainty test hits novel AI work hard.
- [Applying ASU 2025-06: Mapping Capitalization to Your Backlog](https://www.quantifyhq.com/software-capitalization/applying-asu-2025-06): ASU 2025-06 ties software capitalization to funding, scope, and technical risk — events that live in your backlog, not your ledger. How to map the probable-to-complete threshold to epics, sprints, and spikes.
- [Capitalizing Software Costs for Apps Built on Platforms](https://www.quantifyhq.com/software-capitalization/apps-on-platforms): If you build apps or integrations on a platform — Atlassian, Salesforce, Shopify, ServiceNow — how you capitalize the development depends on whether you're building to sell or to run your own business.
- [ASU 2025-06: The New Internal-Use Software Capitalization Rules](https://www.quantifyhq.com/software-capitalization/asu-2025-06): ASU 2025-06 replaces the three-stage model for capitalizing internal-use software with a probable-to-complete threshold, effective FY2028. What changed, what it means for software teams, and how to prepare.
- [ASU 2025-06 Worked Examples: When Does Capitalization Start?](https://www.quantifyhq.com/software-capitalization/asu-2025-06-examples): ASU 2025-06's probable-to-complete threshold in three concrete scenarios — configuring an ERP, building a new app with shifting scope, and proving novel technology — showing exactly when capitalization begins and why.
- [ASU 2025-06 Transition Guide: How to Adopt the New Software Rules](https://www.quantifyhq.com/software-capitalization/asu-2025-06-transition): How to adopt ASU 2025-06 — the three transition methods (with a worked derecognition example), how to choose, early-adoption strategy, the new ASC 360-10 disclosures, and a readiness plan through FY2028.
- [Capitalize vs. Expense Software Costs — How to Decide](https://www.quantifyhq.com/software-capitalization/capitalize-vs-expense): A practical guide to deciding whether a software cost is capitalized or expensed — by what the work is and which stage it's in, with a decision table for engineering and finance.
- [The Useful Life of Software (and How to Amortize It)](https://www.quantifyhq.com/software-capitalization/economic-life): The useful life of software is how long it stays worth running — and the period you amortize a capitalized build over. How to set a defensible estimate and amortize software the right way.
- [Is Software a Fixed Asset or a Capital Asset?](https://www.quantifyhq.com/software-capitalization/is-software-a-fixed-asset): When you capitalize software, what kind of asset is it? Short answer — a capital asset, but an intangible one, not a tangible fixed asset. What that means for your balance sheet.
- [Software Capitalization Journal Entries (with Examples)](https://www.quantifyhq.com/software-capitalization/journal-entries): How to book capitalized software in your ledger — the journal entries for capitalizing development costs, amortizing them, and writing off software you retire, with worked examples.
- [Software Depreciation vs. Amortization: Which Applies?](https://www.quantifyhq.com/software-capitalization/software-depreciation): People say "software depreciation," but capitalized software is amortized, not depreciated. The difference, why it matters, and how software's cost is actually spread over time.
- [What is software capitalization?](https://www.quantifyhq.com/software-capitalization/what-is-software-capitalization): Software capitalization records certain development costs as a balance-sheet asset instead of an expense — what it is, what qualifies, and how GAAP draws the line.

## Software-capitalization/glossary
- [ASC 350-40: Internal-Use Software](https://www.quantifyhq.com/software-capitalization/glossary/asc-350-40): ASC 350-40 is the U.S. GAAP standard for capitalizing internal-use software — software built or bought to run your own business, not to sell.
- [ASC 350-50: Website Development Costs](https://www.quantifyhq.com/software-capitalization/glossary/asc-350-50): ASC 350-50 is the U.S. GAAP standard for capitalizing website development costs — which build costs become an asset, and which are expensed.
- [ASC 720-45: Business and Technology Reengineering](https://www.quantifyhq.com/software-capitalization/glossary/asc-720-45): ASC 720-45 governs the accounting for business-process and technology reengineering costs — which are expensed, even when bundled into a software project.
- [ASC 730: Research and Development](https://www.quantifyhq.com/software-capitalization/glossary/asc-730): ASC 730 sets the default for research and development costs — expensed as incurred — the baseline the software-capitalization rules carve their exceptions out of.
- [ASC 985-20: Software to Be Sold](https://www.quantifyhq.com/software-capitalization/glossary/asc-985-20): ASC 985-20 is the U.S. GAAP standard for capitalizing the cost of software you build to sell, lease, or market — keyed to technological feasibility.
- [ASU 2025-06: Performance Requirements](https://www.quantifyhq.com/software-capitalization/glossary/performance-requirements): A term ASU 2025-06 defines as what the software needs to do — its functions and features; until the significant ones settle, capitalization waits.
- [ASU 2025-06: Probable-to-Complete Threshold](https://www.quantifyhq.com/software-capitalization/glossary/probable-to-complete): The ASU 2025-06 threshold for capitalizing internal-use software — capitalize once funding is committed and the project is probable to be completed and used as intended.
- [ASU 2025-06: Significant Development Uncertainty](https://www.quantifyhq.com/software-capitalization/glossary/significant-development-uncertainty): A condition introduced by ASU 2025-06 that blocks capitalizing internal-use software costs until novel technology is proven or requirements stabilize.