It’s time again for another installation in our series about SDLC models! Next up: the Lean model.
Unlike other SDLC models, the Lean model focuses on the “less is more” principle. The model does this by streamlining the software development lifecycle.
7 Principles of Lean Software Development
The Lean model is guided by these seven principles that focus on reducing wasted time and increasing value:
- Eliminate waste
- Increase learning
- Decide as late as possible
- Increase integrity
- Deliver as quick as possible
- See the process as a whole
Following the Lean model means that developers can minimize the amount of waste produced.
The Lean model is set up in a way that waste reducing efficiencies can be applied to each level of production. This includes at the department level, the whole organization, interdepartmental operations and organizational relationships between suppliers and customers.
For the Lean model, the word “waste” has a wide-ranging definition that encompasses any aspect of a project that doesn’t add value to it.
The focus for product development teams that work with the Lean model should be on learning.
Additionally, the high demand for software apps means that developers should decide on the features they plan to use as late into the process as they can because this will decrease the chance of having to make changes.
Advantages of the Lean model
The biggest advantage to utilizing a Lean model is the elimination of waste.
Another advantage is that the model allows for projects to be delivered to customers quickly.
The Lean model also allows for regular communication with the customer.
Disadvantages of the Lean model
One disadvantage of the Lean model is that relies heavily on a team. This means that those wanting to work with the Lean model will need to have an established team with a high skill set around them.
Given the team aspect of the Lean model, there is also the tendency for multiple subgroups that can result in a loss of focus.
Another disadvantage is that it requires a high degree of documentation, which means that any area that is poorly documented is in danger of being underdeveloped.