1 / 6

Gather Voice of the Customer (VOC) around the current development process

Gather Voice of the Customer (VOC) around the current development process. “People work in silos”. “No customer feedback”. “Less bugs”. “Products are late + over budget”. “Developers throw code over-the-wall to testers”. “We lose key people”. “Reward good employees”.

alain
Download Presentation

Gather Voice of the Customer (VOC) around the current development process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Gather Voice of the Customer (VOC) around the current development process “People work in silos” “No customer feedback” “Less bugs” “Products are late + over budget” “Developers throw code over-the-wall to testers” “We lose key people” “Reward good employees” “We don’t have the right mix of skills on our teams” “Too much governance” “We spin our wheels a lot” “Requirements are unclear +conflicting” “More feedback” “Too much waiting” “Our requirements suck” Use open ended questions to discover the participants obstacles and challenges

  2. Group the VOC data to identify the user needs for the new development process Ranked User Needs 8 Requirements 7 Adequate Resources 6 Quality 5 Better Testing 4 Staff Retention 3 Better Communication 2 Recognition & Rewards 1 Skilled People Requirements Quality Skilled People Adequate Resources Rank the user needs from high to low

  3. Derive the new development process requirements which fulfill the user needs Remember: requirements are solution agnostic.

  4. Rank the relationship between the user needs and the new process requirements 9 = strongly related, 3 = moderately related, 1 = weakly related

  5. Identify the process requirements that are critical-to-quality (CTQ) Highest scored requirements are CTQ for the process transition

  6. Develop measures which allow us to monitor the process transition. Happy Customers: 20% increase in sales in the first 6 months. 90% of all releases are validated by the customer. 75% of surveyed customers are “satisfied” or “very satisfied” with the release. Happy Employees: 10% less sick days than the previous 6 months. 65% of surveyed employees are “satisfied” or “very satisfied” Within Budget: 75% of projects within ± 20% initial estimates. On-Time Delivery: 80% of projects end within ± 15% of initial estimates for duration. “Bugless” Software: 70% of release candidates delivered to Quality will have ≤ 4 severity level “Critical” defects discovered. 65% of releases will have ≤ 1 severity level “Critical” defects reported by customers. What Agile practices allow us to meet our measures faster and sustain progress?

More Related