Being one of the principles of the agile manifesto, sustainable pace is considered important by many to deploy agile. But achieving a sustainable pace can be difficult, and teams are often asked to improve their velocity. What did you do to adopt sustainable pace with your team? And how did you improve the speed in which your team delivers, and establish a new sustainable level?
Organization mostly do an agile transformation for a whole team, project, or organizational unit, given that agile is a team driven approach. But there are also professionals who start using agile practices individually, or who are working agile as a one person team. How can individuals adopt agile, and what kind of benefits can it give them?
Jonathan Kohl makes the argument for adapting processes in response to changes in the environment and technology ecosystem. He provides examples from the mobile device world and how a number of the "accepted" agile practices actually impede rather than enhance teams' ability to deliver value quickly.
The principle of “responding to change over following a plan”, is it a strength or a flexibility that can’t work in practice? For example, what about agile projects that had difficulties managing changes and customers who expect too much flexibility? Can agile not live up to its promises, or is it the way that teams and organizations have adopted agile that is causing the problems?
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.