Tapestry for Nonbelievers
A new article by I. Drobiazko and R. Zubairov introduces v. 5 of the Apache Tapestry component-oriented web framework. The tutorial shows how to create a component and covers IoC in Tapestry and Ajax.
Tracking change and innovation in the enterprise software development community
Posted by Deborah Hartmann on Dec 26, 2006 01:07 PM
The "Toyota Production System", an icon of process effectiveness, has provided the model for numerous process improvement initiatives. Since Toyota's industry-leading approach to auto production became widely known in the late 80's, GM, Ford and Chrysler have applied ideas drawn from TPS, yet at this point they still trail Toyota, which continues to grow steadily. In his recent FastCompany article, "No Satisfaction at Toyota," Charles Fishman suggests that the difference is in the underlying understanding of the work: "Toyota's competitiveness is... rooted in an institutional obsession with improvement that Toyota manages to instill in each one of its workers, a pervasive lack of complacency with whatever was accomplished yesterday." The article, with its interviews and stories, provides an interesting study for those interested in reducing waste in the software development industry.The work is really threefold: making cars, making cars better, and teaching everyone how to make cars better. At its Olympian best, Toyota adds one more level: It is always looking to improve the process by which it improves all the other processes.Every members of a Toyota production team is both an expert in car manufacture and an expert in process improvement. With every employee trained in, and responsible for, hunting out waste the enterprise gains a powerful grassroots tool for improvement. Kosaku Yamada, chief engineer of the Lexus ES 300 has summed it up: "The real differential between Toyota and other vehicle manufacturers is not the Toyota Production System, but the Toyota Product Development System".
Lean Software Development Principles
Eliminate waste
does not mean throw away all documentation.
Amplify learning
does not mean keep on changing your mind.
Decide as late as possible
does not mean procrastinate.
Deliver as fast as possible
does not mean rush and do sloppy work.
Empower the team
does not mean abandon leadership.
Build integrity in
does not mean big, upfront design.
See the whole
does not mean ignore the details.
--Mary Poppendieck and Tom Poppendieck
Lean Software Development, An Agile Toolkit, p179
IBM Agile Development eKit: Free Articles, Expert Q&A, Educational Resources
Fighter Jets and Agile Development at Lockheed Martin (Case study)
I like the idea of having everyone in the team an expert not only in what they do, but also in process improvement. I'm just through explaining to a team that the problem with their process improvement groups is that none of them have any experts in process improvement. Now, if everybody were an expert in process improvement, we would have some confidence that any changes would be changes for the better.
Having an external process improvement group goes against the lean process. Lean software development gives you a number of principles and tools; these all make the team who is building the product the responsibility (and principles and tools how-to) for constant process/quality improvement. Only "the people on the floor" now best how to improve their work, make them responsible and give them empowerment. That's the lean way. Having external process groups sounds very CMMI-like and like I said very Lean-unlike.
A new article by I. Drobiazko and R. Zubairov introduces v. 5 of the Apache Tapestry component-oriented web framework. The tutorial shows how to create a component and covers IoC in Tapestry and Ajax.
In this interview, Burton Group consultant Pete Lacey talks to Stefan Tilkov about his disillusionment with SOAP, his opinion on REST, and addresses some of the perceived shortcomings REST vs. WS-*.
Jay Fields presents his concept of Business Natural Languages - a type of Domain Specific Languages geared towards being readable by domain experts.
Adoption and interest for Distributed Version Control Systems is constantly rising. We will introduce the concept of DVCS and have a look at 3 actors in the area: git, Mercurial and Bazaar.
Deborah Hartmann interviewed Segundo Velasquez about his experience as customer with an Agile team during the initial phase of software design of a product.
David Cooksey shows how to fine grained versioning to a ClickOnce deployment using an HttpHandler written with ASP.NET, making partial rollouts to a test audience much easier.
Windows workflow (WF) is an excellent framework for implementing business processes, but lacks support for human activities. This article describes a completely generic approach for changing this.
In this interview taken during OOPSLA 2007, Markus Voelter talks about the importance of documenting the software architecture, and gives some good and also bad examples on how it could be done.
2 comments
Reply