Agile Requirements

Making large projects more agile

We are on a large project for a client (>100 developers) and one of the issues that keeps coming up is how can we reduce the cycle time. At one point in the project we were using a waterfall model, all the requirements had to be done and approved before …

Read More

Three keys to success in Agile Modeling

For Agile development teams, there are three key modeling concepts that are critical for successful requirements modeling. First, create model artifacts “just in time” and make them “just good enough”. Creating model artifacts just in time means not trying to produce detailed models too far in advance of when they …

Read More

Agile Requirements – The use case narrative

Last month I wrote about Agile Requirements and a concept called GRIT or Great Requirements in Total. The idea behind GRIT is that it is important to deliver great requirements models along with great working software. GRIT recognizes that software is a product, not a project, and should be managed …

Read More

Agile Requirements – no BRUF just GRIT

The first principal of agile software development is that the highest priority is to satisfy the customer through early and continuous delivery of valuable software. This is a significant departure from traditional waterfall methods in which delivery of working software happens not early, but very late in the process. In …

Read More

Agile Development

Someone asked me the other day about agile development. Should we do it? Can we reduce the time we spend on requirements if we are doing agile development? Is it only good for some kinds of projects? If you’re reading this blog there is a good chance you know about …

Read More

Agile… Again

Some people have pointed out that the reason I don’t like agile methods is because I am trying to sell services which depend on “traditional” requirements. The reason I like “traditional” requirements is because I don’t like screwed up projects. Everyone is trying to sell something and the Agile gurus …

Read More

Traditional software requirements don’t work?

Recently I have talked to a number of clients that have referred to the fact that traditional requirements don’t work. It didn’t take long to ferret out that they were referring to creating software requirements using a waterfall model. I want to state for the record that I completely agree …

Read More

The impact of Agile development techniques on Product Management

Two weeks ago I attended the monthly meeting of the Austin Product Marketing and Management group. The session was titled Agile Software Development and its Impact on Product Management and was a panel discussion with three panelists and 30+ audience members. It was the second largest gathering I have seen …

Read More

Can’t we all just get along?

I got a notice today regarding the next meeting of the Austin PMM chapter where the topic will be Agile Software Development Techniques and Their Impact on Product Management. A discussion around the role of a PdM in an Agile environment is one that has been kicking around our office …

Read More

One Size Fits None

The November 15, 2005 issue of CIO Magazine leads with the headline “Rethinking Requirements” and includes an article titled Fixing the Requirements Mess. Now, I just know someone is going to come along and burst my bubble by revealing this is a recycled story the editors run every few months, …

Read More