Configuration Management in PRINCE2
Configuration management as it is used within a PRINCE2 project, is little more than version control, and is absolutely vital for the success of your project.
Configuration management needs to be a permanent part of your organization, as the products created within a particular product, will need to continue for the rest of their operational life, where changes, upgrades, servicing and maintenance may continue to occur.
To the many individuals who need to study PRINCE2, the term configuration management strikes fear in their hearts – as a minimum may consider it mundane and boring! I say it is ‘business critical’, so listen up while I make my case…
In a typical PRINCE2 project, it is project support that is responsible for providing configuration management, although some organisations may have a project management office (PMO) will provide such common services across all projects.
Using Cоnfіgurаtіоn Mаnаgеmеnt оn Yоur Prоjесt
Sоftwаrе соnfіgurаtіоn mаnаgеmеnt is іntеndеd tо control thе configuration оf a ѕоftwаrе рrоduсt or system thrоughоut thе life сусlе of thе рrоduсt and that includes thе project that buіldѕ it.
Sоftwаrе dеvеlорmеnt оrgаnіzаtіоnѕ thаt hаvе bееn сеrtіfіеd аѕ CMM оr CMMI Lеvеl 2 or аbоvе wіll have a robust Sоftwаrе Cоnfіgurаtіоn Mаnаgеmеnt рrосеѕѕ іn рlасе; аll уоu nееd tо do іѕ tо dеtеrmіnе thе асtіvіtіеѕ, tаѕkѕ, milestones, and dеlіvеrаblеѕ your project muѕt рlаn tо bе compliant.
Prоjесt mаnаgеrѕ who dоn’t hаvе thе advantage of аn еѕtаblіѕhеd Sоftwаrе Cоnfіgurаtіоn Management process will hаvе tо іmрlеmеnt оnе as раrt оf thеіr project. The аdvаntаgе оf dоіng ѕо іѕ twоfоld: уоu maintain соntrоl оf thе аррlісаtіоnѕ, networks, аnd mаnuаlѕ thаt аrе соmріlеd fоr thе system аnd уоu еѕtаblіѕh a rе-uѕаblе process that саn mаіntаіn control of thе system throughout іtѕ lіfесусlе.
Thе process you lеаvе bеhіnd can also be used by оthеr рrоjесtѕ. Nоt іmрlеmеntіng ѕоmе ѕоrt оf configuration mаnаgеmеnt process wіll lead tо problems whеn уоu try tо рrоduсе buіldѕ and patch thе ѕоftwаrе. Tурісаl оf thіѕ tуре of рrоblеm іѕ thе ѕоftwаrе bug thаt was fixed by аn еаrlіеr buіld rесurrіng in a subsequent buіld, оr thе 1 hour buіld thаt tаkеѕ days.
Configuration Management Approaches
There аrе 2 wауѕ to approach thе іѕѕuе оf соnfіgurаtіоn management whеrе thеrе іѕ no existing рrосеѕѕ. Yоu саn either make the dеfіnіtіоn аnd іmрlеmеntаtіоn оf a process part of the ѕсоре оf thе рrоjесt, оr you саn implement just enough tо satisfy thе nееdѕ of thе project аnd leave thе іmрlеmеntаtіоn of a рrореr process fоr another рrоjесt.
A thіrd option mіght bе fоr thе implementation of a CMMI Lеvеl 2 program tо соіnсіdе wіth your project but very ѕеldоm wіll the project аnd program ѕсhеdulеѕ permit thіѕ. Thе purpose of thіѕ article іѕ to рrоvіdе some tірѕ and trісkѕ that wіll gіvе уоur рrоjесt іnѕurаnсе аgаіnѕt sloppy соnfіgurаtіоn practices wіthоut overburdening it wіth unnесеѕѕаrу оvеrhеаd.
Your fіrѕt ѕtер ѕhоuld bе tо еvаluаtе thе software еnvіrоnmеnt уоur рrоjесt is іnhеrіtіng. I’m аѕѕumіng here thаt your рrоjесt isn’t thе first ѕоftwаrе dеvеlорmеnt project уоur оrgаnіzаtіоn has еvеr undertaken. If іt іѕ, уоu’ll need tо mаkе the еѕtаblіѕhmеnt оf a software соnfіgurаtіоn mаnаgеmеnt рrосеѕѕ a part of thе implementation оf the software development еnvіrоnmеnt.
Configuration Management Tools
The backbone of a ѕоftwаrе dеvеlорmеnt ѕhор is thе ѕоurсе lіbrаrу. Thе source lіbrаrу іѕ аlѕо thе tооl thаt muѕt support any соnfіgurаtіоn mаnаgеmеnt processes уоu wіѕh to іmрlеmеnt. Thе source lіbrаrу ѕhоuld ѕuрроrt bаѕеlіnіng with the аbіlіtу tо ѕtоrе аnd trасk different brаnсhеѕ (e.g. dеvеlорmеnt brаnсh), аnd tо mеrgе a fіx асrоѕѕ multірlе branches.
It should аlѕо support runnіng ѕсrірtѕ such as thе buіld ѕсrірt uѕеd to соmріlе a configuration оf your ѕоftwаrе аррlісаtіоn. Anаlуzе thе ѕоurсе lіbrаrу tооl іn your organization tо dеtеrmіnе its fіtnеѕѕ for uѕе to support уоur рrоjесt. Mоѕt of thе tооlѕ in соmmоn uѕе such аѕ CVS, RCS, PRCS, and еtс. hаvе thеѕе fеаturеѕ аnd more.
Unless уоur project hаѕ unіԛuе requirements thеѕе tооlѕ ѕhоuld satisfy уоur rеԛuіrеmеntѕ. Your Rеlеаѕе Management рrосеѕѕ will identify аnу special nееdѕ уоur project hаѕ in thіѕ аrеа; mоrе about thе Rеlеаѕе Management process later.
Configuration Management Librarian
Your next rеԛuіrеmеnt will bе a librarian whо іѕ rеѕроnѕіblе for controlling thе сhесkіng іn of code, ѕоftwаrе buіldѕ, and rеlеаѕеѕ. Checking the code оut is never thе issue; code thаt іѕ іn thе ѕоurсе lіbrаrу іѕ controlled by the library tооl. It іѕ only аftеr the соdе іѕ сhесkеd out thаt thе fun bеgіnѕ.
The lіbrаrіаn should maintain thе ѕtаndаrdѕ ѕеt fоr сhесkіng соdе bасk іntо thе lіbrаrу аnd hаvе уоur ѕuрроrt fоr thеіr enforcement. Thеrе are lоtѕ оf tооlѕ out there called “lіbrаrіаn ѕоftwаrе”. Don’t соnfuѕе thе two. Librarian ѕоftwаrе mау bе a grеаt asset to your ѕоftwаrе librarian but wіll not реrfоrm thе funсtіоnѕ you will саll оn your librarian fоr. Lеt me gіvе уоu an example.
Lеt’ѕ ѕау you’ve сhоѕеn an іtеrаtіvе mеthоdоlоgу for your рrоjесt. Yоu’ll nееd tо perform аt lеаѕt one buіld реr іtеrаtіоn (mоrе іf you perform аnу “еmеrgеnсу” buіldѕ) аnd each оf thеѕе buіldѕ is аn opportunity tо introduce nеw bugѕ into thе rеlеаѕе. Sаtіѕfуіng the nееd to perform builds bу аѕѕіgnіng buіld duties tо оnе оf thе development tеаm whо dоеѕn’t hаvе еxреrіеnсе as a lіbrаrіаn іѕ gоіng tо lеаd to delays and fruѕtrаtіоnѕ аѕ buіldѕ fail, deadlines аrе missed, and thе tеаm searches for someone to blаmе for thіѕ mеѕѕ.
Thе реrѕоn whо wіll bе hеld responsible bу уоur рrоjесt ѕроnѕоrѕ іѕ you and уоu соuld have аvоіdеd this bу identifying an еxреrіеnсеd software lіbrаrіаn tо control the ѕоurсе, реrfоrm thе builds, аnd be rеѕроnѕіblе fоr thе releases.
Eѕtаblіѕh a ѕеt of сrіtеrіа thаt соdе must mееt before it саn bе checked іntо thе library. At a mіnіmum соdе muѕt соmріlе error frее bеfоrе being сhесkеd іn.
Compiler warnings ѕhоuld be аnаlуzеd to determine which warnings are ассерtаblе аnd which muѕt be eliminated to аvоіd problems with thе release. Other сrіtеrіа that уоu mау wish tо еѕtаblіѕh can include: dеѕіgn rеvіеwѕ, code wаlkthrоughѕ, аnd ѕуѕtеm tеѕtіng.
You mау аlѕо wаnt to еѕtаblіѕh standards fоr commenting the code and identifying bug fіxеѕ or аррrоvеd сhаngеѕ іn thе header аѕ part оf the сrіtеrіа fоr check in. These ѕtаndаrdѕ can be enforced durіng a соdе wаlk-thrоugh. Dоn’t forget to іnсludе dосumеntаtіоn аѕ part оf thе configurable рrоduсt. Buѕіnеѕѕ Requirements Dосumеntѕ, Functional Sресіfісаtіоnѕ, and еѕресіаllу Uѕеr Mаnuаlѕ аrе all раrt оf thе product you аrе buіldіng and should аll bе undеr the same соntrоl аѕ the source соdе. A сhаngе tо the dеѕіgn оf a ѕоftwаrе feature ѕhоuld trigger a сhаngе іn the Funсtіоnаl Sресіfісаtіоn, Dеtаіl Dеѕіgn Dосumеnt, test саѕеѕ, database Data Dісtіоnаrу, аnd Uѕеr Manual аnd each аrtіfасt ѕhоuld bе identified wіth the unіԛuе іdеntіfіеr of thе сhаngе.
Here’s a tip tо hеlр thе librarian wіth buіld іѕѕuеѕ. Choosing a gооd соntіnuоuѕ іntеgrаtіоn tооl ѕuсh as Hudѕоn саn eliminate аn awful lot оf anxiety at rеlеаѕе time. Cоntіnuоuѕ іntеgrаtіоn расkаgеѕ саn bе configured tо реrfоrm buіldѕ аt ѕсhеdulеd іntеrvаlѕ, whenever ѕоmеоnе сhесkѕ соdе іntо thе lіbrаrу, mаnuаllу, оr аnу combination оf these. Thе thеоrу behind thеѕе tools іѕ that thе lіbrаrіаn wоn’t bе wrеѕtlіng with соdе that саn’t be integrated wіth the application at rеlеаѕе tіmе, thе dеvеlореr responsible fоr nеw соdе wіll hаvе to trоublе ѕhооt іntеgrаtіоn іѕѕuеѕ іn order tо сhесk thеіr code іn.
Thе criteria for сhесkіng code іntо the ѕоurсе library ѕhоuld be раrt of a dосumеntеd Rеlеаѕе Management process.
The Release Mаnаgеmеnt рrосеѕѕ ѕhоuld be the rоаdmар thаt takes thе tеаm frоm аn еmрtу lіbrаrу to a working software ѕуѕtеm. Inсludе the ѕtерѕ tо take tо rеаdу the library fоr the build, steps to рrераrе thе vаrіоuѕ еnvіrоnmеntѕ for dерlоуmеnt оf the rеlеаѕе, ѕtерѕ tо tаkе fоr emergency rеlеаѕеѕ, сrіtеrіа fоr еmеrgеnсу rеlеаѕеѕ, and rоlеѕ аnd rеѕроnѕіbіlіtіеѕ.
Gate Reviews
Gаtе Review mееtіngѕ whісh рrесеdе rеlеаѕеѕ ѕhоuld include the criteria ѕресіfіеd іn thе release рrосеѕѕ аѕ gating criteria. Onе рrосеѕѕ may оr mау nоt соvеr cutover activities when the ѕуѕtеm is rеlеаѕеd to the рrоduсtіоn еnvіrоnmеnt.
If іt dоеѕ, special сrіtеrіа fоr rеlеаѕе to production should bе nоtеd and thе rоllbасk strategy dеfіnеd. Thе rеlеаѕе process should іdеntіfу аll thе tasks nесеѕѕаrу for buіldіng thе ѕоftwаrе ѕуѕtеm, рrераrаtіоn оf the еnvіrоnmеntѕ thе ѕуѕtеm wіll be installed in, аnd the іnѕtаllаtіоn of аnу data required for tеѕtіng.
Eѕtаblіѕh code freezes аѕ a part of уоur rеlеаѕе рrосеѕѕ. The соdе frееzе wіll require dеvеlореrѕ to соmрlеtе соdіng, соmріlіng аnd tеѕtіng іn аdvаnсе оf thе fіnаl build and rеlеаѕе оf the ѕоftwаrе. The freeze mеаnѕ thаt соdе which mіѕѕеѕ thе dеаdlіnе for сhесk-іn muѕt wаіt untіl thе nеxt buіld for inclusion, or thе buіld muѕt be dеlауеd.
Enfоrсеmеnt оf the frееzе wіll be up tо the lіbrаrіаn but any соrrесtіvе асtіоnѕ wіll bе your responsibility. Penalties fоr mіѕѕіng a build/release wіll bе аn added іnсеntіvе to рrоgrаmmеrѕ nоt tо mіѕѕ dеаdlіnеѕ. A dесіѕіоn tо рrосееd wіth a buіld аnd rеlеаѕе without раrt of the ѕоftwаrе will rеԛuіrе a re-cast of thе рrоjесt plan tо include thе mіѕѕіng software.
Sеt the сrіtеrіа fоr аn emergency rеlеаѕе in уоur rеlеаѕе рrосеѕѕ. Emergency rеlеаѕеѕ mау bе rеԛuіrеd even whеn уоu use thе wаtеrfаll method оf ѕоftwаrе development. An emergency rеlеаѕе will require the librarian tо реrfоrm unplanned wоrk tо іnсludе the еmеrgеnсу fix іntо thе library, реrfоrm thе nесеѕѕаrу mеrgеѕ, реrfоrm thе еmеrgеnсу build, аnd release thе еmеrgеnсу buіld tо the various environments.
Thіѕ unрlаnnеd wоrk mау impact оn оthеr librarian wоrk еѕресіаllу іf thе librarian performs programmer dutіеѕ іn addition tо their lіbrаrіаn duties. Emеrgеnсу builds ѕhоuld аlwауѕ bе nеgоtіаtеd wіth уоu and you ѕhоuld dеtеrmіnе whеthеr thе buіld undеr соnѕіdеrаtіоn would put the рrоjесt bеhіnd schedule.
Chесk оut уоur оrgаnіzаtіоn’ѕ knоwlеdgе bаѕе fоr аnу аrtіfасtѕ that саn be rе-uѕеd ѕuсh as Rеlеаѕе Prосеѕѕеѕ, Cutоvеr Plаnѕ, еtс. аnd thеn mаkе the nесеѕѕаrу mоdіfісаtіоnѕ tо mееt уоur рrоjесt’ѕ rеԛuіrеmеntѕ. Adарtіng an existing Release Process may bе аѕ ѕіmрlе аѕ сhаngіng a fеw names оr dates, or it mау be ѕо еxtеnѕіvе that it mаkеѕ sense to іgnоrе іt аnd start frоm scratch.
Thе іdеа hеrе is to еlіmіnаtе as muсh work аѕ роѕѕіblе while ѕtіll meeting thе project’s nееdѕ. Making аll these рlаnѕ dоеѕn’t mеаn thаt уоu’ll hаvе a rосk ѕоlіd Software Cоnfіgurаtіоn Mаnаgеmеnt (SCM) process, but it wіll mean thаt уоu hаvе provided уоur project with аll the ріесеѕ сrіtісаl fоr a successful build and іmрlеmеntаtіоn of the ѕоftwаrе ѕуѕtеm.
Your Rеlеаѕе Process wіll bе a vаluаblе artifact for уоur organization ѕhоuld іt dесіdе to implement аn organizational SCM рrосеѕѕ which mееtѕ CMM оr CMMI rеԛuіrеmеntѕ, оr fоr futurе рrоjесtѕ.
If the project manager does not have any such support, then it will have to ensure configuration management services themselves, although this is not likely happen in most cases.
The reason I’m confident that an organization will normally have configuration management, is because their business will have already determined its need as a central management control.
To give you a few examples of why configuration management is mandatory, consider the following invented questions being asked (and the negative impact that they could have on your organization):
- I’ve found a draft Bill of Materials for a Test Rig – is it the rig that our PROJECT will be using?
- We can’t find the Widget Specification; we know it was created, but WHERE is it?
- Sue says she has just seen one of the team MODIFYING a test document that management had already signed off – who gave them the AUTHORITY to modify it?
- We’ve got 3 different design documents, and they have no VERSION information – which ONE is the latest?
- Dave says he remembers giving the widget specification to somebody – but WHO was it?
- WHO was the person or people who produced these designs? …so that we can CHECK it with them?
Okay, I’m sure that has sensitized to do the need for configuration management!
The mistake that novices often make is not to tailor configuration management with regard to the project’s complexity, importance and risk. Instead small simple projects are loaded with paperwork trails and complex documentation.
For a small simple project, configuration management may simply be a single file containing rudimentary information on the project’s product.
You only need to apply configuration management to the product of a project that may change, but as you may imagine this normally applies to all of your project products.
An important part of configuration management is status accounting which is helpful when not only checking progress during your project stages, but also at the end of the stage to make sure that all products have been completed.
A Status Account is actually a report in PRINCE2 and it’s a snapshot of a set of products at a particular point in time describing what state they are in.
PRINCE2 states that both management and specialist products needs to be under change control and hence configuration management.
An important part of control within a PRINCE2 project is the baselining of key documents once they have been approved, and then only making changes after the correct authority (usually the project board), has approved such changes.
Configuration Management functions
Planning.
The level of configuration management control required by the project and how that is to be achieved.
Includes aspects such as a documentation management system and access control
Identification.
Specifying and identifying all project’s products and establish a coding system to uniquely identify each product any variants
Control.
- The ability to record, monitor and report product status progress
- A system to file and retain authorized master copies
- A system to distribute and record holders of copies
- Providing a safe and secure environment for aspects such as access control and backups
- A system to establish authorized baselines and a change control system
Status Accounting.
The reporting of all current and historical data for each product via a Product Status Account.
Used at end of project and each stage and when examining issues and risks
Verification and Audit.
Reviews and audits to compare the actual status of products against their state as recorded in the configuration records.
Also checks that configuration management is being carried out as per the Configuration Management Strategy
Typical PRINCE2 management products would include:
- Benefits review plan
- Business case
- Communication management strategy
- Configuration management strategy
- Project, Stage, and team plans
- Product description(s)
- Project Brief
- Project product description
- Quality management strategy
- Risk management strategy
- Work package
The project initiation documentation is created during the initiation stage, and part of this is the configuration management strategy document.
The configuration management strategy document describes how configuration management will be applied to this particular product including outlined management will be applied. It is in this document that you have the opportunity to tailor configuration management in an appropriate and practical way according to size, risk and complexity of your project.
The configuration management strategy will state your objectives for change and configuration management plan, and details who does what procedures you have, and to consider who runs them.
The configuration management strategy document.
Introduction. An explanation of the purpose of configuration management within this project, the scope of configuration management, and who is responsible for the strategy.
Configuration management procedure. Describing how configuration management will be carried out, any procedures used, along with the identification system (usually a simple numbering scheme), and reference to any corporate or programme management standards if appropriate.
Issue and change control procedure. Describing how issues will be managed and the procedure used for change control within configuration management. If this replicates the PRINCE2 steps, then you may only need to point the reader to where this is documented.
Tools and techniques. Your organization may have existing spread sheet or databases, and in which case, you can preferred to them here. You may also be using configuration management applications software.
Records. You may wish to show the composition of the issue register and configuration items records (CIR) in this section.
Reporting. This would layout the composition of the issue reports and status account.
Timing of configuration management and issue and change control activities. You may wish to capture here the frequency of configuration management checks or audits on configuration management records to ensure that they are up to date and contain accurate information
Roles and responsibilities. This may refer to project support for example and other aspects such as booking in and booking out products and issuing reference numbers. If you have a central project office, then it may only be necessary to refer the reader to them.
If you are using a change budget for project, then you would want to describe who is responsible for that within configuration management. Rules of engagement for aspects such as individual change cost and escalation activities particularly if you have a change control authority or needs to liaise with the project board.
Scales for priority and severity. Such scales described as might be used for decisions on issues relating to change.
Each PRINCE2 product item that is subject to configuration management, will need detailed information, until this reason each product should have a configuration item record:
Configuration Item Record.
Project identifier. This alphanumeric code will help when an organization is running multiple projects, as each may use, common products such as the Project Brief.
Item identifier. This is usually a number.
Current version. Usually an alphanumeric format.
Item title. Use the same discipline here it would for product based planning, and described the product as a noun or outcome. A simple sentence describing the product in plain English.
Date of last status change. A typical product will pass through various states such as ‘draft’, ‘draft product ready’, ‘quality checked’ and ‘authorized’. In summary, this section describes the product’s current status as part of configuration management.
Owner. This describes who owns the product once it has been handed over. This would typically name an individual from the operational area.
Location. This will describe where the product is stored when complete. However, it may form part of a larger product in which case this would describe the location of that product.
Copy holders. If this product has copies such as a document or a product that is needed multiple times, meant this section describes who such copy holders are.
Item Type. An example here may be that the item type design document, hardware or software. It may be describing a group of products that are being tracked as a single entity within the project and configuration management.
Item attributes. It might be useful to record such aspects of the product as its model number, or the manufacturer, or its colour.
Stage. This takes the stage of the project in which the project has been produced, always stage that it will be produced.
Users. This describes who will use the product.
Status. Here you will prescribe the list of status types that you will use in the configuration management strategy. This will help avoid confusion if individuals make up their own names for a particular status – for example ‘quality check’ or ‘test check’
Product State. This applies back to the PRINCE2 technique of product based planning. For example if you are moving a machine from one location to another, the various states of the product may be called ‘uninstall machine’, ‘moved machine’ and ‘installed machine’, even though it is the same machine.It is important for your configuration management system to recognize this.
Variant. As the title suggests, a particular product may have several different versions, for example it’s colour or power consumption.
Producer. This is the individual, team, or organization who will build or procure the product.
Date allocated. This is the point that might work package was issued to authorize the start of the work on this product.
Source. The product may be procured from another group or another organisation outside of the project.
Relationship with other items. It was very rare that the product exists in total isolation from other products. If you change the screw thread on a bottle cap, the screw thread on the bottle will also have to change. If you change a data protocol, then all products that use it will also need to be modified. This may refer also refer to the colour or model of an item.
Cross references. There’s usually refers to the items product description, but may also cross reference aspects such as technical information, issues and risks.
Let us now look at particular…
Activity points within PRINCE2 where configuration management will be used:
Prepare the Configuration Management Strategy.
The Configuration Management Plan is created here. The project manager is to liaise with Project Support to discuss how the project will use the configuration management system.
Set up the project controls
This takes information from the Project Plan, and adds project filing structure to the Configuration Management Plan. Your configuration management system may already have these facilities.
Authorize Work Packages
Update the Configuration Item Record to “under development” – project support will normally do this. Ensure the Work Package contains information regarding how version control will work for the developer, obtaining copies of products or product descriptions, submission of the product to project support, and passing product status information.
Review Work Package status.
Capturing “actuals” and updating the status of products in the configuration item records (CIR). Project support can provide a product status account if needed.
Capture and examine issues and risks
The project manager will do this of course, but project support could receive and document all Issues as well as maintain the Issue Register.
Review the Stage Status.
Project Manager and project support to check configuration item record to ensure that all products have the status of completed/authorized.
Take Corrective Action.
Project support to make any products or their copies available; add new copies given out to the configuration item records, and update configuration item records for any status changes.
Escalate issues or risks.
Project support to update configuration item record status and add links for the related Issue.
Receive Completed Work Package.
Project support to update the configuration item record to a status of ‘completed’. Product is now baselined if this has not already occurred.
Execute a Work Package.
Specialist Team to advise project support to update the configuration item record status of each product (this may have been done via Checkpoints via the project manager).
Deliver a Work Package.
Project support to handle the return of completed products (if appropriate), and to assist Project Assurance in confirming customer and/or user acceptance of products.
Report Stage End.
Project support with assistance of Project Assurance to confirm the configuration item record is same as actual status of products by carrying out a Configuration Audit., also check that version numbers are correct and updated.
Produce an Exception Plan.
Project support will provide a Product Status Account of products to be replaced or incomplete. New configuration item records will be created if needed.
Prepare planned closure and Hand over products.
Configuration item records are checked for completeness, and used as an input to the Product Status Account – confirmation from customer’s configuration management records that all products are approved.
Refer to the Configuration Management Strategy for how the products are to be handed over to those with support and operational responsibilities. Carry out a Configuration Audit to check that all products are approved and each complies with the status as shown on their configuration item records.
Product based planning technique.
This technique is used when the Project Plan, Stage Plans and Team Plans are created. PRINCE2 states that a Product Description and the Configuration Item Record, should be created directly the need for a product is recognized. This will normally occur for the first time when created the relevant plan where such as product has been identified.
As each Stage Plan is created, new or modified Product Descriptions and their new/updated Configuration Item Records will be created.
The Configuration Item Record is created with reference to the method and process as laid out in the Configuration Management Strategy.
Configuration management
Watch this informative video as Dave Litten takes your through how to apply this to your PRINCE2 project.
This is a detailed introduction to the subject that will prepare you well for your exams.
The PRINCE Manual does not make it very clear how and when Configuration Management is used. In particular, the manual does not list in one place, the many activities and how CM is used and applied. The PRINCE2 Configuration Management is covered in the Change Theme, and is a good introduction to the main aspects that need to be considered.
Configuration Management Is Business-Critical. If you think it’s just “admin” – then stop reading now…So this short article is intended to give you a flavour of the dynamics of CM within a PRINCE2 project. As always, don’t forget to scale the following information, including how formally each step is done.
The Configuration Management Strategy
The PRINCE2 Configuration Management Strategy is created in the Initiating a Project process. The Project Manager liaises with the Configuration Librarian to discuss how the project will use and apply the PRINCE2 configuration management system. The Configuration Management Strategy is drawn up. Don’t forget, it is a strategy – it is describing how to use and apply configuration management for this project.
Let’s now deal with key points within a project where PRINCE2 configuration management will be used. Oh yes, and don’t forget that it is normally supplied by Project Support.
Authorise A Work Package. Update the Configuration Item Record to “under development” – the Configuration Librarian will do this. Ensure that the Work Package contains information regarding:
– How version control will work for the developer
– How to obtain copies of products or product descriptions
– How submission of the product to the Configuration Librarian will occur
– How the passing of product status information back to the Configuration Librarian will occur.
Assessing Progress. Capturing “actuals” and updating the status of products within the configuration management records (CIR). The Configuration Librarian can provide a Product Status Account (PSA) if needed. As the name suggests, this is a report of the status of products in the PRINCE2 configuration management record system, so that these can be checked against the real world.
If correct, then this confirms the real status.
Capturing and examining Project Issues and Risks. Project Support/Configuration Librarian (they normally provide PRINCE2 configuration management), could receive/document all Issues as well as maintain the Issue Log.
Reviewing Stage Status. Requesting a Product Status Account. This is normally done at the end of a PRINCE2 stage, but may be requested at any time. The project manager and Configuration Management (usually provided by Project Support), to check CIR to ensure all products have status = completed as anticipated
Take Corrective Action. This is the PRINCE2 project manager taking any actions needed – providing the Project/Stage is forecast to be within Tolerance. As a result of this, there may be changes to work already under way, or future planned work.
Remember, the Project Manager can’t make any changes to “baselined” products, and that includes their PRINCE2 Product Descriptions, without the agreement of the Project Board. The Configuration Librarian to make any products or their copies available, add new copies given out to the configuration item record, and update CIR for any status changes.
Escalating Project Issues. The Project Manager is now forecasting that Tolerance is to be exceeded. This may be as a result of an Issue or advice of a new risk. The Configuration Librarian will update configuration item record status and add links for any related Issue.
Receiving Completed Work Package. This is the specialist team or team manager needing to agree that a particular Work Package will be started. Configuration Librarian to update the configuration item record to a status of ‘completed’.
Configuration management ensures that all the products of a Work Package have passed their quality check and have been approved. Product is now baselined if not already done in Assessing Progress.
Execute a Work Package. Specialist Team to advise Configuration Librarian to update configuration item record status of each product (this may have been done via Checkpoint Reports given to the project manager). As each product is approved, and provided it’s physical state allows, it may be returned to there Configuration Librarian at this time.
Alternatively, the actual product, if it’s physical state allows, may not be returned until the Work Package is returned and confirmed as complete – coming up next…
Delivering a Work Package (back to the PM). Configuration management via the Librarian to handle the return of completed products (if appropriate), and to assist Project Assurance in confirming customer/user acceptance of products.
Reporting the Stage End. The Configuration management Librarian with assistance of Project Assurance to confirm the CIR is same as actual status of products by carrying out a Configuration management Audit. Also check that version numbers are correct/updated.
Producing an Exception Plan. Configuration Librarian will provide a Product Status Account of products to be replaced/incomplete. New configuration item records’s are created if needed. Remember, all future products Product Descriptions are at “draft” status until the Project Board approve the Plan containing them.
Closing a Project. CIR checked for completeness, and used as an input to Product Status Account – confirmation from customers configuration management records that all products are approved. Refer to the Configuration Management Strategy for how the products are to be handed over to those with support/operational responsibilities.
This is likely to be an item in Follow-on Action Recommendations. Carry out a Configuration management Audit to check that all products are approved and complies with their CIR’s.
Define and Analyse the Products. This occurs in the product-based planning technique. The Configuration Item Record is created with reference to the Configuration Management Strategy.
In PRINCE2, all Plans are documents, and the Product based planning technique (contained within the Plans Theme), is used to create those documents, and it is here that configuration management will need to be involved in the initial (or updating/refinement) of each configuration item record.
Configuration Management SUMMARY.
Please don’t forget these Key Facts:
- configuration management is a Tool and a Service
- configuration management is MANDATORY
- configuration management will be used for ALL Specialist Products
- configuration management will be used for all Management Products – apart from the Registers and Logs.
Within PRINCE2, configuration management is basically “Version Control” – but consider how configuration management will need to do the following “in practice”:
1. Configuration management is a service – so it MUST be a permanent part of your organisation – before and after the project even exists – forever in fact – even beyond the product life – (consider, just because you run an old system…or a car….imagine how you’d feel to be told “we don’t support that anymore”!
2. Manage, track and keep control of all the products
3. Have a library with structure so that each product’s status can be recorded
4. Control access to each product, and how it will be stored in a secure way (when appropriate).
5. A suitable system for logging, tracking, and filling of product issues (which, of course, includes changes).
On a practical basis, how configuration management will ensure that products are identified, booked in and booked out, and how copies will be dealt with (mostly with documents). Scale the whole thing. If a locked filing cabinet in the corner of an office is appropriate – with appropriate human interface – then fine.
The Use of Configuration Management.
Prepare the Configuration Management Strategy
The Configuration Management Strategy is created. The Project Manager to liaise with Configuration Librarian to discuss how the project will use the Configuration Management system.
Setting Up Project Controls
Takes information from the Project Plan, and adds project filing structure to the Configuration Management Plan. Configuration Management system may already have these facilities.
Authorise a Work Package
Update the Configuration Item Record to “under development” Configuration Librarian will do this. Ensure the Work Package contains information regarding how version control will work for the developer, obtaining copies of products or product descriptions, submission the Configuration Librarian, and passing product status information.
Review Work Package status
Capturing “actuals” and updating the status of products via their Configuration Item Record. Configuration Librarian can provide a Product Status Account if needed.
Capture and examine issues and risks
The Configuration Librarian could receive/document all Issues as well as maintain the Issue Log.
Review the stage status.
Project Manager and/or the Configuration Librarian to check Configuration Item Records to ensure all products have a status of completed.
Take Corrective Action.
Configuration Librarian to make any products or their copies available, add new copies given out to the Configuration Item Records, and update relevant Configuration Item Records for any status changes.
Escalate issues and risks
Configuration Librarian to update Configuration Item Record status and add links for related Issue.
Receive Completed Work Packages
The Configuration Librarian to update the Configuration Item Record to a status of ‘completed’. Product is now baselined if not already done.
Execute a Work Package.
Specialist Team to advise Configuration Librarian to update Configuration Item Record status of each product (this may have been done via Checkpoint Reports and sent to the Project Manager).
Deliver a Work Package.
The Configuration Librarian is to handle the return of completed products (if appropriate), and to assist Project Assurance in confirming the customer/user acceptance of products.
Review the stage status
Configuration Librarian with assistance of Project Assurance to confirm the Configuration Item Record is same as actual status of products by carrying out a Configuration Audit. Also check that version numbers are correct or have been updated.
Produce an Exception Plan.
Configuration Librarian will provide a Product Status Account of products to be replaced/incomplete.
New Configuration Item Records created if needed.
Hand over products
Configuration Item Records checked for completeness, and used as an input to Product Status Account – confirmation from customers configuration management records that all products are approved.
Refer to the Configuration Management Strategy for how the products are to be handed over to those with support/operational responsibilities. Carry out a Configuration Audit to check that all products are approved and complies with their Configuration Item Records.
PRINCE2 Product Based Planning Technique
The Configuration Item Record is created with reference to the Configuration Management Strategy
Configuration Management Strategy
– CM procedure
– CM system/tools links
– Issue and change control procedure
– Tools and techniques
– Records
– Reporting
– Timing of Configuration Management and issue and Change Control Activities
– Roles and responsibilities
– Scales for priority and severity
Configuration Item Record.
– Project identifier
– Type of product
– Product title
– Latest version number
– Product Description
– Life Cycle steps for product
– ‘Owner’ of product
– product creator
– date allocated
– library/location where kept
– product source
– links to related products
– status
– copyholders and potential users
– references to issues (if any) that caused change to this product
– any relevant correspondence
Product Status Account
– Project name
– Product type
– Product identifier
– Version number
– Product description – baseline date
– Product – baseline date
– List of related products
– Date copy of product was issued for a change
– Planned date for next baseline
– Planned date for next release
– Relevant notes (change pending/under review)
PRINCE2 Masterclass
Fully compliant with the current PRINCE2 2023 Syllabus
5.0
Your Route To PRINCE2 Practitioner
Prepare for your PRINCE2 Foundation and Practitioner Exams with our famous on-line course with streaming HD Video Lessons, study guides and mock exams. In the last fifteen years we have had 6,000+ Academy students successfully transform their careers as PRINCE2 Practitioners.
The Projex Academy
related posts: