Tracking change and innovation in the enterprise software development community
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
Introducing the
SpringSource
Application Platform:
Next-gen Java
AppServer
Rule your SOA
with CentraSite
standards-based
registry/repository
Create REST
-enabled Web Apps
with Project Zero
from IBM.
Plan-driven dev
Environments and
Agile tutorials at the
Better Software
Conference & Expo!
In this InfoQ article Kenji Hiranabe applies lessons learned while working with Japanese manufacturers. While many Agile teams are optimizing only a portion of the value stream, Hiranabe proposes a simple way to adapt lessons from Lean Manufacturing's "Kanban" visual tracking system to make process visible to more of the organization, for better communication and process improvement.
In this 90-minute talk from the Agile2007 conference, Lean software thought leader Mary Poppendieck reviewed 20th century management theories, including Toyota and Deming, and went on to talk about "the matrix problem", alignment, waste cutting, planning and standards. She closed by addressing the role of measurement: "cash flow thinking" over "balance sheet thinking".
In a 60-minute JAOO 2005 talk, Scrum creator Dr. Jeff Sutherland covers the history of Scrum from its inception thru his participation with Ken Schwaber in rolling out Scrum to industry, to its impact at Easel, Fuji-Xerox, Honda, WildCard, Lexus, Google. He looks at Scrum types A, B and "all at once" type C, and confirms the humorous rumour that Kent Beck "stole" Scrum practices when creating XP.
"A fundamental premise of the 'train-wreck' approach to management is that the primary cause of problems is 'dereliction of duty'" said Peter Scholtes in his 2003 book on leadership. Mary Poppendieck's recent article on process, people and systems asked: "Which is more important - process or people?" and showed how Lean is an alternative to certified process improvement programs like ISO 9000.
David Anderson described how his team is using a kanban system for their sustaining engineering (maintenance and bug fixing) activities. Iterations have been dropped although software is still released every two weeks. Work is scheduled, monitored, and run via a "kanban board" and daily stand-up meetings.
Since the "Toyota Production System" emerged in the late 80's, GM, Ford and Chrysler have applied TPS ideas, but they still trail Toyota. In his article, "No Satisfaction at Toyota," Charles Fishman suggested that the key is in teaching new ideas about what success looks like. It's an interesting read for those thinking about waste reduction in software development.
Jeff Sutherland, an Agile Manifesto signatory, ran the first Scrum at Easel Corp. in 1993. At JAOO 2005 he covered the history of Scrum from its inception to its impact at Easel, Fuji-Xerox, Honda, WildCard, Lexus, Google. Along the way Sutherland shared interesting stories & looked at Scrum types A, B, and "all at once" type C, reminding listeners that cultural change is the hard part of Scrum.
