|Published (Last):||7 September 2005|
|PDF File Size:||15.96 Mb|
|ePub File Size:||17.34 Mb|
|Price:||Free* [*Free Regsitration Required]|
Certainly it is a very good idea to adopt disciplined agile strategies into an existing CMMI environment, although the opposite direction, applying CMMI into an existing Disciplined Agile environment, is very questionable in our opinion. Identify causes of selected outcomes and take action to improve process performance. Establish and maintain the integrity of work products using configuration identification, configuration control, configuration status accounting, and configuration audits.
Tends to be heavy handed in the description, and as a result likely goes beyond just good enough for the given context Decision Analysis and Resolution DAR.
Analyze possible decisions using a formal evaluation process that evaluates identified alternatives against established criteria. Develop and sustain a measurement capability used to support management information needs. Establish and maintain a usable set of organizational process assets, work environment standards, and rules and guidelines for teams. Develop skills and knowledge of people so they can perform their roles effectively and efficiently. Assemble the product from the product components, ensure that the product, as integrated, behaves properly i.
Establish and maintain plans that define project activities. Provide staff and management with objective insight into processes and associated work products. Elicit, analyze, and establish customer, product, and product component requirements.
Identify potential problems before they occur so that risk handling activities can be planned and invoked as needed across the life of the product or project to mitigate adverse impacts on achieving objectives. Manage the acquisition of products and services from suppliers. Select, design, and implement solutions to requirements. Solutions, designs, and implementations encompass products, product components, and product related lifecycle processes either singly or in combination as appropriate.
Demonstrate that a product or product component fulfills its intended use when placed in its intended environment. Ensure that selected work products meet their specified requirements. CMMI Level. Configuration Management CM. Tends to be heavy handed in the description, and as a result likely goes beyond just good enough for the given context.
Collaborative work Light-weight milestones Enterprise awareness Active stakeholder participation. This PA assumes project teams whereas DA also supports, and encourages, stable product teams instead.
Measurement and Analysis MA. None, other than keeping it as lightweight and practical as possible. It is an underlying assumption of DA this this will happen, although it is kept as lightweight as appropriate.
Organizational Training OT. Product Integration PI. Explicit support for many technical practices such as continuous integration CI , parallel independent testing, regression testing, initial architecture , architecture spikes, continuous delivery and many more.
Project Planning PP. Requirements Development RD. Requirements Management RM. Heavy, assumes bi-directional traceability is desired whereas in practice it is only sometimes needed. Technical Solution TS. Validation VAL. Verification VER.
Mapping CMMI to Disciplined Agile