Tracking change and innovation in the enterprise software development community
Create REST
-enabled Web Apps
with Project Zero
from IBM.
Introducing the
SpringSource
Application Platform:
Next-gen Java
AppServer
Plan-driven dev
Environments and
Agile tutorials at the
Better Software
Conference & Expo!
Rule your SOA
with CentraSite
standards-based
registry/repository
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
At NFJS Venkat Subramaniam, author with Andy Hunt of "Practices of an Agile Developer," shared his pragmatic approach to some of the important technical and non-technical factors contributing to project success, including: coding, developer attitude, debugging, mentoring and feedback.
Joseph Pelrine has come full circle: from university studies in Psychology, journeying through SmallTalk, XP and Scrum, and now back to broader questions: Why and how does Agile work? In this interview, Joseph talked about Complexity Science, and how story-telling, "sense-making," network analysis and speed-dating's gut-feel approach may prove more useful than our old toolkits for managing teams.
What does it take to create a high-performing team? According to Doug Shimp and Samall Hazziez, a "Well Formed Team" exhibits the following characteristics: follow Agile and Lean principles, use an adaptive system with a feedback loop, are focused on the business vision, are passionate and hyper-productive.
Kirk Knoernschild shares his thoughts about Design and Code reviews. He mentions that such reviews promise to improve software quality, ensure compliance with standards, and serve as a valuable teaching tool for developers. However, the way they are performed affects their value. In some organizations they might really add whereas in others a review might just be a part of the bureaucracy.
The discussion of applying lean principles to software development has largely focused on identifying and eliminating waste (in Japanese: muda). Lean Thinking equally aims to remove overburden (muri) and unnecessary variation (mura). Roman Pichler discusses the relationship of the "three M's" and proposes to eliminate overburden as the first step toward a leaner process.
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.
At QconLondon 2007 Jim Coplien spoke with "Pragmatic" Dave Thomas for InfoQ. This energetic 30-minute interview runs the gamut of Dave's wide-ranging interests: 'agile' publishing; how to turn what you love doing into a book; programming (and methodology) monocultures; staying limber with code "katas"; and advice for academics: help your students live with the passion of a 5-year old!
Agile, once the territory of "early adopters" is coming into the mainstream and meeting resistance. Does this mean Agile can't work in more traditional teams and organizations? Not necessarily, say coaches Michael Spayd and Joe Little, in this InfoQ interview taped at Agile2006. What's needed is an awareness of the need to facilitate organizational change.
Of course, "anything more than 'barely sufficient' process is waste," but what does that mean for your team, or my next project? In this 60 minute presentation from the APLN Leadership Summit at Agile2006, Todd Little shared a model to help choose the right "flavour" of Agile for different kinds of projects, and discussed the importance of 'steering' throughout the project's duration.
