Try This


1.

Use the Kano model to analyze a current development effort. Make a list of features and capabilitiesat a high leveland put them on an index card or Post-it Note. Use a large sheet to make the Kano model, and mount it on the wall. Next, attach the cards or notes to the appropriate area of the Kano model. How many features fall in the category of "delighters"? What percentage of features are "delighters"?

2.

In Chapter 10 we describe a single number that is a good measurement of customer satisfaction, called a "net promoter score." Compute the net promoter score for your customers. Create a simple survey that asks your customers how likely they are to recommend your product or service to a colleague on a scale of 010. What percentage of responses are 9s and 10s? This is your promoter percentage. What percentage of responses are 06s? This is your detractor percentage. Subtract the detractor percentage from the promoter percentage. Is the net score positive or negative?

3.

Make a list of all the programs or projects that are currently active. For each effort, write down the name of the current leader or leaders. How many leaders does each effort have? Have you written down someone who provides both a market and technical leadership for each effort? Is there any correlation between how well a project is doing and its market/technical leadership (or lack thereof)?

4.

Complete Teams: Do you have operations people on your team? Is someone from tech support regularly consulted when designing new features? Are testers involved in development right from the start? When do technical writers get involved? Are customers or customer proxies treated as full team members?

5.

Projects/Products: Are development efforts funded incrementally or all at once? What are the success criteria of a development effort? Are teams kept intact or do people regularly move to new teams? Do teams maintain the code they develop? Who is accountable for the business results of the money allocated to software development?




Implementing Lean Software Development. From Concept to Cash
Implementing Lean Software Development: From Concept to Cash
ISBN: 0321437381
EAN: 2147483647
Year: 2006
Pages: 89

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net