- Employment
- Services
- Software Documentation
- Quality and ISO
- Data Analysis and Reporting
- Research
- Achievements
- Recommendations
- Water
- Water Data
- She Has A Story For Everything
Software Development Process Management (SEI-CMM)
With minimal software-related training, I have programmed systems used for over ten years before off-the-shelf software could compete, developed successful software training programs where others failed and implemented software project management systems against significant pushback.
My employment at United Airlines was for the UA implementation of the Software Engineering Institute Capability Maturity Model (SEI-CMM) software development project management system. An overview of Level 2 can be seen here. My job was one of two IT Project Management Coordinators (tech support) for Primavera Project Planner (PPP), the software development project management software. Within six months, I was the prime contact for most of the software groups on PPP and interpretation of the many UA documentation requirements. To overcome resistance that had developed from the initial training, I created and presented new training programs to help development managers understand the system. Even though resistance was significantly reduced, the biggest problem was too much paperwork. While I could not do anything about it at UA, I did have ideas.
After 18 months at UA I was employed by ProBusiness Services for their SEI-CMM implementation. In many areas, development managers had created good processes but they were not being used. IT and Development were disconnected from each other as well as other departments. In SEI-CMM, the first area of change is within development. However, since other departments were eager to participate and contribute, the upgrading of processes was extended to IT, marketing, deployment, training and the user base. The implementation was going well until the dot-com bust when ProBusiness was sold to ADP. My fondest memory was a programmer walking into my office saying, "I am so glad you're here. For the first time, I actually know what I am supposed to be programming." That was the best job in my life.
I am still interested in improving development cycle processes.
On the next page is a list of documentation I either developed or edited for clarity and content. I have provided samples of those documents that were my own work.
My employment at United Airlines was for the UA implementation of the Software Engineering Institute Capability Maturity Model (SEI-CMM) software development project management system. An overview of Level 2 can be seen here. My job was one of two IT Project Management Coordinators (tech support) for Primavera Project Planner (PPP), the software development project management software. Within six months, I was the prime contact for most of the software groups on PPP and interpretation of the many UA documentation requirements. To overcome resistance that had developed from the initial training, I created and presented new training programs to help development managers understand the system. Even though resistance was significantly reduced, the biggest problem was too much paperwork. While I could not do anything about it at UA, I did have ideas.
After 18 months at UA I was employed by ProBusiness Services for their SEI-CMM implementation. In many areas, development managers had created good processes but they were not being used. IT and Development were disconnected from each other as well as other departments. In SEI-CMM, the first area of change is within development. However, since other departments were eager to participate and contribute, the upgrading of processes was extended to IT, marketing, deployment, training and the user base. The implementation was going well until the dot-com bust when ProBusiness was sold to ADP. My fondest memory was a programmer walking into my office saying, "I am so glad you're here. For the first time, I actually know what I am supposed to be programming." That was the best job in my life.
I am still interested in improving development cycle processes.
On the next page is a list of documentation I either developed or edited for clarity and content. I have provided samples of those documents that were my own work.
