Management can get the feeling of losing control when their enterprise adopts agile and starts deploying self-organizing teams. Procedures, review boards and consultation bodies can become superfluous when switching to an agile approach, but they may not realize that, says Marcel Heijmans. Trying to regain control with additional planning can make things worse, causing "death by planning".
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.
As the need for software products and services increases organizations look for ways to increase their capacity. Often organizations decide to scale up by adding more people. Some question this approach and suggest alternative ways to be able to deliver more software without adding people.
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.
Tasktop released a new tool called taktop sync 3.5 for agile at scale. InfoQ spoke to Mik Kersten, CEO of Tasktop Technologies about the product release.
Larger organization often have the desire to use Scrum beyond the team level. This news explores some examples of what organizations do to adopt an agile way of working across the enterprise by scaling Scrum.
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.
Enterprise Scrum Definition Release 1.01 released by Mike Beedle as business-oriented, scalable, general empirical management and execution framework.
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.
To incrementally develop and deliver products using agile software development, requirements are gathered and organized into a product backlog. A requirement technique that is used in agile software development is use cases. Some techniques to apply use cases for managing product requirements in agile are use case 2.0, slicing and laminating.
The product owner role from Scrum is used to interface between the business and development. In larger organization with complex products and many decisions that need to be made, having this role filled in by one person is often not feasible. InfoQ did an interview with Timo Punkka about the role of the product owner, lean portfolio management, and customer collaboration.
Enterprises that are adopting agile organizational-wide will at some time have to scale their agile practices. In a session at the Agile Methods in the Finance Sector and Complex Environment conference, attendees shared their experiences with scaling agile in enterprises.
The way that agile teams and organizations take decisions impacts the value that they can get from agile ways of working. To become agile, it can help to learn different decision making techniques, and pick the one which is most suitable for a situation.
The Scaled Agile Framework (SAFe), created by Dean Leffingwell, seems to be gaining momentum in our community and is touted as the equivalent of Scrum at an organizational level. It is currently supported by several vendors including Rally, Net Objectives, Valtech, and Ivar Jacobson International. However, not all in the community think SAFe is a good idea.
Back in November, Spotify released a paper titled "Scaling Agile @ Spotify with Tribes, Squads, Chapters & Guilds". I recently had a chance to chat with Henrik Kniberg, one of the coaches on site there, to ask him some questions about the paper and to get an update on where they are today.