-
Johanna’s Books
Category Archives: requirements
Traceability Matrix and Agile
I received two questions this week about how well does agile allow you to do traceability matrix. Very well is the short answer. Here’s why. If you commit to implementing features (not chunks of architecture) based on user stories in … Continue reading
Beyond Bold
I’m an assertive, bold, blunt, and direct person. I try to live within the bureaucracies I encounter, but I don’t always succeed. I’m at SD West this week, where I did a half-day tutorial Monday and am presenting two … Continue reading
Implicit Requirements are Still Requirements
I have an all-in-one machine, a fax/copier/scanner/printer, that I use for copying, scanning and primarily faxing. It’s fine fax machine. And it’s a great copier. But when I hook it up to my computer for scanning to a file, … Continue reading
When Requirements Spawn Requirements
A colleague asked me what to do when you’re in an iteration and you realize that the story you’re working on spawns other requirements. I suggested that the person add them to the product backlog (the backlog of everything … Continue reading
Posted in requirements
Tagged agile, feedback, iterative planning, project team, technical debt, transition to agile
1 Comment
Projects Have Requirements and Goals
I’m in the midst of writing the PM book (which is why I haven’t blogged much). One of my tips is that projects have both requirements and goals–and that the PM (at least) needs to know the difference. A … Continue reading
Single Point Requirements Require Iteration
Don has a great post on Single Point Requirements. You get one example of the requirements: “This product needs to do this. Just this.” Sure enough some months (or years) later, that single example is not sufficiently general to … Continue reading
Producing Software is the Art of Requirements Refinement
Well, that’s certainly a provocative title. Let’s see if I can back it up :-) First, read Keith Ray‘s Engineering post, where he says “software development is a cooperative “game” in creating and deploying “knowledge” and various people-oriented practices … Continue reading
Rank Requirements
One of the questions I ask project teams is how they know what to do when. Most of the time, the developers look at me as if I’ve grown two heads and say, “Well, we look at the requirements. … Continue reading
Describing Requirements
In my last post, I argued that functional and non-functional requirements are unsuitable for the art of describing requirements. I prefer to discuss attributes of the system instead, and then talk about functionality. (Gause and Weinberg wrote Exploring Requirements, … Continue reading
Users Can’t Know Their Requirements Early
I’ve been thinking more about requirements. In the most recent two assessments I’ve done, both organizations have been stuck on thinking they could define their requirements before design and implementation. IWBNI (It Would Be Nice If) users could know … Continue reading
Posted in requirements, user experience
Tagged agile, iterative planning, product development
Leave a comment
