CMMIbased Business Analysis SEIR基于CMMI的业务分析西.ppt

CMMI-based Business Analysis Used to Support CMMI Huntsville Pilots A technique for connecting organizational issues with CMMI Process Areas Author: SuZ Garcia, SEI Presenter: Sandra Cepeda, CSSA Purpose of CMMI-based Business Analysis Provide those considering adoption of CMMI with enough information to make a reasonable first guess as to which Process Areas would be most helpful to them ASSUMPTION: the organization is looking for areas that will have early, visible, positive effects on the business’ performance, regardless of “level” designations. Two-Pronged Approach-1 Incorporate symptoms that are often seen when practices for a particular Process Area (PA) are missing into the Process Area education portion of an orientation session Get a 1st level reading for each PA using “thumb votes” that are recorded on a flip chart: Do the practices of this PA have High/Medium/Low impact on your business if they aren’t done well? (select only one) What level of problem are you experiencing in this topic/Process Area? High/Medium/Low When Requirements Management isn’t done well…. Symptoms: High levels of re-work throughout the project Requirements accepted by staff from any source they deem to be authoritative “Galloping” requirements creep Inability to “prove” that the product meets the approved requirements Why Should You Care? Because…. Lack of agreement among stakeholders as to what are the “real” requirements increases time and cost to complete the project You’re highly likely to deliver an incorrect or incomplete product Revisiting requirements changes over and over is a waste of resource highly visible to the customer Two-Pronged Approach-2 After education session is over, go back through the PAs, asking participants to write specific problems they are experiencing in their work related to each PA, one per sticky note. Post these sticky notes with the correct PA on flip charts, one PA per flip chart (consultant can help to allocate a particular to a CMMI issue