1860 Module 5 Project Requirements PDF

1. The component of the project management plan that describes how scope will be defined, developed, monitored, controlled, and validated 2. Building upon the major deliverables, assumptions, and constraints mentioned in the project charter. process to obtain conditions or capabiliti...

1. The component of the project management plan that describes how scope will be defined, developed, monitored, controlled, and validated 2. Building upon the major deliverables, assumptions, and constraints mentioned in the project charter. process to obtain conditions or capabilities that are necessary to be present in the product, service, OR result to satisfy a business and project need 3. Updated as more information becomes available. must include a minimum a project scope description, product user acceptance criteria, and detailed information on all project deliverables 4. A deliverable oriented grouping of the work that defines the total scope of the project. the WBS breaks all the work required for the project and into deliverables, and groups them into a logical hierarchy Financial stakeholders should sign off on this Everything you need to deliver Created before the WBS, after the Project Charter Nouns not verbs - paint the room > room painted Work packages start with verbs - they are actual tasks Notice the numbering system Go in chronological order when possible 1. based on previously done work 2. managers, usually not involved, develop 3. the team develops together Try to be as ‘lean’ or efficient as possible, and bring as much value as possible A. A hierarchical structure reflecting the products elements and deliverables B. Define, analyze, and validate stakeholder needs and requirements to minimize conflict and eliminate ambiguities or conflicting requirements C. Studying a procedure or business. looking at the big picture. to identify goals and then create systems and processes to achieve them D. An interdisciplinary field that focuses on designing, integrating, and managing complex systems over their life cycles E. Earned value analysis, using a set of measures for scope, schedule, and cost to determine the performance on the project F. A multidisciplinary approach done with cross-functional teams to identify and reduce costs while maintaining product quality All work to be delivered is on product backlog - but not all on log may be delivered in time The user/buyer/client determines priority Scrum master and product owner discuss priority Give each item a number and that’s their priority rank #1 is most important, lowest number is least important - each item has a number For the ‘w’s, keep on product backlog but at the bottom The product team will review the features on the product backlog and then map them to this grid 1. Performance: the more functionality we provide, the more satisfied our customers become 2. Must be: product features that are simply expected by our customers. If the product doesn't have them, it would be considered incomplete or just plain bad 3. Attractive: these are unexpected features which, one presented, cause a positive reaction. They are exciters or delighters 4. Indifferent: these are features, whether present or absent don't make a real difference in our reaction towards the product Another scrum approach and came from ‘extreme programming’ 1. A set of related requirements or functionalities that provide value 2. Large, related body of work intended to hierarchically organize a set of requirements and deliver specific business outcomes 3. A brief description of an outcome for a specific user 4. A small amount of work that has been decomposed to allow assignment and tracking Breaks down the priorities into manageable tasks for the sprints Make up fake people, created in a way as if they are a real client/customer very detailed, as if they are a real person 1. Independent: can be completed on its own 2. Negotiable: one or two sentences long. details can be worked out through discussion 3. Valuable: provide value to the customer 4. Estimatable: a good approximation 5. Small: can be completed within one iteration 6. Testible: know when it's complete Very similar to the WBS but different names/labelling system