Feb
5
The Vanished
February 5, 2007 |
Here are the tasks in Requirements Analysis that are currently not planned to make it into that KA in 2.0:
- Create Business Domain Model. This one is up in the air–it may move to Solution Assessment and Validation, since it’s really about assessing the functioning of a working system. If you have feelings about it either way let me know.
- Analyze User Requirements, Analyze Functional Requirements, and Analyze Quality of Service Requirements. These all got cut for the same reason: they’re oriented towards software development and nothing else. For 2.0, we wanted to make sure the BABOK tasks applied equally well, for instance, to documenting a business process. Yes, you could call that a “functional requirement” even if there was no software but it was a major sticking point for every BPM person I talked to. So, they were replaced.
- Determine Requrements Attributes. Moved to Requirements Planning and Management.
- Document Requirements. Er, we have an entire Requirements Communication KA. This belongs there.
- Validate Requirements. This task should be covered in Solution Assessment and Validation.
Comments
1 Comment so far
What I'm Reading- Communicating requirements to different stakeholdersBA Rocks!
- Product Management Reader: 13Nov08The Productologist
- Satisficing SprintsTyner Blain
- The Decline and Fall of AgileJames Shore
- Theory is Obsolete and other touchy topicsHerding Cats
- Agile Product Managers and Agile Product Owners Living Together in Harmonyenthiosys agile product management
- Rapid Results and the Big Systems ProjectProject X Discussions
- PMBOK, Agile and the need for TheoryHerding Cats
- A 5th element for the Agile ManifestoOn Product Management
- More on Agile Product Managers and Product OwnersScaling Software Agility
Hello
I thought I would comment on Validating Requirements.
Validating requirements is not a part of the solution design. It is definitely a step in the requirements elicitation and definition process.
Cheers
Better Projects