CMMI is a framework for Software Process Improvement. CMMI is divided into Maturity Levels, then these Maturity Levels are further divided into Process Areas and each Process Area is further divided into Specific Practices. At Maturity Level 3 there are 18 Process Areas that needs to be fulfilled. Now question arise how to achieve Maturity Level 3. We can divide… Read more →
Many times we come across this question about the time frame required to achieve CMMI Maturity Level 3 from CMMI Maturity Level 2. There is no straight forward answer to this question. And a simple answer will be â€“ it depends. It depends on many factors, like: Current Processes Implementation Status Compliance Level Cultural Issues
The only way to be sure that the Organization you are going to work will follow the defined process is to identify the correct appraised identity within the organization. That means to say that when an Assessment is conducted for CMMI SCAMPI C, B or A and â€œOrganizational Unitâ€ (OU) is identified that goes under assessment. This OU can represent… Read more →
Lots of IT companies today are using or moving towards using Agile Projects to develop new projects because of the freedom project teams have and the enhanced experience customer enjoy in Agile Environments. At the same time these companies fear that they would not be able to attend CMMI Maturity Levels 3 by with Agile Projects. Many Quality Consultants also… Read more →
Q:- I am a Defect Prevention team member in our CMMI Maturity Level 5 company. We are trying to plot the Defect Removal Efficiency (DRE) metric in our projects. I have a few questions: Our DRE is based on phase level defect injection and detection concepts. If we go closely by the definition of the phase “testing/QA”, bugs should not… Read more →
An organization may choose to approach process improvement from either the Process area capability improvement approach Organizational maturity improvement approach CMMI models support each approach with a representation.
Software Engineering is not considered an engineering discipline throughout the world when compared to electrical engineering, mechanical engineering, and civil engineering. Software Engineeringâ€™s brief history has been filled with problems: Cost overruns Schedule slippage Poor performance compared to specification Unsatisfied customers
What youâ€™ll see: Unclear who is authorized to make what decisions? Decisions are made on primarily subjective basis Same issue is â€œdecidedâ€ over and over and overâ€¦â€¦ Rationale for earlier decisions is unavailable when needed to understand the decision later in the project Only a few choices considered for major decisions
What youâ€™ll see: Idealistic approach that assumes â€œall is wellâ€ even when there is evidence that all is NOT well Issues that are known risks to project staff are a surprise to management Every time a new problem manifests, a new management technique is tried
What youâ€™ll see: Staff attending training courses they donâ€™t need Staff avoiding training that is provided Inappropriately-skilled staff being assigned to tasks, often without knowledge of the deficiency Staff arenâ€™t released to attend training they do need.