Planning an agile, iterative and incremental software development involves many concerns, trade-offs and judgement calls. This paper presents a number of agile planning principles to help you get it right.
This article discusses a graphic that shows the status of larger projects, how to gather the information needed, read the status chart, and when needed, show more detailed breakdown for each subproject.
This compilation of three brief articles by IBM Rational thought leaders describes how the IBM Rational Unified Process, or RUP, is not only "agile" in its own right, but also encompasses much of the guidance teams need to scale agile techniques successfully.
This overview helps project management and teams in selecting the best iterative method(s) for their projects, based on the major risks they want to tackle. The overview highlights the focus of the different methods, ie. which risks are mainly addressed. This is not a detailed course on all the methods, but references to literature are provided.
It has been argued that agile methods only work for small, collocated, self-directed teams that include on-site customers. But what if your customer cannot be on-site full-time, or your development team is distributed around the world, or your developers lack self-directed team skills? Does this mean you cannot take advantage of agile methods? This article presents a case for using key agile practices along with recommended extensions on a broader range of projects, including large and physically distributed efforts. The article motivates the use of agile methods by exposing common myths and providing information that can help managers and customers facilitate practical agility within their organizations.
With so many Continuous Integration (CI) servers to choose from, it can be difficult to decide which one is right for you. This article looks at a handful of open source CI servers, including Continuum, CruiseControl, and Luntbuild, using a consistent evaluation criteria and illustrative examples.
If you have never experienced a well-run retrospective, then it is hard to imagine what it is like by simply reading a book. Nevertheless, this chapter tries to tie many of the discussions in this book into a single experience. It is based on one real-life retrospective, but spiced up with a few pieces from other retrospectives. I'm certain the participants would recognize themselves, but I hope I have changed enough of the trivia to protect their privacy.
In the past few years there's been a blossoming of a new style of software methodology - referred to as agile methods. Alternatively characterized as an antidote to bureaucracy or a license to hack they've stirred up interest all over the software landscape. This essay explores the reasons for agile methods, focusing not so much on their weight but on their adaptive nature and their people-first orientation.