At the Lean Kanban France 2014 conference Bjarte Bogsnes gave a keynote presentation about beyond budgeting. In his presentation he talked about the problems with traditional management and how transparency and self regulating management comes to the rescue, and the principles and practices of beyond budgeting.
Metrics are engrained in kanban. They play a role in several kanban practices like visualizing and managing flow, and support the agenda’s for sustainability, service orientation and survivability. At the Lean Kanban Central Europe 2014 Conference Wolfgang Wiedenroth talked about the power of metrics. In his presentation he provided may examples of using metrics with kanban.
Blockades in work, like insufficient information, unclear requirements or having to wait for tools or systems to become available can have a systematic cause. It could be the case that similar problems that block the team keep happening until the underlying causes are addressed. You can use your blockades as treasures of improvement to sustainably improve the way work is done.
Martin Fowler, described Maturity Model as a tool that helps people assess the current effectiveness of a person or group and supports figuring out what capabilities they need to acquire next in order to improve their performance.
Teams can become so focused that they forget the world around them and risk losing contact with stakeholders. This makes it difficult for them to know what their customers need and how end users will use their products. At the ASAS2014 conference Daisy Rasing-de Joode will show how successful agile teams create synergy by being interdependent and highly collaborative with their environment.
Agile retrospectives are mostly done at the team level or at a project level. What if you need to conduct a retrospective with 50 teams or more? Luke Hohmann describes how a large scale agile transformation project did a huge retrospective to create insight on what was going well and what needed to be improved.
Continuous learning supports agile adoption in enterprises. A culture change can be needed to enable and support continuous learning. There are several things that managers and agile coaches can do to establish and nurture a continuous learning culture.
Developing and delivering products which customers don’t want and for which there is no market can be costly. Agile can help you to efficiently develop products, but you need to know what to build. How can you find out which products your customers need?
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.
Software delivery in a modern company requires autonomy to make releasing software easy. Niek Bartholomeus gave the presentation orchestration in meatspace at the DevOps Summit in Amsterdam where he discussed how can we change enterprises from orchestration to a more autonomous approach, in order to speed up the feedback cycle from idea to production.