1. Class 5 – Getting to the Scope  How do we gather requirements?  User Stories  Functional Components  Agile Stories vs Waterfall Requirements  Drivers Exercise  Client Teams Checkpoint

2. Starting with our list of stakeholders we identify from whom we need information All stakeholders or just a few? What are ways to gather info? Having an “Agile” mentality what seems best? In interviews listen for: GOAL: What they want and why they want it Listen also for priority clues! Example: “What we really need is…” “You know what would be cool…” MoSCoW Method (Must, Should, Could, Wont) How Do we Gather Requirements?

3. From Interviews/Observations we draft User Stories From Users Stories we can derive a list of components or functional requirements How Do we Gather Requirements?

4. Requirements & Stories How would you define what a Functional Requirement is? What is an example…maybe from K? Now what is a User Story? Can someone give an example? User Stories follow a template: I as a would like to be able to so that I can.

5. Requirement: The system should let me pull reports on loan data. User Story: As a Loan Analyst I want the ability to export Loan Balances, Loan Types, and Payment Statistics so that I can measure good and bad performance across the loan portfolio Requirements & Stories

7. Out of Scope (i.e. Won’t Have)

8. Drivers Exercise

9. Client Project task this week Get teams together by Friday! Confirm with Prof on group size. Tuttle – (9 groups of 5) White – (4 groups of 5) & (4 groups of 4)