When one looks at all the wastes, defects has to be the most obvious one. The cost and repercussions of finding defects varies depending on where in the cycle they’re found. Defects found early on in the development life-cycle are way less costly to resolve than defects found later on in the cycle; the most expensive being when applications are already in-production.
Additionally, depending on when the defects are found, defects can and do trigger other wastes like task switching, relearning etc.
Gunther Gerlach
written by gunther gerlach-2009
In wider spanning service ecosystems, several service providers may offer functionally replaceable services that differ in their extra-functional characteristics, such as usage terms and quality of service delivery. Service providers need to be responsive – potentially in real-time – to negotiate variations of service delivery requirements (e.g., price, deliverable timetable). Service ecosystems should therefore explicitly support the negotiation process, reducing non-critical human involvement and providing decision-makers with the information they require to formulate and assess service offers.
Gunther Gerlach
written by gunther gerlach-2009
Velocity is a measurement of how much the team gets done in an iteration (called as Sprint in Agile Scrum). Velocity is what actually got done in the last iteration not what is planned and is calculated by the number of story points done in a certain sprint.
In Scrum it is measure in Story points. Each feature in scrum is a story. A story has points. Points can be anything you come up with.
Examples are 1, 2, 4, 8 , 16
Gunther Gerlach
written by gunther gerlach-2009
As I mentioned earlier, Capability Maturity Model “CMMI” is a collection of best practices for the development and maintenance of both products and services. It is the application of process management and quality improvement concepts to software development and maintenance and, designed to guide in selecting improvement strategies by determining current maturity of the software process.
The Five Levels of CMMI
CMMI Level 2 – Key Process Areas
CMMI Level 1-Initial: processes are unpredictable and poorly controlled
CMMI Level 2-Repeatable: Can repeat previously mastered tasks
Gunther Gerlach
written by gunther gerlach-2009
The CMMI is a collection of best practices for the development and maintenance of both products and services. It was developed to enhance and replace the use of multiple process models, while preserving the government and industry investments in process improvement. By combining multiple models into a single model, the CMMI has enabled the use of common terminology, components, appraisal methods, and training material across multiple disciplines. This, in turn, reduces the cost of establishing and maintaining process improvement efforts across the enterprise using multiple disciplines to deliver products or services. The CMMI currently covers systems engineering, software engineering, integrated product and process development, and supplier sourcing. The CMMI represents the consolidation of the following models:
Gunther Gerlach
