Agile methods have the potential of creating great results. But those great results are not a guarantee; in fact anecdotal evidence suggests that those great results are only achieved by a small percentage of those teams and organizations adopting and adapting agile methods. There are invisible requirements for this success. One of these requirements seems to be safety.
Retrospectives are often considered to be a valuable agile technique, but sometimes teams have difficulties doing them: insufficient control of things, thinking that they can’t improve, difficulties defining good actions, or much complaining. Teams may find retrospectives boring, and a waste of their time. How to deal with this, and help teams to discover better ways to do retrospectives?
Martin Fowler talked about software development in the 21st century, discussing agile essence and how teams adopt agile. He presented at the GOTO Amsterdam 2013 conference how teams can increase their agile fluency, from a first star level up to four stars.
The third annual GOTO Amsterdam conference covers Java, Mobile, Cloud, OpenSource, Lean/Agile, Architecture, New Languages & Process communities. The first day started with a keynote by Linda Rising, exploring research on incentives starting from the industrial age, and looked at how it is being doing in practice by managers with development teams. InfoQ interviewed Linda about her experiences.
Collaboration between business and IT can be a problem in enterprises. People are finding ways to better support the business needs and increase the business value of IT, using business IT fusion, DevOps or sociocracy.
Collaboration between agile team members, like developers and testers, helps to make teams successful. What can scrum masters do to help testers and developers to work together in agile teams, and improve collaboration?
Impediments are used to discuss issues take actions when a team becomes blocked. Impediments are handled in different ways, a look at how some scrum masters do it.
VersionOne recently released the results of their State of Agile Development Survey for 2012, and once again it proved to be an interesting indicator of Agile adoption and trends.
Retrospectives help teams to learn and improve their way of working. Several agile coaches have scaled retrospectives to cover larger projects or programs with multiple teams. Let’s explore how they did it.
Gil Broza, author of “The Human Side of Agile” has announced a series of audio interviews with a variety of authors and commentators on the topic of “Individuals and Interactions” in May. The theme of the series is "Apply proven strategies, approaches, and actions to make the Agile promise happen".
Organizations that implement self-organized agile teams need managers who empowerer the teams by using servant leadership, and who coach and mentor them to learn and continuously improve themselves.
Two video lessons covering agile coaching and organizational change were released by Pearson/Addison-Wesley in the last quarter of 2012. They provide a different way to increase knowledge on agile adoption for visual and audible learners.
Organizations want to improve their business processes, and today they need to do it faster. Is it possible to use agile methods and techniques for business process improvement?
Ryan Cromwell has released the Release Cadence Report Survey. Based on the premise that the rate at which software is released is one of the most important metrics teams should be monitoring and reporting on he has launched a survey which examines five areas of team activities. The survey will remain open until 24 May 2013, following which the results will be made available to the community.
After software development agile practices are now also being used in other aspects of business, according to Gartner. Insights in using agile in the whole enterprise, with examples from marketing, sales and services.