InfoQ Homepage Planning Content on InfoQ
-
/articles/many-levels-planning-agile-project/en/smallimage/maze2.jpg)
The Many Levels of Planning on an Agile Project
One of the fundamental Agile values is “we value responding to change over following a plan” which has sometimes been misintrepreted to mean we don’t need to plan on an Agile project. Nothing could be further from the truth - in reality agile organisations and projects plan at many different levels. Shane Hastie discusses the different types and approaches to planning and how the work together.
-
/articles/agile-team-fixed-price-contract/en/smallimage/image_contract-clock.jpg)
Agile Team Meets a Fixed Price Contract
Fixed price contracts are evil - this is what can often be heard from agilists. On the other hand those contracts are reality which many agile teams have to face. But what if we try to tame it instead of fighting against it? How can a company execute this kind of contract using agile practices to achieve better results with lower risk? This article will try to answer those questions.
-
/articles/5-config-mgmt-best-practices/en/smallimage/image_medal2.jpg)
5 Configuration Management Best Practices
There has been a lot of conversation going on around the configuration of applications, and how to manage it. This article explores things people can do from within their code to make their lives, and the lives of anyone else who has to administer or maintain their application, easier. These patterns have been used a number of times on ThoughtWorks projects, and they have proven their worth.
-
/articles/short-iterations-argument/en/smallimage/calendar.JPG)
A Case For Short Iterations
Dave Nicolette, Agile Coach with Valtech, addresses the question are short iterations better than long. Dave demonstrates that short iterations: allow for more rapid response to change, the opportunity to discover and fix problems more often. He also deals with the concerns that short iterations might lead to burnout and other issues.
-
/articles/agile-estimation-techniques/en/smallimage/image_scratching_head.jpg)
User Story Estimation Techniques
One of the great things about working as a consultant is the ability to try out many different ideas and adapting your personal favorite process to include things that work. This article gives the details about user story estimation techniques that Jay Fields has found effective.
-
/articles/agile-kanban-boards/en/smallimage/three-level-kanban_small.jpg)
Visualizing Agile Projects using Kanban Boards
In the spirit of "information radiators and “big visible charts” Kenji Hiranabe proposes using Kanban Boards to organize three viewpoints (Time, Task, and Team) so the whole team understands the current status of the project and can work in an autonomous, motivated and collaborative manner.
-
/articles/SOA-Agile-Friends-Or-Foes/en/smallimage/image_agile_soa.jpg)
SOA and Agile: Friends or Foes?
SOA aims at making the entire enterprise agile by using services as the building blocks for applications. Agile software development aims at making organizations agile by introducing practices that increase communication and feedback. Which is right? Which is better? Are we comparing apples and oranges? Can they be used together, and if so, how? Join us in the discussion!
-
/articles/agile-karma/en/smallimage/sunrise3.jpg)
Good Agile Karma
Agile relies heavily on discipline, rather than genius. We're told that average teams, even in the early stages, can achieve dramatic performance improvement if they are disciplined. As we do these things, the effects of our words and actions actively create, and re-create over time, the environment in which our teams and projects operate - for good or ill.
-
/articles/Agile--The-SOA-Hangover-Cure/en/smallimage/image_soa_hangover.jpg)
Agile: The SOA Hangover Cure
Author Carl Ververs who is an expert on SOA Integration and Distributed Systems writes about the application of "Agile" development philosophies that ensures that organizations can overcome architectural paralysis and get moving on those important SOA projects, while at the same time ensuring that the architecture is sufficiently flexible and adaptable for future growth.