Friday, July 15, 2005, 12:30 AM - CMMI, CMMI Implementation, Technology, Technology Ideas
If you have read one of my first postings (CMMI first post ) you know I have been looking for the right tools for the job up till now. It seems the search is almost over and I have found a solution that will require little or no programming effort and will allow to achieve the goals set forth in the earlier posting.
The solution I have in mind combines the latest Office technology from Microsoft to deliver flexible and easy to use system.
1. SharePoint Services
2. InfoPath
3. SQL Server
4. Word
5. Excel
The idea is to organize the various artifacts in SharePoint to utilize its facilities for:
- organizing data in various views (grouped by, filtered, with only relevant information displayed)
- easy access via web interface
- provision for integration with Office, SQL Server and virtually all other MS Technology
- ability to version data
InfoPath provides means for editing structured data i.e. has advantage over Excel and Word with
- strong formatting i.e. users cannot involuntarily corrupt the format/schema
- validation facilities
- multiple views on data
- ability to sign documents electronically, important for documents that pass through review cycles
- ability to integrate with external data sources
SQL Server is of course providing facility for keeping data in a format that is easy to query, aggregate and analyze
Word and Excel are going to be used as report/result presentation tools.
The Big Picture
So far I had elaborated initial vision of the solution and only high level architecture.
In short we need:
1. Process Asset Library - holding different organizational process artifacts
2. Project Measurement Repository – this will hold the measurements we collect.
3. Per project repositories where project records will be held along with the projects defined processes
4. Additional data – these will be different lists with clients, contacts, suppliers, training & qualification records
The basic workflow for a contracted project will be:
1. Plan the project:
|
a. Input project summary info (planned cost, size, effort) b. Create Project Repository c. Create Project’s Defined process |
2. Summarize milestone i.e. allocated engineers, planned and actual milestone data (effort, # defects, # change requests)
3. Complete the project
|
a. Enter completed project actual values and lessons learned, problem root cause analysis b. Summarize the projects process specifics into the PAL as needed |
Well this is what I am working on now. Once I make the complete solution from technology and requirements I will post more details.
I am also going to look at what the MS Team system is like as it may be just too similar to what I am doing. I am a bit afraid that it is going to be too much Microsoft Centric and integrated with Visual Studio, which of course is not good for .Net free projects.
Thanks for reading :)
| [ 0 trackbacks ] | permalink |
( 3 / 6455 )Back
6474495
