Tracking change and innovation in the enterprise software development community
JProbe Freeware,
an Eclipse plug-in,
diagnoses
memory issues
quickly & easily.
QCon San Francisco
Nov 19-21:
+ 80 sessions & tracks
Register now
and Save $400!
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
In team sport, as in software development, the team factor is crucial for success. In fact, team sport shows many inspiring parallels to software development. This article outlines 9 essential principles top-coach Marc Lammers discovered while building the world’s best field hockey team, and maps them to software development practices
Is the role of an agile manager only that of servant leader? Should they ever use traditional command and control tools? Should the agile manager ever wield authority and make demands of the team? Should they ever make changes in the membership?
Any change whether an Agile implementation or re-arranging the office furniture is going to encounter some resistance. The real question is how we react when that happens. Dave Nicolette and Lasse Koskela's workshop - was designed too help us understand where resistance comes from and how to handle it.
It's an old story. Techies cave in to the business guys because they don't know how to push back. The problem? Developers use numbers primarily for computation, but the business uses numbers to make decisions. In this story the "Spirit of Agile" encourages a developer to turn non-computational problems and issues into number language.
Agile approaches introduce a new leadership role, the "Agile Coach," which is not familiar from traditional methodologies. What's so important about this role? Is it just a new name for an old role? Why does Monster.com list 54 positions with this title? Patrick Kua of ThoughtWorks lists 26 useful answers to this question, in the form of an A-to-Z primer.
Joseph Pelrine was present when XP took its first steps, was Europe's first Certified Scrum Trainer, and today is still breaking new ground. In this 2007 InfoQ interview, Joseph talked about Network Analysis and how Social Complexity Science informs his work with teams; the usefulness of the Dilbert archetype; & a speed-dating technique to help teams get started (creating software, of course).
InfoQ presents a one hour video from the APLN Leadership Summit at Agile2006, where a panel of business leaders spoke about their experiences: Bud Phillips (Capital One Financial), Israel Ganot (BMC Software), Steven Ambrose (DTE Energy), Peter George (Cronos Inc.). Topics included top-down vs. bottom-up adoption, making the leap of faith to enterprise adoption and the value of the PMO.
Kenji Hiranabe talks about Toyota's development process of a new car. Kenji shares his experience meeting Nobuaki Katayama, former Chief Engineer at Toyota, and the lessons he learned from him.
In this presentation, recorded at QCon, Burton Group research director Anne Thomas Manes talks about how to make the business case for SOA. Her talk covers explaining SOA to non-technical business people, various approaches for selling SOA to management and gaining funding for SOA investments.
