Configuration Management is a self-discipline that is special to the organization of establishing application so is not specifically tackled wherever in the PMBOK. The objective of this article is to give recommendations on how this self-discipline can be integrated into your project management designs for a application progress project with the minimum amount of disruption. Even though none of the things of configuration administration are right tackled in the PMBOK you can uncover that establishing a application software of any dimension is extremely hard with out some things of configuration administration. The resource library employed to edition and release the application is a very good instance. CMM also specifies that the objective of configuration administration is to maintain the integrity of the application throughout the project’s application life cycle. Configuration administration will reward the business throughout the entire life cycle of the application products, lasting very well outside of the finish of the project which introduces it.
Beyond aiding in the CMM/CMMI certification approach, adhering to the conditions established for degree 2 certification in the space of configuration administration will not only reward your application project but will also reward upcoming initiatives and assistance the assistance business maintain the application items manufactured. The places reviewed in this series formerly (specifications administration, project arranging, project monitoring and oversight, subcontract administration, and high-quality assurance) all align with some awareness space from the PMBOK so compliance with individuals conditions need to not insert noticeably to the project scope. The pursuits needed to comply with CMM/CMMI conditions in this space might insert major overhead to your project. You need to compare the demands of the project for configuration administration function against the function needed to fulfill CMM/CMMI degree 2 conditions, determine the function and tools needed to tackle the delta and ensure that your project is adequately funded and resourced to undertake the supplemental function.
As with the other Critical Approach Parts (KPAs), Software program Configuration Management is structured into targets, commitments, qualities, pursuits, measurements, and verifications.
- Software program configuration administration pursuits are planned.
- Software program items below configuration administration are determined, managed, and available.
- Improvements to determined items are managed.
- Afflicted groups and persons are informed of the status and information of application baselines.
These targets will all align very well with a very well managed application progress project. Configuration administration function, like all the function of the project is planned, staffed, and scheduled, variations are managed by the Integrated Change Control Method and the information of baselines is communicated to the stakeholders in accordance with the Communications Management approach. Continue to keep in mind that the context in which CMM/CMMI employs the time period transform handle is precise to the application items below administration and will involve a device to deal with edition handle.
Commitment to Complete
Commitment is demonstrated by the prepared organizational coverage for application configuration administration (SCM). This coverage should condition who is accountable for SCM, how SCM is carried out by each and every project life cycle, a resource library device is employed, and that baselines are proven and routinely audited. The coverage will be up to the business to outline unless it is specified in the scope for your project.
Capacity to Complete
Capacity to perform is demonstrated by the establishment of a Software program Configuration Control Board (SCCB) and a Software program Configuration Management (SCM) group. The SCCB is accountable for developing application baselines, authorizing variations to the baselines, and releasing the application. The SCM group is accountable for the implementation and administration of the resource library and all SCM procedures, methods, benchmarks, and designs. In addition to the implementation of these 2 groups, the business is accountable for furnishing methods and funding for their pursuits and for instruction the SCCB, SCM group, and the application engineering group in SCM pursuits.
The development of the SCCB, SCM group, and all the procedures, methods, designs and benchmarks referred to as for below will be in addition to function needed to create a resource library device and a librarian which are minimum demands for the typical application project. These groups and documentation will choose substantial function to implement and need to be specified as section of the project scope if they are to be carried out.
Actions Carried out
- An SCM approach is geared up for the project (and for just about every project) in accordance with a documented method. This approach will be section of the project approach and will be employed as section of that approach to handle SCM pursuits for the project.
- A resource library process is proven. The conditions CMM/CMMI has for the library are fairly substantially what any very good device will give, with these achievable exceptions: that it assistance archival and restoration of configuration things and that it keep SCM documents and develop SCM reviews.
- The application function items to be put below configuration administration are determined. “Software program function items” include this sort of ancillary things as Small business Demands Documents, Functional Specifications, Depth Design Documents, test designs, and so forth. Identification also involves a special identifier for each and every item (this will be enforced by the library device), the baseline it belongs to, and the proprietor (developer, analyst, or tester).
- Change requests and bug reviews are recorded, reviewed, determined upon, and tracked according to a documented method. The Integrated Change Control Method has all round accountability for controlling variations to the project, like configurable things, and the process need to be described in your Change Management approach.
- Improvements to baselines are managed according to a documented method. The method need to ensure that application is correctly tested when it is changed, the SCCB approves variations to configurable things, and that verify-outs and verify-ins are performed correctly (i.e. managed by the resource library). The method need to also determine a transform request or bug report with each and every transform or fix. 1 way of facilitating this exercise is by integrating your SCCB and Integrated Change Control Boards (ICCB).
- Products from the resource library are created and their release is managed by a documented method. The method referred to below is the make approach. The librarian or make learn need to have a documented method which they adhere to to make and release a products. The method need to include this sort of issues as when and how the library is frozen, how a make is authorized (by the SCCB), and when builds are to happen.
- The status of configurable things is recorded according to a documented method. This suggests that the resource library device is able of reporting the current edition of each and every item, retrieving archived versions, and the composition of each and every release is recognised (the things incorporated and the edition of each and every item). The resource library device need to also be able of reporting on the cause for each and every new edition/update. Explanations will include new options, accepted variations, and bug fixes.
- Standard reviews on SCM pursuits, baseline contents, and so forth. are developed and made available to all influenced groups. The reviews referred to are non-technological and include this sort of data as transform requests, bug reviews, as very well as summary reviews of variations to each and every baseline and audit success. These reviews need to be described in your Communications Management approach.
- Software program baseline audits are done according to a documented method. The audits need to include assessments of baseline integrity, resource library construction, baseline contents (for completeness and correctness), and SCM benchmarks and methods compliance. The audit success should be noted to the project manager and audit points tracked to closure. Audits need to be done by an external human body but if the identification of this human body is an concern make the SCCB accountable for the audit.
Measurement and Evaluation
You are needed to evaluate your SCM pursuits. The measurements include progress to approach for configuration administration pursuits, general performance to spending plan for these things, as very well as metrics for transform requests. By assigning the different team users doing the job on SCM or SCCB pursuits to an SCM or SCCB group you will aid working with your MS Project file to report on only individuals pursuits. By dividing the function in the MS Project file into diverse places like 1 for application progress, and determining transform requests with the space they effect you can isolate SCM similar variations and report on individuals.
Verification and Implementation
SCM pursuits need to be reviewed by senior administration periodically. For the reasons of the project these testimonials can happen at Gate Review conferences or Steering Committee conferences, or in different conferences scheduled for the objective. SCM pursuits need to also be reviewed with the project manager. This criterion will be fulfilled if you manage these conferences and are in attendance. The SCM group periodically audits application baselines to validate information and correctness. It is unclear to me particularly what the distinction is involving this audit and the 1 described in Action #9, other than who performs the audit. Verification also phone calls for the SQA group to assessment and/or audit the function items and report the success. The SQA audit need to evaluate the adherence of the SCM, SCCB, application engineering group, and testers to the SCM methods and benchmarks.
A good offer of the conditions for CMM/CMMI Level 2 certification will be fulfilled by a project manager following greatest methods for application progress initiatives. There is no greater way that I know of to exhibit a grasp of project management greatest methods than certification as a Project Management Professional (PMP). Project supervisors who fulfill PMI’s conditions can attain the certification by using a PMP class or very similar PMP examination planning instruction and then composing the certification examination. Requirements that drop outdoors the realm of project greatest methods have been determined below and need to for section of your project approach.