This thread is so full of useful information I'd like to move it into a public area and rename it. Suggestions as to the appropriate forum and a new thread title invited (please).
Participation is voluntary.
Alcocks Electrical Services | Alcocks Pest Control & Entomological Services | Alcocks Hygiene Services
'software development processes' under the it forum?
The cost of living hasn't affected its popularity.
Sponsored By: http://www.honeycombhouse.com
Hi Dave, I have to agree with Marg, 'Software Development Processes' under the IT forum is perfect.
found a mapping for ISO vs CMMI as well.
Read here.
it's kind of interesting when someone does a comparison like that.
apologies if I'm asking questions that are available somewhere, I just didn't see them on the CMMI site, but how do the maturity levels differ? would those be levels of CMMI integration into business practices? and if that is the case, isn't that a slightly different way of saying "Compliant"?
Dave A (19-Aug-09)
Thank you very much for the link you have sent. It is very informative!
You really don’t have to apologise, it is always nice to add extra information where possible.
To understand the levels, you need to know that CMMI has two representations
1. Staged Representation
2. Continuous Representation
The decision to choose one or the other depends on the goals of the organisation.
Staged Representation uses maturity levels to measure process improvement, there are 5 maturity levels. It will provide a sequence of improvements, beginning with basic management practices and progressing through a predefined and path of successive levels, each serving a foundation for the next.
Maturity levels are as follows:
ML1: Initial - This is typically ad hoc and chaotic. ML1 has no process areas
ML2: Managed - An organisation has achieved all of the goals of the ML2 process areas. ML2 has 7 Process areas
ML3: Defined - An organisation has achieved all of the goals of the ML2 and ML3 process areas. ML3 has 11 process areas
ML4: Quantitatively Managed - Processes achieved are controlled using statistical and other quantitative techniques. ML4 has 2 process areas
ML:5 Optimising – All the process areas are achieved. ML5 focuses on continually improving process performance
Continuous Representation uses capability levels to measure process improvement, there are 6 capability levels. The organisation can select the order of improvement that best meets the organisation’s business objectives.
Capability levels are as follows:
0 Incomplete
1 Performed
2 Managed
3 Defined
4 Quantitatively Managed
5 Optimising
Both representations are designed to offer essentially equivalent results, most organisations choose the stage representation.
Not all the CMMI levels integrate into the business practices, CMMI will show the business what is working and what is not, it helps align business goals and IT goals.
Dave A (19-Aug-09)
Here I have attached an image of the stage represenation maturity levels.
Maturity Levels:
Maturity levels consist of a predefined set of process areas. The maturity levels are measured by the achievement of the specific and generic goals that apply to each predefined set of process areas.
Idle thought occured -
Typically, is software development considered a project or an organisation?
Participation is voluntary.
Alcocks Electrical Services | Alcocks Pest Control & Entomological Services | Alcocks Hygiene Services
Software development can be considered to be a project and an organisation:
As an example, a banking institute will have multiple software development projects actively running, however they are not considered to be a Software Development organisation.
The other example is an organisation that solely does software development with multiple software development projects actively running can be considered to be a Software Development organisation.
I dont know about organisation but I can tell you about the process and projects.....for eg..here is a typical Software Development Cycle.
- Programmer produces code he believes is bug-free.
- Product is tested. 20 bugs are found.
- Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren't really bugs.
- Testing department finds that five of the fixes didn't work and discovers 15 new bugs.
- Repeat three times steps 3 and 4.
- Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.
- Users find 137 new bugs.
- Original programmer, having cashed his royalty check, is nowhere to be found.
- Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.
- Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits.
- Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.
- New CEO is brought in by board of directors. He hires a programmer to redo program from scratch.
- Programmer produces code he believes is bug-free…
The cost of living hasn't affected its popularity.
Sponsored By: http://www.honeycombhouse.com
Dave A (21-Aug-09), Genevie Vince (21-Aug-09), Yvonne (24-Aug-09)
Did you like this article? Share it with your favourite social network.