IDEAL[cmm╱cmmi认证IDEAL_Model_for_spi].ppt

1、Soft Tech Development Inc.,1,Software Process Improvement,The IDEAL Model for SPI Programme Management,Soft Tech Development Inc.,Soft Tech Development Inc.,2,The IDEAL Model,Soft Tech Development Inc.,3,Initiating,Soft Tech Development Inc.,4,Initiating Critical Tasks,Identify Business needs and Dr

2、ivers for Improvement Build a SPI Programme Proposal Establish the Infrastructure Determine leverage points and barriers Define your goals,Soft Tech Development Inc.,5,Identify Needs and Drivers,Purpose The purpose of this step is to understand, from a management perspective, the key business and CM

3、M needs driving the requirement for the SPI Programme.,Soft Tech Development Inc.,6,Build a SPI Programme Proposal,Purpose The purpose of this step is to build a proposal for business unit directors that will explain what the SPI Programme is, why it should be initiated, what it will cost, how long

4、it will take to see results, and what approach is selected. The proposal should answer the questions, “What do we want to do?” and “Why do we want to do it?”,Soft Tech Development Inc.,7,Establish the Infrastructure,Purpose Maintain visibility for the programme. Facilitate and encourage information

5、sharing. Capture and retain lessons learned and improvements developed. Provide a support resource.,Soft Tech Development Inc.,8,Determine Leverage Points and Barriers,Purpose The purpose of this activity is to identify barriers and leverage points across the business unit that will have an impact o

6、n the SPI Programme, and to develop effective plans to ensure that the improvements made during the programme last.,Soft Tech Development Inc.,9,Define Your Goals,Purpose Clearly defined, measurable goals are necessary to provide guidance and to assist in developing tactics for improvement. They als

7、o allow objective measurement of the improvement results. Good goals are: few in number critical to the business unit highly visible,Soft Tech Development Inc.,10,Diagnosing,Soft Tech Development Inc.,11,Diagnosing Critical Tasks,Determine your baseline Plan for the baseline Conduct the baseline Dev

8、elop the report,Soft Tech Development Inc.,12,Determine Your Baseline,Purpose Your organisation has compelling reasons for undertaking a SPI Programme. The purpose of deciding how many and what type of baselines are to insure that the focus of the programme is linked to the business needs of the pro

9、jects or groups within the business unit.,Soft Tech Development Inc.,13,Plan for the Baseline,Purpose To accomplish the baselining activities requires a significant amount of co-ordination of people, data, facilities, training activities and support services. This activity may repeat some of the wor

10、k done when first initiating the SPI Programme. Sometimes this repetition is not needed, but often, the SEPG has different members than those who set up the original programme, and they will need to cover some of the same topics to develop their own understanding and strategy.,Soft Tech Development

11、Inc.,14,Conduct the Baseline,Purpose The purpose of conducting the baseline is to gather the factual information required to support the SPI Programme. The information gathered will present a snapshot of your organisations strengths and weaknesses relative to its software development and management

12、practices.,Soft Tech Development Inc.,15,Develop the Report,Purpose The Findings and Recommendations Report documents the baselining effort and provides a lasting representation of your organisations current state. The baselining team will develop a set of recommendations to go along with the findin

13、gs that were discovered during the baselining activity. The results of the baselines will be incorporated into the SPI Strategic Action Plan and reconciled with other existing and/or planned improvement efforts.,Soft Tech Development Inc.,16,Establishing,Soft Tech Development Inc.,17,Establishing Cr

14、itical Tasks,Review vision and business plans Determine key business issues Prioritize the activities Create specific, measurable goals Create an action plan,Soft Tech Development Inc.,18,Review Vision and Business Plans,Purpose This activity may repeat some of the work done earlier. Sometimes this

15、repetition is not needed, but often, the SEPG will have different members than those who initiated the local Software Process Improvement Programme, and they will need to cover some of the same topics to develop their own understanding and strategy.,Soft Tech Development Inc.,19,Determine Key Busine

16、ss Issues,Purpose Unless the SPI Programme is driven by the current business needs and understood and agreed to by management, it will likely be difficult to sustain the program over the long term. This is because it will be difficult to clearly demonstrate to senior management that the initiative i

17、s achieving real value for the business unit in business terms.,Soft Tech Development Inc.,20,Determine Key Business Issues,Purpose The key business needs have to be clearly defined, measurable, and understood to provide a common view to all those involved in improvement activities. Improvements sho

18、uld be selected based in part on their ability to satisfy these business needs. Not all process improvement activities can easily be linked to current business issues; however, the business issues identified should be used to prioritise improvement projects.,Soft Tech Development Inc.,21,Prioritize

19、the Activities,Purpose The baselines typically identify issues and provide recommendations based on a much broader consensus than may have been available before. These issues and recommendations serve to provide some guidance, and often, a prioritisation of actions. Publicly document an objective ap

20、proach to deciding which of the many competing improvement recommendations and actions will be launched and funded.,Soft Tech Development Inc.,22,Create Specific, Measurable Goals,Purpose This is done by incorporating the measurement of the current state of those goals and defining an aggressive but

21、 achievable improvement in those measures. For example: The measurement baseline established that 80 percent of current projects exceed their original cost and schedule estimates by more than 25 percent. The transformed goal could be to improve that measure such that 80 percent of all projects compl

22、ete within 10 percent of their original estimates,Soft Tech Development Inc.,23,Create an Action Plan,Purpose Now that all sections of the Strategic Action Plan are ready, the plan has been reconciled with the baseline results, and the goals transformed, the plan has to be put together, edited, and

23、finalised.,Soft Tech Development Inc.,24,Developing and Deploying,Soft Tech Development Inc.,25,Developing and Deploying Critical Tasks,Create a Tactical Plan Develop the Solution Pilot the Solution Develop Roll-out Strategy Package the Improvement Roll-out the Solution,Soft Tech Development Inc.,26

24、,Create a Tactical Plan,Purpose The purpose of this activity is to complete a tactical plan from a template that is supplied to the working group by the SEPG. The completed plan will be approved by the management board. The teams early efforts should be focused on narrowing the scope of the charter

25、to the specific improvement on which they will work.,Soft Tech Development Inc.,27,Develop the Solution,Purpose This is the step where solutions to the process identified earlier are developed. The purpose of this activity is to create solutions to the problems or processes that the business unit ha

26、s determined are necessary to meet the business needs of the unit.,Soft Tech Development Inc.,28,Pilot the Solution,Purpose Pilot projects are used to test out the solutions in both the process-centred and problem-centred approaches. The solutions will require some tailoring and refinement to fit th

27、em into projects across the organisation, and the pilots will help determine the tailoring needs and guidelines for the rest of the roll-out. Several pilots may be run for a solution.,Soft Tech Development Inc.,29,Develop Roll-out Strategy,Purpose Once the solution has been developed and piloted, th

28、e solution will be ready to roll out to the organisation. The roll-out plan will give guidance to the development projects that will be installing the process improvement. The plan will include what training they need what tools and methods to acquire installation steps information on how to get sup

29、port, etc.,Soft Tech Development Inc.,30,Package the Improvement,Purpose During solution development the working group has probably developed several intermediate products and artefacts. These must be collected into a package that can be turned over to the SEPG for long-term maintenance and support.

30、,Soft Tech Development Inc.,31,Roll-out the Solution,Purpose The purpose of this step is to install the proven solution across the organisation. The solution has been developed and proven by pilot testing with a project. Now the solution needs to be installed across all projects.,Soft Tech Developme

31、nt Inc.,32,Leveraging,Soft Tech Development Inc.,33,Leveraging Critical Tasks,Gather and Analyze lessons learned Revise Approach Review Sponsorship and Commitment Establish goals Develop next SPI Proposal,Soft Tech Development Inc.,34,Gather and Analyze Lessons Learned,Purpose The purpose of this st

32、ep is to: Ensure that all of the lessons learned data is available for review prior to starting the next cycle through the SPI programme. Ensure that the process you are using for SPI is the best that you can make it. You are looking for ways to make things better for all on this next cycle through

33、the programme.,Soft Tech Development Inc.,35,Revise Approach,Purpose The purpose of these activities is to make the next cycle through the SPI process more effective and efficient. Any enhancements you can make to the SPI process will allow you to make improvement changes more effectively, reduce re

34、sistance to change and allow SPI to proceed at a faster pace.,Soft Tech Development Inc.,36,Review Sponsorship and Commitment,Purpose As you have probably recognised during the previous cycle, sponsorship and commitment are critical to the success of SPI. As you did the first time through the Initia

35、ting phase, make sure you have sufficient sponsorship and commitment to support your SPI programme.,Soft Tech Development Inc.,37,Establish Goals,Purpose As when the programme was initiated, general, high-level goals need to be established. These goals will be made more specific during the action pl

36、anning activity later. Clearly defined, measurable goals are necessary to provide guidance and to assist in developing tactics for improvement. They also allow objective measurement of the improvement results.,Soft Tech Development Inc.,38,Develop next SPI Proposal,Purpose Until the strategic action

37、 plan is updated or recreated, the SPI programme needs some initial guidance. The purpose of this step is to create a plan to guide the programme up to the action planning steps. The activities will be very similar to those performed initially when the first proposal for SPI was created.,Soft Tech D

38、evelopment Inc.,39,Managing Critical Tasks,Organisation Planning Staffing Monitoring,Soft Tech Development Inc.,40,Organisation,Purpose As an SPI Programme gets under way, an infrastructure must be developed and put in place. This infrastructure will have the responsibility of providing guidance for

39、 the programme within the organisation In most cases there will be two components to the organisations programme infrastructure: A single, permanent Software Engineering Process Group (SEPG). A number of transitory Working Groups.,Soft Tech Development Inc.,41,Organisation - The SEPG,The Local SEPG

40、helps to sustain support for the programme in an environment of change builds and reinforces sponsorship nurtures and sustains the individual improvement activities An SEPG is not the implementer of the improvements. The role an SEPG is that of a facilitator, helping to guide the process improvement

41、 activity.,Soft Tech Development Inc.,42,Organisation - The Working Groups,These working groups are created to address a particular focus of the programme. For example, there could be a configuration management WG or a project planning WG addressing a specific software engineering domain. A WG is typically made up of those practitioners in the business unit who have knowledge and experience of the area under evaluation.,Soft Tech Deve