Scrum And Agile Requirements

Editor's Notes

1. But before we start I wanted to start with the agile manifesto to have people understand the spirit of agile.
2. But before we start I wanted to start with the agile manifesto to have people understand the spirit of agile.
3. But before we start I wanted to start with the agile manifesto to have people understand the spirit of agile.
4. But before we start I wanted to start with the agile manifesto to have people understand the spirit of agile.
5. But before we start I wanted to start with the agile manifesto to have people understand the spirit of agile.
6. Communicate: ie. Testers
7. Communicate: ie. Testers
8. Communicate: ie. Testers
9. Communicate: ie. Testers
10. Communicate: ie. Testers
11. And nothing, no docs is also common!
12. And nothing, no docs is also common!
13. And nothing, no docs is also common!
14. And nothing, no docs is also common!
15. And nothing, no docs is also common!
16. Waterfall processes need to create these An SRS should be: Correct, Unambiguous, Complete, Consistent,Ranked for importance and/or stability, Verifiable, Modifiable, Traceable
17. Waterfall processes need to create these An SRS should be: Correct, Unambiguous, Complete, Consistent,Ranked for importance and/or stability, Verifiable, Modifiable, Traceable
18. Waterfall processes need to create these An SRS should be: Correct, Unambiguous, Complete, Consistent,Ranked for importance and/or stability, Verifiable, Modifiable, Traceable
19. Waterfall processes need to create these An SRS should be: Correct, Unambiguous, Complete, Consistent,Ranked for importance and/or stability, Verifiable, Modifiable, Traceable
20. Who has the ball?
21. Various quotes about what a use case is, notice the word behavior in each one. Doesn’t have to be software, can be a business process.
22. Various quotes about what a use case is, notice the word behavior in each one. Doesn’t have to be software, can be a business process.
23. Various quotes about what a use case is, notice the word behavior in each one. Doesn’t have to be software, can be a business process.
24. Scope: 2 kinds of scope Functional Scope and Design Scope
25. Scope: 2 kinds of scope Functional Scope and Design Scope
26. Scope: 2 kinds of scope Functional Scope and Design Scope
27. As you start to identify use cases you’ll start to decide on the functional scope as well as the behavior of the system.
28. As you start to identify use cases you’ll start to decide on the functional scope as well as the behavior of the system.
29. As you start to identify use cases you’ll start to decide on the functional scope as well as the behavior of the system.
30. Cockburn suggests using 2 tools
31. The actor-goal list gives a starting point for use case creation.
32. Describe which system is under discussion
33. Describe which system is under discussion
34. Describe which system is under discussion
35. Summary: show context, show sequence, help organize the project User Goals: are the heart of the functionality Subfunctions: usually shouldn’t be written separately!
36. Summary: show context, show sequence, help organize the project User Goals: are the heart of the functionality Subfunctions: usually shouldn’t be written separately!
37. Summary: show context, show sequence, help organize the project User Goals: are the heart of the functionality Subfunctions: usually shouldn’t be written separately!
38. User stories have gotten a lot of attention
39. A user story is 3 things, only a small part of it is written down.
40. A user story is 3 things, only a small part of it is written down.
41. A user story is 3 things, only a small part of it is written down.
42. Intuit Ideo
43. It’s not a one time event.
44. Interdependence - constraint