This is a nice training on CMMI
http://www.tutorialspoint.com/cmmi/index.htm
Monday, 31 May 2010
Friday, 21 May 2010
Sunday, 2 May 2010
Lean Tools - Software Configuration Management
* Visual Control Charts:
For important / critical CIs - have visual control charts with information of: CI version, CI status (checked-in, out) ,Person working on CI, Changes being made to CI, Expected date of completion, % completion, storage location of CI, etc.
* 5S:
To establish configuration management process - as per my earlier blog
* DSM (Design Structure Matrix):
To understand the dependencies of CIs and complexity wrt - # of CIs having same cluster, # of people working on the same CIs, etc. Following are the other benefits you may achieve using DSM:
- Creating teams / modules - depending upon the CI cluster
- CI dependecies / Impact Analysis
- CI complexity - Higher the CI interaction, higher is the complexity
- Planning / scheduling of CI work
- CIs that can be developed in Parallel - Concurrent Engineering
Applying Lean principles in SCM
7 Wastes:
1. Overproduction - sharing the links of the folders containing latest version rather than sending the latest document thru emails
2. Waiting Time - Notification of check in, check out
3. Defects - Always the use of latest version (system not allowing wrong naming convention to be entered)
4. Overprocessing - Automation of : status accounting, configuration audits, Archiving of the old files
5. Transportation - Folder structure (storing files) , naming convention, indexing (path of files), sending links of folder containing latest version,
6. Inventory - status accounting and Indexing ( can be automated)
7. Motion - Indexing of files will help in searching of files, creating shortcuts / links to he files & folders
1. Overproduction - sharing the links of the folders containing latest version rather than sending the latest document thru emails
2. Waiting Time - Notification of check in, check out
3. Defects - Always the use of latest version (system not allowing wrong naming convention to be entered)
4. Overprocessing - Automation of : status accounting, configuration audits, Archiving of the old files
5. Transportation - Folder structure (storing files) , naming convention, indexing (path of files), sending links of folder containing latest version,
6. Inventory - status accounting and Indexing ( can be automated)
7. Motion - Indexing of files will help in searching of files, creating shortcuts / links to he files & folders
Lean in Configuration Management
- Using 5S principles in Software Configuration Management
1st S (Sort) -
Logical folder structure - based on way of working (PMI, Prince2, etc.)
Naming Convention
2nd S (Set in Order) -
Create a common share drive, sharepoint, CM Tool
3rd S (Shine) -
Status Accounting,
CI Indexing
4th S (Standardise) -
Trainings??
5th S (Sustain) -
Configuration Audits
1st S (Sort) -
Logical folder structure - based on way of working (PMI, Prince2, etc.)
Naming Convention
2nd S (Set in Order) -
Create a common share drive, sharepoint, CM Tool
3rd S (Shine) -
Status Accounting,
CI Indexing
4th S (Standardise) -
Trainings??
5th S (Sustain) -
Configuration Audits
Software Configuration Management Process
SCM process activities:
- Configuration Management Plan
1.1 CI Identification
1.2 Folder Structure
1.3 Naming Convention
1.4 Config activities: Configuration Audits, Status Accounting, - Acquiring CIs and creating baselines
- Control of Changes to Baseline
- Configuration Audits
Subscribe to:
Posts (Atom)