After rereading our white paper “Your Software Project…Approved: Discover Agile’s CapEx/OpEx Advantage”, we realized that some critical information was missing.
In the paper, we explained how Agile gives you the flexibility to capitalize a larger percentage of software development costs. And yes, that still means you can start your projects with less OpEx.

What we forgot to warn you about were some common mistakes that could put your software project at risk, even if you partner with an Agile firm.

So, here they are—the top 10 things you should never do or the accounting gods will rain fire on your software project:

1. Send your CFO an email, asking her to lighten up on “all that CapEx/OpEx crap”.
2. Pay your development partner with gift cards.
3. Try to amortize CapEx over a bazillion years, making your project practically free.
4. Categorize that marathon interoffice Halo competition as “development” and claim it as CapEx.
5. Hire a psychic to verify the future economic benefit of your software.
6. Describe each project expense as “about x dollars—you know, give or take a few thousand”.
7. Hire your cousin to develop the software and do the accounting.
8. Invite everyone in the office to your own version of the Burning Man festival, where you publicly torch the company’s CapEx/OpEx policy.
9. Insist that 90% of all projected software development expenses will be neither CapEx nor OpEx, so no one has to worry about costs.
10. Design your software’s loading screen to show a picture of your CFO with horns, a goatee, and a red, bifurcated tail.

Hopefully, after reading this handy list, you’ll be able to put away that asbestos umbrella and build some great software that’s within your budget.

Want to learn more about our Agile approach to software development? Check out our other white papers or contact us directly.