A report on why agile works for Australia’s most progressive organizations like ANZ, Bankwest, Commonwealth Bank, NAB, Suncorp, Allianz, SunSuper and many more and their journey to DevOps and continuous delivery.
Agile teams use retrospectives to reflect upon their way of working. Since it’s the team’s own responsibility to continuously improve themselves they have to decide upon the actions that they will do. What can managers do to support their teams when they are doing agile retrospectives?
When defining a business case for adopting agile, the question can arise how you can measure the business value that can be delivered using agile software development.
Following on from the "Individuals and Interactions" interview series Author Gill Broza launched a series titled "A Packing List for your Agile Journey" in which he will interview a variety of commentators, practitioners and authors on what it takes to make an agile transition sustainable in the long term.
Scrum of scrums can be used to scale the daily stand-up meeting when multiple teams are involved. Its purpose is to support agile teams in collaborating and coordinating their work with other teams. Several authors have shared views on scrum of scrums, with experiences of using them.
Agile retrospectives help teams to find and do actions to improve continuously. There are different ways to do follow up on the actions and to evaluate if actions are leading to better team performance and more value delivered to customers.
When adopting agile teams can use (external) coaches and mentors. But teams can also develop themselves by having team members mentoring and coaching each other. Team members can learn skills and abilities from other team members in multidisciplinary teams, enabling the team to grow as a whole and become self-organized.
InfoQ spoke to VersionOne CEO Robert Holler about the 8th State of Agile survey results which were recently released.
Adopting agile is an organization change which involves management. It is said that management buy-in is crucial for agile to succeed and that a lack of management support can be a barrier in agile transformations. There are different ways for management to support agile in enterprises.
The Manifesto for Agile Software Development values "working software over comprehensive documentation". This core value asks us to think about how much and which kinds of documents are needed and when they need to be written.
Several approaches exist to improve software development, among them are agile and lean. Managers have to decide which approaches to deploy in their organization. Approaches can also be combined depending on the problems that need to be solved. InfoQ interviewed Régis Medina about combining agile and lean, focusing on people and learning.
Agile coaches can coach in pairs instead of coaching individually. Each coach will focus on different aspects of coaching. As every coach has specific experience and skills they can complement each other. Two coaches can collaboratively help individuals or teams to learn and improve when adopting agile.
Regularly doing agile retrospectives helps teams to learn and improve themselves. You can make retrospectives more effective by adding purposes and by validating if your retrospective actions are leading to improvement with the usage of hypotheses.
Agile suggest that teams should fail-fast to enable quick learning from mistakes. Learning from failure is one approach, you can also learn early and fast from successes, by doing experimentation, or by using a plan for knowledge acquisition.
The experiences with more than two years of applying Kanban at SAP were presented by Alexander Gerber and Martin Engel at Lean Kanban Central Europe. Their case study showed how they supported the implementation of lean and agile processes. InfoQ interviewed them about how Kanban was introduced and received within SAP, the training approach and the experiences from teams with the Kanban practices