New CapEx and OpEx Article
I’ve been working off and on for the last 4-5 months refactoring the CapEx/OpEx article. There are a number of reasons for this:
- As Agile crosses the chasm to the larger enterprise, it is a topic of increasing awareness, and often a major concern. Some transformations are stopped due to a lack of understanding of the applicability of current accounting treatments for CapEx in software, which are currently typically based on waterfall development. More and more information is becoming available on the problem, as well as potential solutions.
- I was never thrilled with the article anyway, as some readers thought it tended to capitulate to Story tasking by hours, which SAFe doesn’t even recommend
- In addition, I recently had the opportunity to attend a full day workshop at Rally/CA facilitated by Catherine Connor and led by Pat Reed. Pat has been working with the Agile Alliance Agile accounting standard program and industry in general to advance an understanding of the topic. Catherine is working with number of enterprises on this same topic. Also attending the workshop was an Agile/savvy technical accountant from one of the world’s largest financial services companies. Fortunately, I got to sit by her the whole day, and I picked at her brain mercilessly. Thanks Melyssa!
While there were a variety of opinions on the topic, I think we did come together with some common agreement and language to describe the problem and potential solutions.
The SAFe perspective is now provided in this new article. In the Learn More section below, I’ve linked to Catherine and Pat’s (brand) newly published writings on the same topic.
I’d like to use this blog post, which is open to comments, to get additional feedback on the article, and the general topic. So please fire away in the comments below.
I’d also like to thank Catherine, Pat and Melyssa for their joint efforts in helping to bring the business benefits of Lean-Agile development to some of the world’s largest enterprises. We share that mission fully.
And to the readers, thanks for all you do for all those enterprises out there, as well as for your contributions to SAFe,