written by gunther gerlach-2009
In Agile Scrum 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
written 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
written by gunther gerlach-2009
Story points are used to measure the effort required to implement a story and is measure based on Size, Factorial, Squares or Fibonacci techniques. This is a random measure used by Scrum teams.
This is mainly done as we as humans and as managers are better at abstract terms. If we use hours as a way to size stories, then the managers in the room have questions, teams don’t immediately feel comfortable with hours…
|
Duration
|
Size
|
Factorial
|
Squares
|
Fibonacci
|
|
1 – 3 day
|
X Small
|
1 (1!)
|
1 – 12
|
1
|
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
written by gunther gerlach-2009
How it works: Select a regular time period over which to measure project velocity. If you’re using fixed Sprints or iterations, use that time period. Otherwise you can use weeks, fortnights or months. It doesn’t really matter which as long as you’re consistent. Add up the estimates for all the tasks/deliverables/features in your chosen time period. It doesn’t matter whether the estimates are in days, hours or even in relative story points. Only include the estimates for any items that are 100% complete and signed off within the time period. Anything still in progress counts as zero, as there is no value in incomplete work.
Gunther Gerlach
