Senex Rex
  • Team
  • Blog
  • Resources
  • Contact

Why Should Agilists Care About Capitalization?

Posted on February 10, 2013 by Dan Greening Posted in Enterprise

Agile Cap fig1

In many companies, agile software development is misunderstood and misreported, causing taxation increases, higher volatility in Profit and Loss (P&L) statements and manual tracking of programmer hours. One large company’s confused finance department expenses all agile software development and capitalizes waterfall development; projects in this company that go agile see their headcounts cut by 50%. This discourages projects from going agile.

Scrum’s production experiment framework can align well with the principles of financial reporting. In this article, the author explains the basics of capitalization and expensing, and offers a financial framework for capitalizing agile projects that can be understood by both accountants and agile teams.

Software development is an investment in the long-term future. Some software development projects are not long-term investments; it depends on whether the software remains an asset. Agilists should learn proper capitalization and teach their colleagues. Companies can usually save on taxes, hire more developers and create value more rapidly when they capitalize software development correctly.

Companies can gain tax advantages by capitalizing software development; by deferring costs they typically offset more taxable revenue and gain more interest income.

Corporate agilists need to help finance departments capitalize agile software development properly. ScrumMasters and agile department heads who understand capitalization and depreciation can generate millions in tax savings. Responsible agilists must work directly with their own corporate finance departments and auditors to craft acceptable capitalization processes.

Because recommended accounting practices ignore Agile, the article discusses how to classify costs as capital or operational expenses and gives guidance on how to make the transition from waterfall to Agile in a way that pleases management, accountants and auditors.

Making the case for agile capitalization will reduce your company’s tax burden, increase available funds for engineers, and make your auditors happy.

You can read the article by clicking on this link: Agile Capitalization

Share this:

  • Click to print (Opens in new window)
  • Click to share on Twitter (Opens in new window)
  • Click to share on Facebook (Opens in new window)
  • Click to share on LinkedIn (Opens in new window)
  • Click to share on Reddit (Opens in new window)
  • Click to email this to a friend (Opens in new window)
  • More
  • Click to share on Tumblr (Opens in new window)
  • Click to share on Pinterest (Opens in new window)
  • Click to share on Pocket (Opens in new window)
« Q&A: How can I transform my corporation to agile?
Reducing Release Duration Can Increase Agility – A Case Study »

Leave a comment Cancel reply

You must be logged in to post a comment.

Continue with Facebook
Continue with LinkedIn

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Newsletter




Recent Posts

  • Align to a Driving Purpose
  • Scrum
  • Agility
  • Agile Living
  • Is Agile a Subset of Lean Manufacturing?

Contact Us

Senex Rex
1037 NE 65th St # 80358
Seattle WA 98115 USA
+1 (415) 810-3693

Courses

  • Certified Scrum at Scale Practitioner
  • Certified Scrum Product Owner
  • Certified Scrum Master
  • Agile Capitalization Workshop
  • Short Course: Agile Manager

Key Posts

Scrum

  • What is an Agile Methodology? How does it beat Waterfall?
  • How can I transform my corporation to agile?
  • Strategy Scrum Teams Enterprise Scrum: Scaling Scrum to the Executive Level
  • Release Duration and Enterprise Agility

Agile Base Patterns

  • Measure Economic Progress
  • Adaptively Experiment for Improvement
  • Limit Work in Process
  • Embrace Collective Responsibility

 

Advocacy

  • Develop Agile Managers, or Agile Dies
  • Are We Agile? Answer 5 Questions to Find Out
  • Agile Cancer: Does team-only agile cause developers to quit?
  • Agile Cancer: Stop Whining and Cure It

Advanced Techniques

  • Bulk Estimation
Copyright ©2013-2015 Senex Rex LLC. All Rights Reserved.
loading Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.