InfoQ Homepage Agile Content on InfoQ
-
The Life and Times of TDD
Scott Ambler discusses a recent mini-survey designed to find out how TDD is being used in practice. He examines the state of practice and what techniques and tools are being used with TDD.
-
Stories of Collaboration in Remote Teams
Lisette Sutherland and Elinor Slomba are collecting and sharing stories from people whose business models depend upon getting remote teams right. These stories showing how remote teams collaborate, bridge distance, build trust and get things done together will be described in the upcoming book Collaboration Superpowers: The Remote Field Guide.
-
Nigel Dalton at Agile Australia on System Thinking, Social Experiments and 20 by 2020
At the recent Agile Australia InfoQ spoke to Nigel Dalton about social experiments in modern management, applying Lean, Agile and Systems Thinking to workplaces, disruptive innovation and his goal of "20 by 2020" - having 20% of organisations using agile management approaches by 2020.
-
Q&A with Barry Boehm and Richard Turner on The Incremental Commitment Spiral Model
The Incremental Commitment Spiral Model describes a process model generator. InfoQ interviewed the authors about the principles underlying the Incremental Commitment Spiral Model (ICSM), applying the ICSM, benefits that organization can get from it, and how organizations can use the ICSM to determine under what conditions to use software-intensive agile frameworks like Scrum, DSDM, SAFe, or DAD.
-
What Is Leading Self-Organising Teams All About?
What exactly do we have to do to capitalise on self-organisation? How can we best support our teams? What special kind of leadership is needed? The third article from a series on Leading Self-Organising Teams covers what it means to lead a self-organising team.
-
What UX is and isn't?
User Experience is part of a collaborative, self-contained and balanced team that has all the necessary roles to be wholly responsible for building the right thing, and building the thing right.User experience runs deep, is way more than the UI, and starts in the abstract with the strategy.
-
Renee Troughton on Agile Australia, Pragmatic Scaling and Non-violent Communication
At the recent Agile Australia conference InfoQ interviewed Renee Troughton about the theme of the conference, her experiences with large scale agile adoption and using non-violent communication in coaching.
-
Q&A with Sander Hoogendoorn on This is Agile
The book This is Agile: Beyond the basics. Beyond the Hype. Beyond Scrum by Sander Hoogendoorn covers situations that enterprises can encounter when adopting agile, and provides solutions on how to deal with them. It is a translation of the Dutch book Dit is Agile. InfoQ interviewed Sander about managing agile projects, balancing the work in iterations, and different kinds of agile approaches.
-
Collaborative Software Development Platforms for Crowdsourcing
In this IEEE article, authors provide an overview of current technologies for crowdsourcing in software development. They talk about the requirements, current practice and trends in collaborative platforms.
-
Project Inception - How to Use a Single Meeting to Achieve Alignment
Before you start a project, achieving team alignment is essential for efficacy and efficiency. High fidelity interactions with the whole team are far more effective for aligning a team than many emails, documents, and conference calls. This article describes how to do a single full-day inception meeting to get the extended team aligned.
-
Why Do We Need Self-Organising Teams?
Change is the only constant in our world and “business agility” is demanded. Our old maps for running organisations are no longer valid; we need new ones based on systemic thinking. This second article from a series on Leading Self-Organising Teams discusses why we need self-organising teams.
-
Leading a Culture of Effective Testing
We all want to have confidence in the software we create. We know that testing plays an important role. Assuming we've overcome the hurdle of learning the various ways to test, what's still missing that inhibits us from having confidence in what we do? How do we go about leading a culture of effective testing?