The Runway of Software Products
“… the “runway” available for software products to mature and take off is both limited and precarious. Software products are subject to two over-arching phenomena that affect the runway big time: open source software and software decay…
Click here for a discussion how the two phenomena – open source and software decay – affect both the runway and the hardware v. software discussion.
A Seven Year Retrospective
The results measured by Michael reaffirmed for me a core belief that I had developed as a young man in the Israeli army: ordinary people can achieve extraordinary results. We did not have, with all due respect, extraordinary talent at BMC; our development tools were nothing to write home about; the problems of communicating effectively across 10.5 hours of time zone difference from Austin, TX to Pune, India were very real; and, we were subject to repeated layoffs. What we accomplished was primarily a matter of doing the right things by an extremely important stakeholder – the business unit employees.
Click here for a detailed account of the 2004 experience from a 2011 perspective.
The Three Faces of Innovation
To succeed with innovation, you need to simultaneously address all three aspects:
- Affordable experimentation through the Agile process.
- Empowerment of (self sufficient) local teams.
- Let go of the hierarchical control concentrated in corporate headquarters.
A New Arithmetic for the Backlog
The heart of the matter in this engagement was ensuring that technical debt stories would not become ‘second citizens.’ We proposed treating technical debt as a strategic investment theme. To our way of thinking, technical debt is no different from customary budget allocations to growing market segments, tactical sales opportunities, cost reduction and the like.
Click here for details in the Cutter blog including guidance how to work through the Data Structure of the Enterprise figure below.
Allocation Flows in the Data Structure of the Enterprise
Technical Debt: Assessment and Reduction
Below is the detailed outline for my August 8, 1:30-5:00PM Technical Debt Workshop in Agile 2011. I look forward to meeting you and interacting with you in the conference before, during and after this workshop!
Best,
Israel
Technical Debt: Assessment and Reduction
Part I: Technical Debt in the Overall Context of the Software Process
- A Holistic Model of the Software Process
- Two Aspects of Output
- Three Aspects of Technical Debt
- Six Aspects of Software
Part II: What Really is Technical Debt?
- What’s in a Metaphor?
- Code Analysis
- Time is Money
- Monetizing Technical Debt
- Typical Stakeholder Dialog Around Technical Debt
- Analysis of the Cassandra Code
- Project Dashboard
Part III : Case Study – NotMyCompany, Inc.
- NotMyCompany Highlights
- Modernizing Legacy Code
- Error Proneness
Part IV: The Tricky Nature of Technical Debt
- The Explicit Form of Technical Debt
- The Implicit Form of Technical Debt
- The Strategic Impact of Technical Debt
- No Good Strategy Following Prolonged Neglect
Part V: Unified Governance
- How We View Success
- Three Core Metrics
- Productivity, Affordability, Risk
- What is the Real ROI?
Part VI: Process Control Models
- A Typical Technical Debt Pattern
- Process Control View of Scrum
- Integration of Technical Debt in the Agile Process
- Using Statistical Process Control Methods
Part VII: Reducing Technical Debt
- A Framework for Thinking about and Acting on Technical Debt Issues
- Portfolio Governance
Part VIII: Takeaways
- Nine Simple Takeaway
- Connecting the dots
“Increase your own agility and stealthiness with this blog”
The Agile Executive has been featured on Online Universities list of the Best Management Blogs. The referees cited the following reasons for picking the blog:
When it comes to streamlined leadership, the clunky and the clumsy don’t find much favor. Increase your own agility and stealthiness with this blog.
I feel honored and privileged.