1. Requirements Document Work Breakdown Structure

2. Schedule DateTooicAssignment 1-Oct-08work breakdown/features breakdown 8-Oct-08agile methodsrequirements doc 15-Oct-08acceptance criteriafeature breakdown 22-Oct-08testing - unit, tdd,design review 29-Oct-08Student Presentations 5-Nov-08Student Presentations 12-Nov-08Student Presentations 19-Nov-08DemosDemos 26-Nov-08Thanksgiving Break 3-Dec-08 Code review code review 10-Dec-08last day of instruction

3. Requirements Document DDJ – “Quick-kill Project Management” Problem Statement Problem Statement Project background Project background Stakeholders Stakeholders End-users End-users Vision and Scope Vision and Scope Vision statement Vision statement List of features List of features List of features that will NOT be developed List of features that will NOT be developed

4. Problem Statement Project background Project background summary of the problem that the project solves. summary of the problem that the project solves. a brief history of the problem a brief history of the problem an explanation of how the organization justified the decision to build software to address it an explanation of how the organization justified the decision to build software to address it why the problem exists why the problem exists the organization's history with this problem the organization's history with this problem any previous projects that were undertaken to try to address it any previous projects that were undertaken to try to address it the way that the decision to begin this project was reached the way that the decision to begin this project was reached

5. Problem Statement Stakeholders – list of stakeholders Stakeholders – list of stakeholders Individuals within the client organization that have a vested interest in the outcome Individuals within the client organization that have a vested interest in the outcome Name, title or role Name, title or role Users Users Name, title or role Name, title or role OR “the end users are individuals with an interest in…” OR “the end users are individuals with an interest in…”

6. Vision and Scope Vision statement Vision statement A description of the goal of the software A description of the goal of the software How does it fulfill the needs of the client or users? How does it fulfill the needs of the client or users?

7. Vision and Scope List of features List of features List of features or functionality that will NOT be developed List of features or functionality that will NOT be developed concise list of exactly what will and won't be built concise list of exactly what will and won't be built

8. WBS What is it? What is it? Why do we need it? Why do we need it? Are we going to get graded on this? Are we going to get graded on this?

9. What is it? In software development, this is a “feature breakdown structure”. In software development, this is a “feature breakdown structure”. Feature-by-feature catalog and description Feature-by-feature catalog and description A comprehensive classification of project scope, not an exhaustive list of work A comprehensive classification of project scope, not an exhaustive list of work

10. Why do we need it? To document agreement with client To document agreement with client To provide a define the scope of the project clearly for the team and the client To provide a define the scope of the project clearly for the team and the client Aids in planning Aids in planning Estimation Estimation Assigning responsibility Assigning responsibility It is considered poor practice to develop a schedule without first designing a WBS

11. Are we going to be graded on this? Yes Yes The way you are graded is pass/fail on this section. If you turn in documents without this they will be returned to you for revision. The way you are graded is pass/fail on this section. If you turn in documents without this they will be returned to you for revision.

12. WBS (wikipedia) 100% Rule 100% Rule Planned outcomes, not planned actions Planned outcomes, not planned actions Mutually exclusive elements Mutually exclusive elements

13. 100% Rule Represents all of the work defined by project Represents all of the work defined by project Includes all deliverables Includes all deliverables Applies to all levels of the hierarchy Applies to all levels of the hierarchy

14. Planned outcome, not planned actions (Unless an action is a deliverable) (Unless an action is a deliverable)

15. Mutually Exclusive Elements When breaking down the tasks, it is important that nothing appears on the WPS more than once When breaking down the tasks, it is important that nothing appears on the WPS more than once

16. WBS User interface User interface Business logic Business logic Database Database

17. WBS User interface User interface User Log-in page User Log-in page Account summary page Account summary page Pay bills Pay bills Business logic Business logic Combine database table data for summary Combine database table data for summary Generate data for presentation Generate data for presentation Database Database Table design Table design Query design Query design

18. WBS Numbering 1.0 User interface 1.0 User interface 1.1 User Log-in page 1.1 User Log-in page 1.2 Account summary page 1.2 Account summary page 1.3 Pay bills 1.3 Pay bills 2.0 Business logic 2.0 Business logic 2.1 Combine database table data for summary 2.1 Combine database table data for summary 2.2 Generate data for presentation 2.2 Generate data for presentation 2.3 Record transactions 2.3 Record transactions 2.4 User verification 2.4 User verification 3.0 Database 3.0 Database 3.1 Table design 3.1 Table design 3.2 Query design 3.2 Query design

19. Granularity How far do you continue this process? How far do you continue this process? Too fine = Micromanagement Too fine = Micromanagement Too course = too difficult to manage Too course = too difficult to manage Can’t estimate time to completion Can’t estimate time to completion Can’t keep track of how complete it is Can’t keep track of how complete it is Can’t turn in interim results because they are not defined Can’t turn in interim results because they are not defined

20. Granularity If a task is not a direct deliverable then it is too fine If a task is not a direct deliverable then it is too fine A task should: A task should: Be definable as an OUTCOME Be definable as an OUTCOME Have a duration no more than a week Have a duration no more than a week

21. Granularity Progressive elaboration Progressive elaboration Allows details to be progressively Allows details to be progressively

22. A word on duration A task may only take 10 hours to complete A task may only take 10 hours to complete Theoretically, that can be done by the end of the week Theoretically, that can be done by the end of the week If the person assigned this task is out of town, sick or gets hit by a bus you have a problem If the person assigned this task is out of town, sick or gets hit by a bus you have a problem

23. Estimating If you can not estimate time to completion, break the task down further If you can not estimate time to completion, break the task down further If you can not AGREE on the time to completion, list the assumptions of those in disagreement If you can not AGREE on the time to completion, list the assumptions of those in disagreement

24. Schedule Each OUTCOME must be listed Each OUTCOME must be listed A date of completion must accompany each outcome A date of completion must accompany each outcome Responsibility for each outcome must be assigned Responsibility for each outcome must be assigned All expected outcomes must be listed All expected outcomes must be listed