Bindings, Platforms, and Innovation
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
Tracking change and innovation in the enterprise software development community
Posted by Deborah Hartmann on Nov 27, 2007 12:01 PM
In this popular talk from Agile2007, The Role of Leadership in Software Development, Lean software thought leader Mary Poppendieck reviewed the last century's managment theories, including Taylor, Toyota and Deming, and went on to talk about "the matrix problem", alignment, waste cutting, planning, standards and other topics including the role of measurement: "cash flow thinking" over "balance sheet thinking".“Only after American carmakers had exhausted every other explanation for Toyota’s success – an undervalued yen, a docile workforce, Japanese culture, superior automation – were they finally able to admit that Toyota’s real advantage was its ability to harness the intellect of ‘ordinary’ employees.”Poppendieck, formerly a process control engineer, participated in the change from statistical process control to Lean-style manufacturing processes at 3M. Her experiences there of excellent teamwork, improved productivity and continual improvement spurred her on to develop a similar approach for software development, resulting in her first book with husband Tom, called Lean Software Development: An Agile Toolkit.
-- Gary Hamel, “Management Innovation,” Harvard Business Review, February 2006
There is something called standard work, but standards should be changed constantly. Instead, if you think of the standard as the best you can do, it’s all over. The standard work is only a baseline for doing further kaizen. It is kai-aku [change for the worse] if things get worse than now, and it is kaizen [change for the better] if things get better than now. Standards are set arbitrarily by humans, so how can they not change?The leader's job is to help people follow standards which they themselves made, and to guide them in continually improving their work, thereby evolving and updating their own standards.
When creating Standard Work, it will be difficult to establish a standard if you are trying to achieve ‘the best way.’ This is a big mistake. Document exactly what you are doing now. If you make it better than it is now, it is kaizen. If not, and you establish the best possible way, the motivation for kaizen will be gone.
Give-away eBook – Confessions of an IT Manager
Ebook: Scaling Agile with C/ALM
The Agile Business Analyst: Skills and Techniques needed for Agile
It's would be nice to have it as mp3 file
Hi Andrey, we plan to do this soon, look out for it in January.
That sounds great - i'm really looking forward to being able to download the content.
Unfortunately this has been pushed back, instead we're gonna fix our videos in general by migrating to a new platform that will solve our runtime problems people have complained about.
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.
This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.
This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.
This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.
After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.
IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.
Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.
4 comments
Watch Thread Reply