Early on in my EA career, I was very fortunate to become involved in a pioneering EA initiative at Westpac. My introduction to Westpac came when I helped its Group Data Resource Management team develop tool and repository support for its enterprise business model. During this engagement, I kept hearing people refer to an exciting but very hush-hush project that went under the code name “CS90.” I was intrigued and determined to find out more. That proved very difficult because the project was so leading-edge and innovative that all its documentation was marked at the highest level of secrecy. To make it even harder for competitors to find out what Westpac was doing, CS90 was divided Read more
Posts Tagged 'process'
By asking the CEOs of some of the most successful and influential companies in the world, such as GE and Google, a clear definition of innovation management emerges. The definition addresses the need to quickly and effectively implement organizational goals and objectives to remain competitive and the desire to strengthen advantages through the adoption of innovative ideas, products, processes, and business models. Enterprises facing increasing competition and the pressure of technological innovation are beginning to realize that to drive organic business growth and maintain a competitive advantage, they need to discover and implement innovation quickly and with great care to ensure maximum value. One-off innovations are moderately easy to take advantage of, but to create a pipeline of Read more
Every once in a while, you run into an individual or an organization with an acutely mechanistic view of software development processes. “Mechanistic,” in this context, means that processes are like machines: you wind them up and let them go. As long as they continue to operate, good things will result. This misconception echoes a similar view of political systems that is alternately harmless and dangerous. In “The Place Of The Independent In Politics,” James Russell Lowell warned that too many Americans had lapsed into a view of the Constitution that it was a “machine that would go if itself.” “I admire the splendid complacency of my countrymen,” Lowell said, “and find something exhilarating and Read more
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 Read more
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 Read more
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. Read more
Over the past few years I had the privilege of carrying out numerous technical debt engagements for Cutter. The typical makeup of these engagements is: A) align the various stakeholders through a one day workshop on technical debt; B) measure the technical debt; C) devise a plan to reduce it; and, D) work with the client to implement the debt reduction plan. The Cutter Consortium case study here describes how we simultaneously addressed the strategic, tactical and operational needs of one of our clients through such engagement. These days we are starting to break new grounds in technical debt research, analysis and field work by integrating technical debt techniques in the fabric of Cutter’s client companies. Read more