Failing fast and often is one of the encouraged practices for agile teams. Sander Hoogendoorn, author of the This is Agile book discusses on his blog the importance of having a strategy that helps you on the decision of aborting a project by assuming its failure on an early stage.
Top-down implementation of agile is a commonly use approach for agile adoption in organizations. Alternative approaches exist, like implementing agile by stealth, using continuous improvement teams, starting with a quiet phase or taking baby steps by implementing a limited set of agile practices.
Roman Pichler shared his views on product owner’s participation in sprint retrospective to increase collaboration with development team.
Hiren Doshi recently published a post on his blog about Anonymous Retrospectives, a technique suggested for agile teams to maximize the feedback gathered during retrospective meetings.
How can we manage and govern multiple agile teams? At the Agile Governance conference in Amsterdam Christoph Johann Stettina presented about agile governance and the role of management. He studied 14 large European organizations on how they apply agile project management methods in IT project portfolios.
How can you make a company grow without sacrificing it’s culture? InfoQ talked with Fridtjof Detzner, co-founder of DIY website creator Jimdo, about how Jimdo started and scaled up using agile and why Jimdo uses kaizen and retrospectives to improve continuously.
Agile software development or Scrum is not enough to make your enterprise truly deliver on the Agile promises, says Dave van Herpen. He suggests that IT service management should apply agile and lean practices combined with DevOps to improve collaboration throughout the entire enterprise.
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?
Random retrospective activity generator "Retr-O-Mat" now available as printed edition, contains 50 activities from various sources.
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.
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.
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.
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
The build-measure-learn feedback loop in lean startup aims to help entrepreneurs to learn about the needs of their customers. Agile retrospectives are a way to reflect and learn and to agree on changes that are needed. Some examples describing how lean startup can be supported with agile retrospectives to learn and take actions.
Working in an agile team can sometimes be stressful, when the needs of the customers are unclear, if there is a lot of work to be done, or when team members are having difficulties doing their work. You might ask the question if having fun could reduce the feelings of stress, increase motivation, or increase productivity? And if that is true, then what can you do to have more fun in agile teams?