Software Development organisations need to be very aware of the maturity model of their industry. Based on the forming, storming, norming, performing model of change management I've devised the following phased model of IT maturity. The bigger they are, the more aware the organisation needs to be because in Phase 4 lurks the small start up who wasn't even on your radar, but who will bring you down.
Phase 1 (embryonic)
-Niche technology pockets addressing specific challenges
-Feature focus. No one minds how you solved the problem, as long as you solved it.
Phase 2 (childhood)
-Technology pockets grow so as to bump up against each other
-Boundaries are created
-Interfaces cause unexpected complications that result in under delivery
Phase 3 (adolescence)
-Responding to the escalating costs and complexity, clients reduce the downside risk and consolidate suppliers
-Gorilla takes all
Phase 4 (adulthood)
-With benefits realigned with expectation, clients turn to maximising the up side and exploiting new generation technologies
-How you've been solving the problem becomes VERY important, because it needs to be consistent with other methods, frameworks and ecosystems
-Creation of platforms for effective competition
-People who can master taking the same components and reuse them in interesting ways will create new business models that redefine the market
Now we can discuss where your company or sector is, and where you're heading.
Tags: technology, information technology, IT, software development, maturity, model, IT architecture, software architecture, developer