The purpose of Configuration Management (CM) (CMMI-DEV) is to establish and maintain the integrity of work products using configuration identification, configuration control, configuration status accounting, and configuration audits.
Send us an email with Subject: Appraisal Plan and we will send you the Demix Appraisal Plan.XLSX tool. It provides wonderful features to simplify your appraisal planning.
Send your emails to This email address is being protected from spambots. You need JavaScript enabled to view it..
The CMMI® is an integrated set of best practices that improve performance and key capabilities for any organization that wants to develop better products, components, and services.
Two forms of Health Check are offered the Silver Appraisal (SCAMPI B) and Gold Appraisal (SCAMPI A).
Both are led by a Certified CMMI® Lead Appraiser supported by trained Appraisal Team Members.
The primary difference between the two types of Health Check is the level of rigor and the fact that the SCAMPI A Appraisal can provide a Capability Level for each of the PMO Process Area in scope, the results can also be published on the CMMI® Institute PARS Site (Published Appraisal Results) if required.
The key deliverable being a report highlighting strengths and opportunities for improvement. This can optionally be expanded into a comprehensive PMO Improvement Plan the implementation of which can be supported by DEMIX Consultants if required.
If your PMO is not adding the value you expected then perform a DEMIX PMO Health Check to find out why!
To find out more or register interest contact Stephen Woods via the email below:
Stephen Woods
This email address is being protected from spambots. You need JavaScript enabled to view it.
or
This email address is being protected from spambots. You need JavaScript enabled to view it.
Definition: Webster defines a tool as "something regarded as necessary to the performance of one's occupation or professional task. [Words are the tools of my trade.]" Configuration Management (CM) tools come in several forms. For systems engineers and their sponsors, these tools include best practice methodologies, standards, documentation, managed environments, manual tools, automated tools, and leadership skills. These require and enable the discipline and rigor needed to plan, stand up, implement, and carry out CM successfully.
Keywords: automated tools, configuration management policy, program management plan, statement of work (SOW), tools
Too many CMDB projects have become black holes, sucking resources and life out of IT with little provided in return. Despite more pragmatic approaches these days, Gartner1 states that more than half of CMDB efforts become unmanageable. With that in mind, how much information needs to go into your CMDB—and when? Hundreds of articles and entire books have been written on this topic, and getting to a specific answer for an individual organization can require weeks or months of workshops and design analysis. In the interest of brevity, I will condense this into one blog post.
Summary: A variety of agile software development methods and practices have now been around for a solid ten years and existed for at least another ten years prior. Configuration management (CM) for agile development has now been discussed since the turn of the century. So what are the core principles of CM and how can CM help agile teams?
By definition configuration management is the process that defines and controls the components of services and products, also maintains accurate information on the historical, planned and current state of the services and products.
Some of the country’s largest IT organizations are looking trim and vigorous these days. It’s no miracle cure or diet of the month. It’s a particular piece of process methodology called Six Sigma.
Six Sigma is a defect reduction methodology that transforms organizations by forcing them to focus on the quality of the customer experience. The term sigma refers to deviations from an ideal level of operation, where each level of sigma, starting from one, allows for fewer defects. Sigma six, the
operational equivalent of nirvana, allows a mere 3.4 defects per million outputs. If you’re in manufacturing, that means 999,996.6 flaw-free widgets. If you’re in IT, that means fewer servers, faster call response times and better project delivery.
Automation is being adopted by many organisations that may be new to the concept of Configuration Management. How do they address this challenge?
With the introduction of automation not only in our daily lives but also in asset-intensive industries, the processes to maintain and manage the configuration of these assets has become more complex. This article 'Challenges of Configuration Management in the Age of Automation' aims to look at some of the challenges that can be experienced in managing the configuration of automated assets and how these challenges can be addressed
