
Requirements Driven Development: A Stream-Based WBS Approach
Address
Joe Farah farah@neuma.com
by Joe Farah
Requirements. Must have. Should have. Want. OK, maybe not really requirements. But when it comes down to it, you need to understand why you're building what you're building in sufficient detail that you'll know if what you built does the job. And you need full traceability to show that you meet the requirements. Developers work to a set of requirements, but these are not the same as the product requirements, which are again different from the customers' requirements. And what about ad hoc requests? Where do they fit in?
Requirements. Must have. Should have. Want. OK, maybe not really requirements. But when it comes down to it, you need to understand why you're building what you're building in sufficient detail that you'll know if what you built does the job. And you need full traceability to show that you meet the requirements. Developers work to a set of requirements, but these are not the same as the product requirements, which are again different from the customers' requirements. And what about ad hoc requests? Where do they fit in?
Reviews (0)
Be the first to review this listing!
