InfoQ Homepage Agile Content on InfoQ
-
Bas Vodde on Large Scale Scrum
Bas Vodde describes strategies for large teams with legacy software to adopt Scrum successfully. Bas discusses communication problems found in most component teams and why and how teams - especially large ones - should make the change to feature teams and how that change affects organizational structure.
-
Jeff Patton on Embracing Uncertainty
In this interview with Jeff Patton at Agile 2008, he talks about three strategies that can help product owners do their job more effectively by embracing the inherent uncertainty in all software development. Namely they are understanding the ultimate goals of the project, delaying decisions until the last responsible moment, and scaling up by building quality.
-
Lean Organizations to Support Agile Teams
Robin Dymond gives an overview of Lean, how it can help take Agile to the 'next level' and why organizations that fail to change will not have successful Agile teams. Robin describes an organizational mismatch between traditional hierarchies and team structures. He believes that organizations will need to reorganize around teams to get the most out of Agile.
-
Pollyanna Pixton on Agile Leadership
Pollyanna Pixton tells us that within a culture of trust leaders must stand back and if they don't then they are hampering and restricting the productivity and the creativity and the innovation of teams. She discusses how leaders can foster a culture of trust and what they must do to get the most out of Agile teams.
-
Brian Marick and Micro-Scale Retro-Futurist Anarcho-Syndicalism
Brian Marick discusses what he means by micro-scale-retro-futurist-anachro-syndicalism and why we should go back to the roots of Agile. He talks about what he thinks were the mistakes in the Agile Manifesto, how it has lead to the state of the Agile community today, and how we can build better systems by making them so that they are much more easily tested.
-
Luke Francl Explains Why Testing Is Overrated
In this interview filmed during RubyFringe 2008, Luke Francl explains his position towards testing. While supporting unit testing, he thinks testing is not going to reveal all application defects. Development teams should also practice code reviews and usability tests which are likely to discover bugs not visible though other methods.
-
Software Design Helps Being Agile
In this interview made by InfoQ’s Deborah Hartmann during Agile 2008, Rebecca Wirfs-Brock talks about software design, the need for good design and the technical debt that might accumulate slowing down the development process. The conclusion is that agile developers should not disregard design.
-
Dan Grigsby Shares Secrets of Successful Entrepreneurship
In this interview made by InfoQ’s Rob Bazinet during RubyFringe 2008, Dan Grigsby talks about programming and entrepreneurship, how a programmer can take his idea and transform it into a successful product.
-
Similarities Between Interaction Designers and Agile Programmers
In this interview made during Agile 2008, Alan Cooper, the father of Visual Basic and supporter of interaction design, talks about his contact with the Agile movement and the similarities discovered between Agile programmers and interaction designers.
-
Ian Robinson discusses REST, WS-* and Implementing an SOA
In this interview from QCon San Francisco 2008, Ian Robinson discusses REST vs. WS-*, REST contracts, WADL, how to approach company-wide SOA initiatives, how an SOA changes a company, SOA and Agile, tool support for REST, reuse and foreseeing client needs, versioning and the future of REST-based services in enterprise SOA development.
-
Jay Phillips on Adhearsion and VoIP
In this interview recorded at RubyFringe, Jay Phillips talks about VoIP, Asterisk and how his framework Adhearsion makes it easy to write voice applications.
-
Keith Braithwaite, an Agile Skeptic
In this interview made by InfoQ’s Amr Elssamadisy during Agile 2008, Keith Braithwaite, an Agile developer, consultant and trainer, says that we should show a good deal of skepticism towards today’s Agile practice.
