InfoQ Homepage Agile Content on InfoQ
-
Inclusion Has to Be Continuous
To create a truly diverse culture, we need to have inclusion throughout the whole lifecycle of an employee’s career journey. Leaders need to foster a psychologically safe inclusive environment to allow diversity and diversity of thought to exist. They need to grow people to move them out and continuously get new people in to shake things up, to maintain diversity and inclusion.
-
Reawakening Agile with OKRs?
Corporate agile often represents an improvement over what went before but falls short on delivering the high performance management wants and quality engineering environment developers dream of. The backlog becomes tyranny. Could OKRs - objectives and key results - reawaken the radical side of agile? Or do OKRs represent a return to command and control?
-
Using the Plan-Do-Check-Act Framework to Produce Performant and Highly Available Systems
The PDCA (plan-do-check-act) framework can be used to outline the performance, availability, and monitoring to enable teams to ensure performant and highly available applications. These include infrastructure design and setup, application architecture and design, coding, performance testing, and application monitoring.
-
Virtual Group Coaching: How to Improve Group Relationships in Remote Work Settings
Due to the pandemic, many software development teams will work remotely longer or permanently or work in blended venues such as some team members working in an office, some working from home, some working from other venues. Virtual coaching can help to improve group interaction or social dynamics in virtual settings where people work together remotely as a group or team.
-
Software Engineering at Google: Practices, Tools, Values, and Culture
The book Software Engineering at Google provides insights into the practices and tools used at Google to develop and maintain software with respect to time, scale, and the tradeoffs that all engineers make in development. It also explores the engineering values and the culture that’s based on them, emphasizing the main differences between programming and software engineering.
-
Inspect & Adapt – Digging into Our Foundations of Agility
Inspecting and adapting are fundamentals in agile practices. Yet, there are wide interpretations of how either is done well. It is a matter of our heart and soul – but the answer lies between our ears. In this article, we invite you to dip your toe into the deep waters of the internal inspect & adapt mechanisms. This article can be summarised in four words: Think. And think again.
-
Evolutionary Architecture from an Organizational Perspective
Creating an architecture that can evolve over time is not simply a technical challenge, and requires collaboration with non-technical people in an organization to ensure the software adapts as needed.
-
Agile Transformation: an Integral Approach
The book Agile Transformation - Using the Integral Agile Transformation Framework to Think and Lead Differently by Michael Spayd and Michele Madore provides an integral approach to agile transformations. The integral approach operates on all levels, from individuals to teams to the whole enterprise, helping us take multiple perspectives on situations and to think and act from multiple worldviews.
-
‘Debt’ as a Guide on the Agile Journey: Organizational Debt
In this article in a series on how ‘debt’ can be used to guide an agile journey, we will provide two examples of smells that are related to organizational debt, explain the symptoms, the impact on the business and in our organization, outline the experiments (countermeasures) that we have introduced in an effort to try to remove the smell, and provide some specific advice for you to be inspired.
-
Keeping Technology Change Human
When we are at the forefront of so much change, it's easy to forget that other people around us find change more challenging. This article is a reminder to look beyond the code and processes, to consider how tech team actions can affect our users in emotional ways. It seeks to establish a few ways of thinking to help bring others along with us when working through technology change.
-
The Game Master's Framework for Software Development
The Game Master Framework for Software (GeMs) combines role-playing concepts with software development, effectively creating a framework to deliver software in complex and chaotic environments. GeMs allows you to use your skills from playing Warhammer, WoW, Dungeons, or dragons, and C’thulu, to create software. GeMs combes gaming tactics with software creation.
-
Applying the “Whole Product Model” to the “Technology Adoption Life Cycle”
In order to develop products customer love, product managers need to truly understand how their “whole product” delivers value and when to address which customer segment. Two models that are very powerful when applied together, and that a product manager can use to develop extraordinary products, are The Whole Product Model and The Technology Adoption Life Cycle.