InfoQ Homepage Adopting Agile Content on InfoQ
-
Going from Architect to Architecting: the Evolution of a Key Role
This article explores the cultural change of moving towards shared architecture, and the role that the architect has evolved into; from one with an air of authority and singular vision, to one in which system design issues are surfaced, which require team-wide input to resolve. Teams being coached and guided towards shared ownership might be struggling with the paradigm shift of ownership.
-
Individualized Testing Processes - One Size Does Not Fit All
Many organizations in the software industry have fallen into a state where they have set processes that are used across the organization and teams. Every team is not the same, so why are their processes all the same? In this article we’re going to explore what it can mean for teams to have individualized processes that are formed by the context of the work they are doing and of the team itself.
-
Accessing Agile Games as a Tool in Transformation and Change
This article puts the usage of Agile Games into a broader business context and introduces the steps needed to make any game a verifiable contribution to a given business objective. As “business” is a wide area of topics to be addressed, the article focuses on accessing Agile Games as a tool used within transformation and change. It provides an example that was taken from this area.
-
DevOps at Schneider: a Meaningful Journey of Engaging People into Change
Adopting DevOps at Schneider started with building a case for change. Tech people were engaged into change by organizing learning and collaboration sessions and getting feedback from the front lines. Change is hard and without leadership support, dedicated time for developers to really digest it and continual reinforcement and conversation, it will be challenging to be successful.
-
What Kind of Coach Does Your Team Need?
Coaching is primarily client-driven; the client chooses the right coach for a particular need at a particular time. However, the team may first need to understand what coaching is before deciding what kind of coach they need, and why they need it. This article examines the role that a coach can play in establishing, maintaining and nurturing a safe space for teams to grow and achieve their goals.
-
How to Optimize for Fast Flow Using Alignment and Autonomy: the Journey of a Large Bureaucracy
This article describes how NAV (Norwegian Labor and Welfare Administration), Norway's largest bureaucracy, has achieved alignment in over 100 autonomous teams. It shows the techniques it uses to align teams with respect to technology: two descriptive techniques - the technology radar and the weekly deep dive, and two normative techniques - the technical direction and internal platforms.
-
Why You Might Need an Island of Agility
Organizational change doesn’t happen overnight, but that doesn’t mean improving agility is impossible. Regardless of the agile approach, by creating an island of agility, we can set a course to agility while the rest of the organization catches up. The key to success is avoiding an island too small to have an impact, having a plan to grow the island, and adding islands to keep momentum.
-
Pipedrive Agile Framework: How a Unicorn Company Customized Agile Processes to Scale
Pipedrive would not have become a unicorn company by using a standard off-the-shelf agile framework. Instead, the company created its own framework. It makes a distinction between Mission Teams versus Launchpads and relies heavily on dynamic reteaming. In Pipedrive's Agile Framework, the product managers pitch new ideas and software engineers volunteer to lead their Mission Teams.
-
Why the Dual Operating Model Impedes Enterprise Agility
Most organizations adopt a dual approach to agility, with some parts of the organization working in an agile way that delivers value in increments, measures the response and adapts accordingly, while the “traditional” organization continues to work as it always has in a relatively top-down way. In this article, This approach must eventually be left behind after an Agile transition.
-
Reducing Cognitive Load in Agile DevOps Teams Using Team Topologies
In this article we will be sharing our experience from 12 months of adopting certain management and organisational insights from the book Team Topologies. It explores how we identified areas of responsibility and assigned those into mostly customer-facing domains which could be given to our teams. It shows how an inverse Conway manoeuvre can be used to improve the architecture.
-
Making Agile Work in Asynchronous and Hybrid Environments
Making Agile work in the age of hybrid and remote teams requires extra effort to stay aligned and collaborative. This article explores how development teams can stay agile, even when face-to-face collaboration isn’t an option, by using visual collaboration to build context and alignment, and adopting new practices for engaging meetings.
-
Using Patterns to Drive a Transformation towards Agility - Practical Insights from Large Companies
In the DACH region, a community of transformation leaders from about 30 companies started “DACH30” sessions where they share experiences and insights from their efforts to help their companies become more agile. This article highlights successful patterns to foster change, how to apply flow-oriented design to optimise your delivery capabilities, and the danger of the illusion of control.