1. Team Skill 4 –Scope (Chapters 18-19- Requirements Text) Team Skill 4 –Scope (Chapters 18-19- Requirements Text) Sriram Mohan/Steve Chenoweth 1

2. Outline Scope ◦ Establishing Project Scope ◦ Managing Your Customer 2

3. The Shape of Project Scope 3 Achievable scope Brook’s Law ◦ Adding labor to a late project makes it later ◦ Why? What happens when the scope is beyond available resources?

4. Requirements Baseline Itemized list of features intended for a given release ◦ Must be acceptable to customer ◦ Must have reasonable probability of success 4

5. Setting Priorities Customers should decide priorities. ◦ Why? 5

6. Example Priorities 6 #FeaturePriority 1External RDB supportCritical 4Portability to a new OSCritical 3Ability to clone new projectImportant 5New project wizardImportant 2Implementation of tool tipsUseful

7. Assessing Effort Developers should estimate effort ◦ Why? 7

8. Example Effort 8 #FeaturePriorityEffort 1External RDB supportCriticalMedium 4Portability to a new OSCriticalHigh 3Ability to clone new projectImportantLow 5New project wizardImportantLow 2Implementation of tool tipsUsefulLow

9. Assessing Risk Implementation of a feature will cause an adverse impact on the schedule and the budget 9

10. Setting the Baseline Include all "Critical" items Add some "Important" items as budget allows Can you deliver all “Critical” items on time? 10

11. Example Baseline 11 #FeaturePriorityEffort 1External RDB supportCriticalMedium 4Portability to a new OSCriticalHigh 3Ability to clone new projectImportantLow Baseline 5New project wizardImportantLow 2Implementation of tool tipsUsefulLow

12. Suggestions for Dealing with the Client During Development Communicate Include customer in decisions about scope reduction Negotiate changes to requirements Give yourself some slack Avoid "feature creep" 12