Lean development life cycle

The purpose of this workshop is to show that lean/CI professionals are not helpless, nor are their situations hopeless. There are skills and resources they can draw upon, the most important of which is their own ability to use themselves and their role to influence. The workshop is designed for lean leaders who wish to learn to better use their ability to personally influence to secure the approval, collaboration or support needed to lead the work they are responsible for. These skills can be successfully adapted to influence superiors, peers and direct reports in ways that increase the likelihood of success.

One of the healthy ways towards integral architecture is refactoring . As more features are added to the original code base, the harder it becomes to add further improvements. Refactoring is about keeping simplicity, clarity, minimum number of features in the code. Repetitions in the code are signs of bad code designs and should be avoided. The complete and automated building process should be accompanied by a complete and automated suite of developer and customer tests, having the same versioning, synchronization and semantics as the current state of the System. At the end the integrity should be verified with thorough testing, thus ensuring the System does what the customer expects it to. Automated tests are also considered part of the production process, and therefore if they do not add value they should be considered waste. Automated testing should not be a goal, but rather a means to an end, specifically the reduction of defects.

Lean development life cycle

lean development life cycle


lean development life cyclelean development life cyclelean development life cyclelean development life cyclelean development life cycle