Lean software development had a unique start, actually being a phrase coined by Mary and Tom Poppendieck in a book that took traditional lean principles but updated, coupled with 22 tools specific to agile practices.  To introduce this concept, this couple has spearheaded numerous conferences, moving the lean software development to new communities.

As a part of lean software development, there are seven specific principles, which run almost parallel to the same ones used by lean manufacturing.  These concepts include:

Waste Elimination

Waste is defined as anything that is unnecessary, extra, defected or damaged, non-producing, not being used or pending completion of something else. In other words, specific to lean software development, anything that is not moving forward or being productive would be deemed waste, which needs to be eliminated.  Everything associated with software development should be adding value to the customer.

For instance, in the arena of software, coding and/or functionality that are considered unnecessary would be waste.  If some type of software was pending completion that too would be wasted.  However, other factors that would be considered waste specific to lean software development include poor communication within an organization, red tape, and unclear direction or needs.

Amplify Learning

The second principle on which the lean software development concepts are based is with Amplify Learning.  With this, ongoing and in-depth testing is required to ensure any errors, defects, or challenges are identified early.  This way, as the code or language is being written, it can be corrected, which saves tremendous time, effort, and money.

The goal with this principle is to shorten the time it takes for a process to be learned by using shorter iteration cycles.  With this, feedback internally and from the customer is received so anything needing to be changed or adjusted can be done quickly to benefit additional or future developments.

Options-Based Approach

Next, lean software development works by working off this approach so important decisions can be made only on facts and not predictions or estimates.  As a computer system begins to grow and become complex, the chance for change is much greater.  However, having the ability to make changes and fix errors, especially those that would cost the company a fortune, especially if the product has been launched.

Fast Delivery

Now, for lean software development, the truth is that companies that can roll out technological solutions typically win.  The reason is that with a quick release, input from users is received, allowing programmers to make appropriate changes.  For this reason, it is common to see multiple versions of a single software solution.

With a fast delivery, the customer’s needs are being addressed quickly while providing opportunity for the programmers to take input and make corrections or changes.  Once the solution being offered is determined to be unrealistic or unreasonable, it is completely removed from the market, likely to be replaced in time.

Team Empowerment

The lean software development concept also includes giving power to team members.  This means businesses need to put people in positions of making correct decisions.  One of the worst practices that can pull a company down is micro-managing.  Instead, managers need to listen to what the developers are saying and entrust them to make the right decisions for the betterment of the company.

Integrity

It is vital for lean software development that programmers work off the concept of perceived integrity.  This means that the way in which a software program is written is done with integrity based on advertising, delivery, assessment, deployment, use, price, and its ability to function and provide solutions to problems.

For lean software development to work, it has to have integrity built into the system from the start, ensuring that each component works as a team, bringing a solid solution to the company, and ultimately, the customer.  Therefore, maintenance, flexibility, responsiveness, and efficiency have to have the perfect balance.

The Big Picture

Finally, lean software development concepts take the overall picture into consideration.  Obviously, the program has to be such that the user can perform a specific task to ensure the customer is happy.  Because many programs are used by multiple departments within an organization, there also has to be cohesive training to ensure everyone is on the same page.

The bottom line is that to eliminate waste and create a powerful solution, lean software development has to follow some very specific concepts.  When this is done, the results are tremendous!  Customers are much happier, employees feel empowered by being given the right tools and resources, and the company begins to see profits increasing significantly.