I introduced XP in the retail bank Internet group (as a six sigma project)
to solve many of the problems I saw (intra-team communications issues, long
release cycles, low customer satisfaction, etc.), and had the support of
senior executives on both tech and business. But there was a concern that
this would hurt the organization's objective to get to CMM L2 by their
deadline.
So once we were up and running (about six months after getting started,
with the help of Kent Beck and ThoughtWorks), we had our internal CMMI lead
appraiser do a baseline assessment. He was quite surprised of the results
... of the 25 or so CMMI baseline assessments he had previously done (North
America and Asia), he never had a team score as high as the XP team did.
And it certainly wasn't because of how well we followed our documented
process ... we didn't have any documented process. It was because the
discipline of XP met most of the goals of the L2 Process Areas (and got us
well on the way to L3).
We would probably have been the first group to L3 (continuous) if the
effort hadn't been derailed by the BankOne merger. (But that's another
story, best told over a beer.)
And our results? We showed a 60% drop in overall defects (80% drop in
critical defects), and 45% reduction in development costs (comparing 6 XP
releases with 4 non-XP projects of similar size, normalized by QA test
cases).
BJ
Ron Jeffries <ronjeffries@...>:
On Sunday, November 13, 2005, at 8:54:28 AM, Bob.Jarvis@... wrote:
> While CMMI might be in conflict with values of XP, when we introduced XP
at
> Chase, our ability to easily get to CMMI L2 made it easier for the CTO to
> continue funding the effort.
Tell us more, please. Why, how, and so on.
Ron Jeffries
www.XProgramming.com
There's a difference between righteous anger and just being crabby.
--Barbara Richmond
To Post a message, send it to: extremeprogramming@eGroups.com
To Unsubscribe, send a blank message to:
extremeprogramming-unsubscribe@eGroups.com
ad-free courtesy of objectmentor.com
Yahoo! Groups Links