Team Skill 4 –ScopeTeam Skill 4 –Scope(Chapters 18-19- (Chapters 18-19-

Requirements Text) Requirements Text)

Sriram Mohan/Steve Chenoweth

1

OutlineOutline

Scope◦ Establishing Project Scope◦ Managing Your Customer

2

The Shape of Project ScopeThe 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?

Requirements BaselineRequirements Baseline

Itemized list of features intended for a given release◦ Must be acceptable to customer

◦ Must have reasonable probability of success

4

Setting PrioritiesSetting Priorities

Customers should decide priorities.◦ Why?

5

Example PrioritiesExample Priorities

6

# Feature Priority

1 External RDB support Critical

4 Portability to a new OS Critical

3 Ability to clone new project Important

5 New project wizard Important

2 Implementation of tool tips Useful

Assessing EffortAssessing Effort

Developers should estimate effort◦ Why?

7

Example EffortExample Effort

8

# Feature Priority Effort

1 External RDB support Critical Medium

4 Portability to a new OS Critical High

3 Ability to clone new project Important Low

5 New project wizard Important Low

2 Implementation of tool tips Useful Low

Assessing RiskAssessing Risk

Implementation of a feature will cause an adverse impact on the schedule and the budget

9

Setting the BaselineSetting the Baseline

Include all "Critical" items Add some "Important" items as budget allows Can you deliver all “Critical” items on time?

10

Example BaselineExample Baseline

11

# Feature Priority Effort

1 External RDB support Critical Medium

4 Portability to a new OS Critical High

3 Ability to clone new project Important Low

Baseline

5 New project wizard Important Low

2 Implementation of tool tips Useful Low

Suggestions for Dealing with the Client During Suggestions for Dealing with the Client During DevelopmentDevelopment

Communicate Include customer in decisions about scope reduction Negotiate changes to requirements Give yourself some slack Avoid "feature creep"

12