InfoQ Homepage Agile Techniques Content on InfoQ
-
Dialogue Sheets: A new tool for retrospectives
Dialogue sheets allow teams to hold facilitator-less retrospectives. They promote self-organization and encourage everyone to speak in the exercise. This results in great levels of participation in and higher energy levels in teams. The sheet itself is A1 in size, 8 times larger than a regular sheet, pre printed with instructions and questions to motivation discussion.
-
Feature Injection: three steps to success
Often Customers provide half baked solutions with no linkage to value. An Agile team needs examples linked to the Business Value they provide. Feature Injection is a process that takes a half baked solution identifies the Business Value it provides and then produces a set of examples driven from that value.
-
Is Agile Sub-Optimal?
Lean has the concept of a Sub-Optimal process. A Sub-Optimal process is where a part of the process is optimized to the detriment of the entire process’s efficiency. Are Agile practices creating projects that are in danger of being or becoming Sub-Optimal? What Agile practices are contributing to projects becoming Sub-Optimal? What can we do ensure our projects do not become Sub-optimal?
-
Interview and Book Review: Specification by Example
Gojko Adzic has written the book Specification by Example, explaining the set of techniques for describing the functional and behavioural aspects of a computer system in a way that they are useful to the development team (expressed ideally as executable tests), understandable by non-technical stakeholders and maintainable to remain relevant despite changing customer demands.
-
Test automation and Continuous Delivery
This article shows how automating certain programmable aspects of a test suite can help software delivery. Covered are automated testing, costs per deployment, tests as documentation & manual testing.
-
Organizational Culture and Agile: Does it fit?
Recently, Agile Coach Michael Sahota has been exploring the impacts of organizational culture on Agile transformations. We caught up with Michael and asked him to answer a few questions for our readers.
-
Active Architecture for Agile Projects
Active Architecture is a type of documentation that helps to bridge the gap between User Stories in Agile Projects and large design deliverables on Traditional projects. It leverages the power and simplicity of User Stories. Unlike traditional design documentation that defines the structure or passive state of the design, Active Architecture defines the actions or active state of the design.
-
Patterns for Continuous Delivery
There is no one-size-fits-all solution to implementing Continuous Delivery. The number and composition of the teams will greatly affect what options are available and what trade-offs need to be made. Staff editor Jonathan Allen reflects on some of the patterns he has observed over the last 15 years.
-
Interview and Book Review: Continuous Delivery
Continuous delivery means that a software product is production-ready from day one of the project, even if all features not implemented, and the product can be released to users on demand. InfoQ spoke with Jez Humble and David Farley, authors of "Continuous Delivery" book on the continuous delivery concept and how it can be used to deliver the software product more efficiently.
-
Limiting Work in Progress and Scrum
Sean recounts the story of how he learned the value of limiting work in progress and removing blockages to allow the flow of work in an IT server lab, and how the lessons he learnt are now applied on Scrum teams doing software development.
-
Agile Architecture Interactions
James Madison shows how architects can bring agile and architecture practices together to pragmatically balance business and architectural priorities while delivering both with agility.
-
Patterns-Based Engineering: Successfully Delivering Solutions via Patterns
InfoQ spoke with Lee and Celso about the Patterns-Based Engineering: Successfully Delivering Solutions via Patterns book, discussing patterns for working with patterns, MDD and the promise of reuse. The book focuses on how to improve efforts in identifying, producing, managing and consuming patterns – leading to better software delivered more quickly with fewer resources.