Stories about the Transformation toward Agile
Many teams, projects and organizations have meanwhile started the transformation toward an agile approach. Yet even more plan to do so. A lot of companies want to become agile because they regard agility as a promising development approach: Some because the Standish Group is recommending agile processes for avoiding project failures but even more so because an agile approach seems to be a better fit to the increasing market demands of today.
Yet, transitioning to agile often has an impact in many dimensions that are difficult to foresee. Moreover, many teams and organizations are uncertain about how and where to start, what pitfalls to avoid and what kind of opportunities to look out for in order to become agile. In this talk, Jutta shares “war stories”, including successes and failures about the transformation toward and integration of agile.
Typical Pitfalls in Agile Software Development
Many teams, projects and even organizations are following meanwhile an agile process. However, not always successful. If you're looking behind the scenery, you will find out that although the agile practices like pair programming or test-driven development are used properly, the agile value system is not implemented. This is due to the fact that the practices can support agility but they can not establish agility. This leads to an expectation mismatch regarding acceptance and success of agile development.
With her experience in helping projects all over Europe to establish the agile value system, Jutta will point out what to look out for when applying agility.
Increasing Productivity by Uncovering Costs of Delay
Fred Brooks once stated so wisely "How does a project get to be a year late? … One day at a time." Lean Development and queuing theories offer help so that this won't happen. The suggested remedy is to implement a steady flow in order to achieve maximum productivity. However, most teams and organizations are far from reaching that goal and moreover it is often unclear which approach leads to what kind of delay. In-depth examination shows how generally accepted concepts such as Definition of Ready, Clean Code, or experts in a team can lead to costs of delay. In this session Jutta presents simple tools and methods for uncovering hidden costs of delay. These tools and methods can be applied in various contexts: In small and large teams as well as in co-located and distributed teams. Using an agile approach will help to make these cost visible.
Agile Teams: Self-Organizing, Collocated, and Distributed
Agile development requires teams to self-organize. However, this doesn't happen by chance. Teams have to be set up in a way that allows them to self-organize. And moreover, if you work on a large project with more than one team the team structure should still enable self-organization. The same is true for global development. In this session we will cover the essentials for building productive self-organizing teams for small and collocated and as well for large and distributed settings.
- Understand what characterizes self-organization and the evolution of an agile team
- Understand what kind of communication and collaboration ensure a team's agility
- Learn how teams can be agile in large and distributed environments
- Understand how both - developing business functionality and ensuring conceptual integrity of the architecture can be supported
Introducing Agility into an Organization or: How to become Agile
According to Forrester Research 14% of the enterprises both in the USA and in Europe apply an agile approach and another 19% consider to get started with agile. A lot of companies want to become agile because they regard agility as a promising development approach, not only because the Standish Group is recommending agile development processes for avoiding project failures. Yet, many teams are uncertain about how and where to start in order to become agile. Moreover, transitioning to agile often has an impact in many dimensions that are difficult to foresee. In this talk, Jutta provides insights in how to get started with agile, what pitfalls to watch out for in the transition phase and as well how to ensure that the agile mindset will be preserved.