Recently, there was some discussion in the group about the “Agile development model” and the “waterfall model”, and everyone exchanged ideas. In my opinion, it is important to know the history of agile and development models in order to decide whether to be specific:
Agile model history (in the country)
It should be from 2011 to 2014 when start-up companies mushroomed in China, such as O2O, e-commerce, small games and small apps. It seems only yesterday that these words are so familiar
There are five characteristics of such an organization/business:
- Small team size
- Low technology
- Version update is easy, anyway is the Internet release
- The CEO urged the team: “Hurry up and build the demo. The next round of funding is waiting.”
- The CEO/PM is also unclear about the product’s goals, and sometimes just looks for a copy of a competing product, or the RQD of the product is not logical
The history of the waterfall model
By contrast, the waterfall model is still used in “traditional” software companies, often in the form of images like the following:
- to B
- Enterprisey: Millions of lines of source code, every single product on G, the entire suite of dozens of individual products
- Enterprise-level software means that programmers are not natural users and need to be trained in the industry or technology
- The release cycle is long and cannot be updated too quickly
- Detailed business logic
evolution
Now the Internet of small fish shrimp warring States period has ended N years, began to cut drama large enterprises. The original fast iteration business began to slow down and precipitate, with more than 10,000 BU appearing, and the module began to deepen. As a result, there has been a “rethink” of agile models and a resurgence of waterfall models.
Which one should I use?
It is relatively easy to make a decision based on the history of both models and the current corporate positioning, business logic, and organizational form.