This software classification was created/defined by Jocelyn Goldfein in the article http://firstround.com/review/the-right-way-to-ship-software/ and explained at The "right" way to ship software Jocelyn Goldfein - hack.summit 2016 for example.
The model classifies an application in two axes:
- Horizontal axis: Stack and deployment model. From very costly to deploy (on-premise, operating systems, embedded software, etc.) to easy to deploy (web application in a cloud PaaS).
- Vertical axis: Business model. From very costly software for a critical mission for an enterprise, up to free software for consumers.
Attending to this classification, we can define the cost of making a mistake for the application, the optimal release process, how to obtain feedback, etc.
For example, for costly enterprise software deployment on-premise, the best approach for obtaining feedback, perhaps is having beta tester programs with discounts for the customer. But to get feedback from a customer-oriented software that is sustained by ads, the fastest way is A/B testing and continuous deployments of new experiments.
Another example, if we consider 1x the cost of making a mistake for a free consumer web application deployed in the cloud, perhaps the cost of making a mistake for expensive enterprise software deployed on-premise may be two orders of magnitude higher.
I found this classification very useful for my day to day work. But remember, the context can be different for each part of a large system and also evolve with time.
According to this classification, these are the systems in which I have been involved:
Thank you, Jocelyn Goldfein, for this useful classification model.
References:
- http://firstround.com/review/the-right-way-to-ship-software/
- The "right" way to ship software Jocelyn Goldfein - hack.summit 2016
- http://www.eferro.net/2017/12/it-depends-context-on-creating-software.html
No comments:
Post a Comment