The Regenerate Web
facilitating the regeneration of software teamsNavigation
User login
Syndicate
Services
Project
- 1My campus life
- delivery (3)
- duration (1)
- effort (3)
- estimation (4)
- Iterative (1)
- measurement (1)
- metrics (1)
- Planning (2)
- PMI (1)
- PMBOK
- Progressive Elaboration (1)
- risk (1)
- Rolling Wave (1)
- schedule (1)
- task (2)
- velocity (6)
- delivery (3)
- duration (1)
- effort (3)
- estimation (4)
- Iterative (1)
- measurement (1)
- metrics (1)
- Planning (2)
- PMI (1)
- PMBOK
- Progressive Elaboration (1)
- risk (1)
- Rolling Wave (1)
- schedule (1)
- task (2)
- velocity (6)
Management
Browse archives
Analysis
- abstraction (1)
- metaphors (1)
- modeling (3)
- requirements (5)
- research
- semantics (1)
- Analysis (1)
- metaphors (1)
- modeling (3)
- requirements (5)
- research
- semantics (1)
- Analysis (1)
Staff
Who's online
There are currently 0 users and 1 guest online.
archives
Requirements Modeling
Submitted by regen_r8 on Sun, 2007-02-04 23:21.
agile | modeling | requirements
OK! So everyone who has had received requirements for a project that didn't "add up" please raise your hand. What about requirements that were impossible to figure out if they add up without rewriting them from scratch? What about requirements that primarily describe the current situation, and not the desired future state? How about requirements that are written more as a functional specification (I need a report that has these data elements with this sorting grouping and formatting)?