Client
Login
IIS-Software Inc.
Capability Maturity Model - Software Quality Process Assessment
Following are some of the questions every software team here at IIS-Software Inc. must address:- What are our goals?
- What are the team roles and who will fill them?
- What are the responsibilities of these roles?
- How will the team make decisions and settle issues?
- What standards and procedures does the team need and how do we establish them?
- What are our quality objectives?
- How will we track quality performance, and what should we do if it falls short?
- What processes should we use to develop the product?
- What should be our development strategy?
- How should we produce the design?
- How should we integrate and test the product?
- How do we produce our development plan?
- How can we minimize the development schedule?
- What do we do if our plan does not meet management’s objectives?
- How do we assess, track, and manage project risks?
- How can we determine project status?
- How do we report status to management and the customer?
IIS - Team Software Process
The TSP provides team projects with explicit guidance on how to accomplish their objectives:
- Build self-directed teams that plan and track their work, establish goals, and own their processes and plans. These can be pure software teams or Integrated Product Teams (IPT) of three to about 20 engineers.
- Show managers how to coach and motivate their teams and how to help them sustain peak performance.
- Accelerate software process improvement by making CMM Level 5 behavior normal and expected.
- Provide improvement guidance to high-maturity organizations.
- Facilitate university teaching of industrial-grade team skills.
IIS - TSP launch process
To start a TSP project, the launch process script leads teams through the following steps:
- Review project objectives with management.
- Establish team roles.
- Agree on and document the team’s goals.
- Produce an overall development strategy.
- Define the team’s development process.
- Plan for the needed support facilities.
- Create a development plan for the entire project.
- Create a quality plan and set quality targets.
- Create detailed plans for each engineer for the next phase.
- Merge the individual plans into a team plan.
- Rebalance team workload to achieve a minimum overall schedule.
- Assess project risks and assign tracking responsibility for each key risk.
- Hold a launch postmortem.
In the final launch step, the team reviews its plans and the project’s key risks with management. Once the project starts, the team conducts weekly team meetings and periodically reports its status to management and to the customer.
In the four-day launch workshop, IIS - TSP teams produce:
- Written team goals
- Defined team roles
- A process development plan
- The team quality plan
- The project’s support plan
- An overall development plan and schedule
- Detailed next-phase plans for each engineer
- A project risk assessment
- A project status report
IIS - Management Team will develop design alternatives and selection criteria that consider the following:
- Life Cycle Cost.
- Technical Performance.
- Complexity.
- Robustness to product operations and the environment.
- Product expansion and growth.
- Cost drivers.
- Technology limitations.
- Sensitivity to construction methods and materials.
- Risk.
- Evolution of equipment drivers and technology.