Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Scrum And Agile Requirements
Upcoming SlideShare
Loading in …5
×

Scrum And Agile Requirements

13,655 views

Published on

Published in: Technology, Business
0 Comments
23 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
13,655
On SlideShare
0
From Embeds
0
Number of Embeds
31
Actions
Shares
0
Downloads
520
Comments
0
Likes
23
Embeds 0
No embeds

No notes for slide
  • But before we start I wanted to start with the agile manifesto to have people understand the spirit of agile.
  • But before we start I wanted to start with the agile manifesto to have people understand the spirit of agile.
  • But before we start I wanted to start with the agile manifesto to have people understand the spirit of agile.
  • But before we start I wanted to start with the agile manifesto to have people understand the spirit of agile.
  • But before we start I wanted to start with the agile manifesto to have people understand the spirit of agile.
  • Communicate: ie. Testers
  • Communicate: ie. Testers
  • Communicate: ie. Testers
  • Communicate: ie. Testers
  • Communicate: ie. Testers
  • And nothing, no docs is also common!
  • And nothing, no docs is also common!
  • And nothing, no docs is also common!
  • And nothing, no docs is also common!
  • And nothing, no docs is also common!
  • Waterfall processes need to create these
    An SRS should be: Correct, Unambiguous, Complete, Consistent,Ranked for importance and/or stability, Verifiable, Modifiable, Traceable
  • Waterfall processes need to create these
    An SRS should be: Correct, Unambiguous, Complete, Consistent,Ranked for importance and/or stability, Verifiable, Modifiable, Traceable
  • Waterfall processes need to create these
    An SRS should be: Correct, Unambiguous, Complete, Consistent,Ranked for importance and/or stability, Verifiable, Modifiable, Traceable
  • Waterfall processes need to create these
    An SRS should be: Correct, Unambiguous, Complete, Consistent,Ranked for importance and/or stability, Verifiable, Modifiable, Traceable
  • Who has the ball?
  • 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.
  • 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.
  • 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.
  • Scope: 2 kinds of scope Functional Scope and Design Scope
  • Scope: 2 kinds of scope Functional Scope and Design Scope
  • Scope: 2 kinds of scope Functional Scope and Design Scope
  • As you start to identify use cases you’ll start to decide on the functional scope as well as the behavior of the system.
  • As you start to identify use cases you’ll start to decide on the functional scope as well as the behavior of the system.
  • As you start to identify use cases you’ll start to decide on the functional scope as well as the behavior of the system.
  • Cockburn suggests using 2 tools
  • The actor-goal list gives a starting point for use case creation.
  • Describe which system is under discussion
  • Describe which system is under discussion
  • Describe which system is under discussion
  • Summary: show context, show sequence, help organize the project
    User Goals: are the heart of the functionality
    Subfunctions: usually shouldn’t be written separately!
  • Summary: show context, show sequence, help organize the project
    User Goals: are the heart of the functionality
    Subfunctions: usually shouldn’t be written separately!
  • Summary: show context, show sequence, help organize the project
    User Goals: are the heart of the functionality
    Subfunctions: usually shouldn’t be written separately!
  • User stories have gotten a lot of attention
  • A user story is 3 things, only a small part of it is written down.
  • A user story is 3 things, only a small part of it is written down.
  • A user story is 3 things, only a small part of it is written down.
  • Intuit
    Ideo
  • It’s not a one time event.
  • Interdependence - constraint
  • ×