Monthly Archives: June 2006

What’s in a release?

There is a bit of irony in building a tool without a tool. It’s like building a table for a workbench so you can then build a table. So far we have been very efficient in our process of building our Requirements Management tool. We have a small team, with white boards and a wiki. [...]

How much time to spend on requirements…

Project teams often struggle with how much time to spend on requirements. I was reading the book “Just Enough Requirements Management” by Alan Davis and liked what he had to say.
“Documenting requirements is a lot like purchasing insurance. If you do not buy enough, you can end up with disastrous consequences. If you buy too [...]

Codecamp 2.0

If you are in the Portland / Vancouver area check out Code Camp 2.0 It looks to be an interesting weekend - if you like to code.

The Ying Yang of Process

This article states that “developer misunderstandings of user requirements are the leading cause of defects in software.”  I do believe the developer should be better connected to the actual requirement. However even when using different methodologies, like Agile, there can be a disconnect. Documentation, conversations, phone calls, meetings after meetings all take place before the [...]

What is an Analyst?

What exactly does an analyst do?  This role varies from project team to project team – but the essence is the same – understanding and documenting an approach to a problem then figuring out how to communicate it back to the stakeholders and the project team.
Karl Wiegers has a nice summary of the Analyst position [...]

Business Rules & Requirements

I’ve been asked why we separated business rules from requirements in Contour.  When we designed the application we decided to keep rules separated so they could be reused and linked to multiple requirements.  I decided to do a little research to see if that makes sense.
Ellen Gottesdiener of ebg consulting has written a number of articles on [...]

Naming Woes

I don’t remember having a hard time with naming things until recently.  We needed to name this new venture and assumed something clever would just come to us.  Fast forward a few months and we still didn’t have a name, so we decided to get serious.
We scheduled naming brainstorm sessions, started a wiki, read the [...]