InfoQ Homepage Agile Content on InfoQ
-
Beyond Requirements - Analysis with an Agile Mindset: Author Q&A
Kent McDonald has written Beyond Requirements: Analysis with an Agile Mindset. The book focuses on the analysis activities in an Information Technology product development project. It presents a set of principles which can be used to guide the analysis activities, some specific techniques with advice on when and how to use them and case study examples of how they have been applied on projects
-
Running Extended New Year’s Resolution Retrospectives with Focused Agile Coaching
This article explores how to do a New Year’s Resolution Retrospectives using a futurespective. It describes a team workshop where participants abstract themselves from the legacy of outstanding challenges and fly high dreaming the future, to see itself in a year from now and possibly derive some actions.
-
Edwin Dando on the Agile New Zealand Conference and Agile Beyond IT
Edwin Dando discusses the Transformation theme of the Agile New Zealand conference and how Agile ideas are taking hold outside of Information Technology
-
#noprojects - Outcomes: The Value of Change
In this third article in the #noprojects series Evan Leybourn explains the importance of focusing on outcomes rather than activities in order to maximize value for the organization. He looks at the context in which value is derived, provides an approach to define and measure outcomes and discusses the impact of constraints.
-
7 Habits of Successful Organizations - An Interview with Erwin van der Koogh
Erwin van der Koogh gave a talk at the Agile New Zealand conference in which he discussed the Seven Habits of Successful Organizations and how they enable business agility. Afterwards he spoke to InfoQ about the key themes from his talk.
-
Conversation Patterns for Software Professionals. Part 6
How to convince your client/supervisor/team to your ideas? – this is one of the most common questions that come up during my work with teams. This article presents some effective techniques that will help you propose solutions that you think are better than those suggested by your client. We will also decide if it is really about convincing.
-
Foundations of Self-Organization
The idea of self-organizing teams has been called the secret sauce of agile development. This article describes a model with three layers to systematically develop healthy self-organization. The layer called Foundations describes the required organizational infrastructure; The layer called People deals with teams and the individuals in the teams while the third layer is about the outcomes.
-
Q&A on Exploring the Practice of Antifragility
In the book exploring the practice of antifragility Si Alhir and Donald E. Gould collected experiences with and perspectives on applying antifragility. InfoQ interviewed them about their view on applying antifragility in software development, how antifragility can help organizations to become more flexible and able to deal with change, and the results gained from applying antifragility.
-
Continuously Improving Your Lean-Agile Coaching
This article describes the challenges faced in starting a group of internal lean-agile coaches and some outcomes such as self-assessment radars, mentoring sessions, and a few lessons. If you are considering a career as a lean-agile coach, you can use it to assess where you are and the next steps you can take. If you already are a lean-agile coach, you can use this to improve your coaching.
-
An Evaluation Guide to Application Lifecycle Management Software Solutions
Application Lifecycle Management tools provide many benefits, and are increasingly used by companies in all kinds of industry. However, identifying the one solution that best suits your requirements and internal processes is a difficult task. Kristof Horvath presents a guide to help you make an informed purchase decision by outlining a Request for Proposals that covers your ALM requirements.
-
Towards an Agile Software Architecture
Boyan Mihaylov covers his experience when working with both traditional waterfall software architectures and agile ones. He depicts the similarities and differences between these with a focus on three areas: the specifics of the software architect role, the timespan of the software architecture, and the output of the software architecture.
-
Connect Agile Teams to Organizational Hierarchy: A Sociocratic Solution
Many agile teams suffer from the mismatch of agile and organizational leadership with the latter being reflected by the organizational hierarchy. This article suggests using sociocracy as a solution that leaves the hierarchies in place yet still allows teams to act in an agile way.