InfoQ Homepage Agile Content on InfoQ
-
How Defining Agile Results and Behaviors Can Enable Behavioral Change
Specifying and measuring behavior within a certain organisational context can enable and drive behavioral change. To increase the success of an agile transformation, it helps if you link the desired behaviors to the expected results. This way you set yourself up to be able to reinforce the behavior you want to see more of in order to reach your results.
-
Effective Retrospectives Require Skilled Facilitators
Retrospective facilitators can develop their facilitation skills by self-study and training, and by doing retrospectives. Better retrospective facilitation can lead to higher effectiveness of change and impact the progress of an organization.
-
The Myth of Product Mindset: It's What You Do, Not How You Think
Companies nowadays are looking for ways to cultivate a product mindset. While the idea of cultivating a “product mindset” allows us to focus primarily on ourselves, actually transforming our organizations often means changing our behavior to focus on our customers and how we work together to serve them.
-
State of Value Stream Management Report Shows Platform Adoption Increased 4X in a Year
The Value Stream Management Consortium has produced their 2022 report, which most notably shows a 4x increase in the number of respondents implementing a Value Stream Management platform. Organisations implementing VSM are using value streams to break down silos, and rather than setting a vision and goals up-front, many are just starting with a VSM mapping exercise treated as an experiment.
-
Using Data to Predict Future Usage and Increase User Insights
By identifying usage trends, you can proactively adjust load, scaling, and routing to better handle the load on particular parts of the globe when you know it will peak there. Data about how users interact with your application can be used to design future features that better mimic these patterns and ensure that new features have a better chance of solving real user problems and getting adopted.
-
Establishing Autonomy and Responsibility with Networks of Teams
Working in outdated ways causes people to quit their work. Pim de Morree suggests structuring organizations into networks of autonomous teams and creating meaningful work through a clear purpose and direction. According to him, we can work better, be more successful, and have more fun at the same time.
-
Trust-Driven Development: Accelerate Delivery and Increase Creativity
By building trust you can break silos, foster collaboration, increase focus, and enable people to come up with creative solutions for products and for improving their processes. The DevOps movement was created to break the silos in the organisations; trust can be built by organising pair programming across various functions and various teams.
-
How Norway's Largest Bureaucracy Optimises for Fast Flow
To optimise for fast flow, the Norwegian Labour and Welfare Administration has adopted a teams-first approach. High-performing teams need autonomy, and they also require direction and alignment. Solutions should be adopted by the teams within their context, abilities, and cognitive capacity.
-
How to Prepare an Agile Business Game
To make playing games "interesting" from the business owner's perspective, we need to ensure that they are aligned with the business needs. There are four steps in preparing a game: exploring the context, knowing your target group, defining the focus, and deciding how to facilitate it.
-
Fair Individual Compensation for Agile Teams with Team-Set Salaries
Team-set salaries can be used to set fair compensation for individuals in multiskilled, collaborative, autonomous teams. People don’t appraise themselves, only their colleagues. It gives everyone a direct say in salary settings.
-
GitHub Codespaces Can Now Be Templated to Improve Performance
GitHub has introduced prebuilt Codespaces to reduce the time it takes to spin up a full development environment for large, complex projects.
-
Increasing Collaboration at Ericsson: Hardware and Software Developers Learn Each Other's Language
You can integrate hardware and software development with a cross-border team setup, where it’s important that hardware and software developers speak each other’s languages. The suggestion is to focus on “us” instead of “we” and “them”, and on the technical competence that connects developers over agile or lean terminology.
-
Leading a DevOps Transformation - a Collaborative Engineering Approach
When leading a DevOps transformation, transparency and visibility can help to get teams engaged in chance. Once involved, developers can act as knowledge multipliers and contribute to change initiatives. A mixture of solving frequently-occurring problems, addressing complex problems, and showing progress of the transformation can help to keep stakeholders involved.
-
How to Work Asynchronously as a Remote-First SRE
The core practices for remote work at Netlify are prioritising asynchronous communication, being intentional about our remote community building, and encouraging colleagues to protect their work-life balance. Sustainable remote work starts with sustainable working hours, which includes making yourself “almost” unreachable with clear boundaries and protocols for out of hours contact.
-
Will the Hybrid Work’s Great Paradox Be the Decade’s Challenge?
The pandemic moved the office home, and while the medical system is trying to eradicate it allowing us to resume our lives as we know them, we also need to understand what the new normal will be. While some leaders will return to the office as soon as it is allowed, others adopt a fully remote approach as the main-approach. Probably a hybrid approach would be the new normal for most of us.