Warning: strpos() [function.strpos]: needle is not a string or an integer in /home/karaatanasov/public_html/index.php on line 17

Warning: strpos() [function.strpos]: needle is not a string or an integer in /home/karaatanasov/public_html/index.php on line 23

Warning: strpos() [function.strpos]: needle is not a string or an integer in /home/karaatanasov/public_html/index.php on line 29
Kiril's web log
CMMI first post 
Monday, June 13, 2005, 10:55 PM - CMMI, CMMI Implementation
Here I will be publishing items I stumble upon while implementing the quality management system of Tineo IT Labs using the CMMI guidelines. Tineo IT Labs is a new software service company, founded in February 2005, aiming to deliver top quality service in Europe and around the globe. Our belief is that using simple communication and business processes combined with sound engineering and management practices we can deliver high value service to our customers.
To get the job done we will be using the principles of CMMI. Initially I will be implementing quality management system to comply with ISO and CMMI level 2. It will for sure include a lot of level 3 stuff, but not all.
My first step is to get a solid foundation for the effort, including:

Templates/framework for documenting processes

It will be really nice to have format that easily supports hyperlinks, embedding of files, graphics and printing. In addition some automatic way to trace items between documents would be great particularly for process inputs and outputs.

Process Asset Library (PAL) system

The process asset library is the place where all data will be stored. Now my plans for what goes in to it are:

- organizational processes documentation classified by process area/intended audience/resource type

- tailored process documents by project type/customer

- process documents from previous projects including archived documentation, lessons learned and metrics summaries.

I am not sure if process documents of running projects should be contained in this library as they are live documents and will require less rigid control, plus they should be easily accessible to project members at all times.

Metrics systems

The metrics system is vital for us, as it will provide transparency to customers on the status of their projects.
The metrics database should be easily used by engineers daily it should be possible to integrate with 3rd party sources of data like issue tracking systems.
The end result should display project status screen to customers/managers indicating overall project state and summary of the individual project aspects.
At present I am reviewing one metrics system I downloaded from NASA's website

Come back for more!

  |  [ 0 trackbacks ]   |  permalink  |   ( 3 / 5684 )