Chapter 2. Collecting Requirements
In this chapter, you'll create a simple list that will be used to track requirements. The remaining chapters in this section will add more capabilities to this list.
Defining Requirements
Requirements can be expressed in many forms. For example, use cases are used to effectively communicate processing rules for specific scenarios. Other requirements, such as system or legal constraints, will normally be described in other formats. Deliverables, such as report definitions, are usually best defined with a sample output provided by an image or Excel spreadsheet. Rather than trying to force all requirements into a common format, it will usually work better to design the requirements-tracking system to allow multiple ...
Get Pro Project Management with SharePoint 2010 now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
