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