Archive

Posts Tagged ‘Enterprise Architecture’

When Done is Done in Agile Scrum

May 16th, 2009

rightwritten by gunther gerlach-2009

In management process, there are few needs to happen for the sprint (iteration) to be called done. There are at least three types of Definitions of done.

 

Story Definition of done

·      A Story definition of done would look like this.

·      All stories should have automated acceptance test.

·      The story should have working code supported by unit test that provide around 60 – 70 percent coverage.

·      The story should have well defined acceptance criteria.

Gunther Gerlach

What is a Pair Programming?

May 16th, 2009

peoplewritten by gunther gerlach-2009

An XP practice where two programmers work alongside each other, trying to get a task accomplished. Two minds at one problem!

 

How this help?

 

·         It brings up productivity if the pair knows what it is up to. A chatty pair can cause more damage to the project than getting done

·         It keeps each person honest. If you don’t know something its apparent in the fifth minute.

·         It helps keep the quality of the code. Since the pair is helping code.

·         This is where design happens.

Gunther Gerlach

Capability Maturity Model 2 [CMM/CMMI]

May 5th, 2009

docs2written by gunther gerlach-2009

As I mentioned earlier, ” 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

Level 2 – Key Process Areas

Level 1-Initial: processes are unpredictable and poorly controlled

Level 2-Repeatable: Can repeat previously mastered tasks

Gunther Gerlach

Capability Maturity Model [CMM/CMMI]

May 5th, 2009

cubeswritten by gunther gerlach-2009

The 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 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 currently covers systems engineering, software engineering, integrated product and process development, and supplier sourcing. The represents the consolidation of the following models:

Gunther Gerlach