back to top

our blog


agile project management

Agile ALM: The Future of Delivery Automation

by Jim Highsmith, 07 June 2011

In the old days, you know those days when waterfall reigned and a certain 3-letter acronym product was widely used, Application Lifecycle Management (ALM) systems were large, monolithic, document-centric, and universally hated by rank-and-file engineering staffs. Then came the Agile movement with the manifesto and it’s first principle which stated, “Individuals and Interactions over Process [...]

Tell me more >
The “To Do Less” List

by Jim Highsmith, 01 June 2011

“Everyone tries to do too much: solve too many problems, build products with too many features. We say ‘no’ to almost everything. If you include every decent idea that comes along, you’ll just wind up with a half-assed version of your product. What you want to do is build half a product that kicks ass.” [...]

Tell me more >
Avoiding Iteration Zero

by George Dinwiddie, 25 May 2011

Teams new to Agile often realize that they have a lot to do before they get their new development process at full speed. Looking at this big and unknown hill in front of them, many Agile teams choose to do an Iteration Zero (or Sprint Zero) to prepare before they start delivering regular increments of [...]

Tell me more >
Public Impediments List !!!

by Joe Little, 24 May 2011

This is essential in Scrum.Why public? Well, so everyone can see and offer feedback on what are our team's biggest impediments.Oh, and the list is prioritized. If the priorities are not obvious, then the ScrumMaster breaks ties.And the real juice is th...

Tell me more >
Building Trust, One Iteration at a Time

by Esther Derby, 26 April 2011

A while back I talked to a CEO of a contract development shop.  He wondered how Agile could help him with fixed price, fixed scope contracts to deliver software. Of course, the requirements that come with these contracts are never complete or completely accurate. The first thing that comes to mind is to stop making [...]

Tell me more >
Scope Issues in an Agile Project

by Jim Highsmith, 14 April 2011

I was talking with a colleague the other day about troubles with scope management in an Agile project. She was lamenting problems that were arising with a particular client who was concerned about the progress of the delivery team. Since Agile teams use time boxed iterations and let scope adjust, this shouldn’t be a problem—should [...]

Tell me more >
Impediment Management and the Agile Triangle

by Chris Sterling, 29 March 2011

The Agile Triangle, a concept that was discussed by Jim Highsmith in his book Agile Project Management: Creating Innovative Products, describes how teams and organizations can go beyond the traditional Iron Triangle in defining project success criteria. In the Agile Triangle, the traditional project constraints of schedule, cost, and scope are confined to one point [...]

Tell me more >
Track Your Agile Projects with a Project Burndown Chart

by Kelly Waters, 07 February 2011

Agile project management often needs more than the practices provided as standard by agile methods. Tracking project status is one area where I think that’s true. Scrum includes the concept of a Sprint Burndown Chart.  For those that aren’t familiar with it, it’s a simple yet very powerful concept. Here’s how it works… At the […]

Tell me more >