http://citconf.com/wiki/index.php?title=Enterprise_CI_Maturity_Model_-_and_how_to_go_insane&feed=atom&action=historyEnterprise CI Maturity Model - and how to go insane - Revision history2024-03-28T14:12:31ZRevision history for this page on the wikiMediaWiki 1.35.11http://citconf.com/wiki/index.php?title=Enterprise_CI_Maturity_Model_-_and_how_to_go_insane&diff=7801&oldid=prev203.167.202.226: New page: See http://www.anthillpro.com/blogs/anthillpro-blog/2009/05/05/1241542860000.html Also http://www.anthillpro.com/blogs/anthillpro-blog/2009/09/11/enterprise_ci_cultural_maturity.html for ...2010-06-26T06:10:26Z<p>New page: See http://www.anthillpro.com/blogs/anthillpro-blog/2009/05/05/1241542860000.html Also http://www.anthillpro.com/blogs/anthillpro-blog/2009/09/11/enterprise_ci_cultural_maturity.html for ...</p>
<p><b>New page</b></p><div>See http://www.anthillpro.com/blogs/anthillpro-blog/2009/05/05/1241542860000.html<br />
<br />
Also http://www.anthillpro.com/blogs/anthillpro-blog/2009/09/11/enterprise_ci_cultural_maturity.html for cultural component<br />
<br />
Ref: Microsoft Books: Rapid Development - Stee McConnel<br />
Ref: Dynamics of Software Dev<br />
<br />
Win 95 was released and CI tested all day. Vista was a 4 month cycle. Possibly why Vista sucked and '95 was such a success?<br />
<br />
Netscape open sourced Mozilla, but also some tools, including Tinder Box for compiling and testing on multiple (e.g. 14) hardware and software platform combinations.<br />
<br />
Tinder box was part of inspiration for Cruise Control project.<br />
<br />
Extreme Programming - Kent Beck - came out of C3 project at Chrysler. <br />
XP says "if it's good, do it all the time"<br />
e.g. peer reviews => pair programming<br />
Automated testing => CI and deployment<br />
<br />
2001 is when Cruise Control and Anthill came out.<br />
<br />
Manual CI - integrate work processes with others<br />
Automated CI - tools for fast feedback <br />
<br />
People are not consistent - not good at repetitive tasks e.g. checklists - doomed to failure. Computers better at this.<br />
<br />
<br />
Daily builds lead to 90% increase in productivity, 36% reduced bugs.<br />
<br />
The Chasm.... gap b/w early adopters and early majority (the latter only do things when their peers are doing it).<br />
<br />
CI got faster adoption than "agile" as it can be implemented by early adopters (devs) and does not rely on organisational culture change as did agile.<br />
<br />
Around 2005-2008 Agile crossed the chasm as it became something management saw as valuable and could bring value.<br />
<br />
Notice the change in language (book titles) over the years... <br />
2001 - scrum in s/w dev<br />
2004 - scrum for projects<br />
2008 - scrum in the enterprise<br />
<br />
Focus shifted from tech to wider biz.<br />
<br />
"Agile has a lean future" - lean business and less s/w dev.<br />
<br />
Ref: Book: 7 Lean Principals of s/w dev<br />
ref: Book: 7 wastes of s/w dev<br />
<br />
Manual processes become a bottleneck (wait = waste)<br />
Spaghetti diagramming to show analysis of bottlenecks.<br />
<br />
CI on $1/day<br />
Get the chicken from other dev (or wait for it).<br />
Get, merge, test, commit. Ring the bell and release the chicken.<br />
<br />
IMVU release 50x/day so need better than the chicken!! If tests pass, release to first cluster... etc.<br />
<br />
Cultural aspect needs to be added to CI maturity model.<br />
<br />
Goal of Lean is to reduce cycle time / faster feedback.<br />
<br />
Get the ops people into your scrum stand-ups.<br />
<br />
Ref: Book: The Secrets of Consulting <br />
Only promise 5% improvements!<br />
<br />
Combination of feedback on broken test (lose points, show red), with positive feedback (gold start on good commit). Non financial rewards.<br />
<br />
Cultural change requires some training to be considered - ongoing.<br />
<br />
Agitar Blog - extreme feedback devices (eg Lava lamps) - race the lava lamp (fix before it goes molten)</div>203.167.202.226