Even if you don’t play chess, you are likely to enjoy Gary Kasparov’s recent article The Chess Master and the Computer. Gary writes on the complicated subject of intelligence and the human mind in a clear, jargon free language. I would dare say his article is as incisive as the way he plays chess. For the Agilist, (and for anyone who takes interest in knowledge work), Gary cuts to the heart of the matter recounting the following episode: In 2005, the online chess-playing site Playchess.com hosted what it called a “freestyle” chess tournament in which anyone could compete in teams with other players or computers. Normally, “anti-cheating” algorithms are employed by online sites to prevent, or …
Posts Tagged 'process'
In his unique style, Hillel Glazer clears up confusion — while perhaps even standing on one leg — around CMMI in this video. He says it’s what to improve, not how, and that every CMMI practice avoids a risk so you can use the practices as guides to finding where you have issues. Agile-and/versus-CMMI has been a topic of lots of debate recently here at Cutter. For example, Hillel wrote in “Agile vs. CMMI: The Debate Goes On“: Jens Coldewey’s Advisor “Why ‘Agile vs. CMMI’ Leads Down the Wrong Track” rightly argues that “Agile vs. CMMI” is not the right direction to go. However, he assumed a particular (and common) perspective about CMMI and in doing …
Below is the detailed outline for my August 8, 1:30-5:00PM Technical Debt Workshop in Agile 2011. I look forward to meeting you and interacting with you in the conference before, during and after this workshop! Best, Israel Technical Debt: Assessment and Reduction Part I: Technical Debt in the Overall Context of the Software Process A Holistic Model of the Software Process Two Aspects of Output Three Aspects of Technical Debt Five Aspects of Software Part II: What Really is Technical Debt? What’s in a Metaphor? Code Analysis Time is Money Monetizing Technical Debt Typical Stakeholder Dialog Around Technical Debt Analysis of the Cassandra Code Project Dashboard Part III : Case Study – NotMyCompany, Inc. …
Software Engineering Radio, the world’s leading podcast on software development, published an episode on “10 Years of Agile Experience” yesterday. In this podcast Marcus Völter interviews me about introducing agile technology to different organizations, the experiences I made doing this job in the last 10 years, and stratgies I derive from this experience. The podcast was recorded in January at OOP 2008 in Munich.
This is the second post on the German book “Evolutionary Management” by Klaus-Stephan Otto and others. If you missed my first post on this, you may want to start there. Traditionally evolution is connected with fight and competition. Darwin phrased the mechanisms “Survival of the Fittest”, which is often interpreted as “Survival of the Strongest”. Otto and his colleagues point out that modern biologists have a slightly different view on this: It’s not the fittest who survive but the unfittest who die out. In other words you don’t have to be best, it is enough not to be the worst – an observation you can also make in today’s economy. In addition Otto points out, …
I recently ran into a book by a German psychologist and executive consultant on “Evolutionary Management” (If you speak German, you may be interested in the full reference below). Since this book is not published in English (yet?), I’d like to share some of their thoughts on this blog. “Evolutionary Management” sees itself as counter concept to a traditional command-control management and as a further development of Systems Thinking as it has been discussed by Peter Senge for general management and Jerry Weinberg in the context of IT. Evolutionary Management analyzes the mechanisms and solutions evolution uses in the nature and maps them to organisational problems. The results sound strikingly familiar to Agilists, although the book …
I don’t care if it works. It’s not our way. I don’t care if it’s expedient, effective or simpler. It’s not right. Those sound like counter-productive and potentially hostile kinds of comments. NOW, put them in a different context. CMMI. SAP. PMBOK. ITIL. These are the cookbooks of organizational success. By following the recipes, we can ensure great success. My two analogies come from my kitchen. I’m the chief cook in our house, and I love it. I was a short-order cook in high school and college, and found the experiences at a small-town restaurant to be enlightening. First, I “roast” my turkey with an inch+ of water in the bottom of the roaster. Talk …



Recent Comments