Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Working with Scrum, Agile and Waterfall

Presentation for BA Network

Kris Scott

on 7 March 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Working with Scrum, Agile and Waterfall

The Process
What role does a Business Analyst Play in SCRUM?
Working with Waterfall and Agile
Agile Methodology
- which focuses on cutting out as much overhead as possible
Some examples:
User Stories
Product Backlog
Backlog refinement meetings
Sprint Review
More Detailed User Stories
Effort Estimation (Planning Poker)
Acceptance Criteria
Identify Tasks
Extra Documentation (but only if required)
Data mapping
- which focuses on agile management and how to better organise development team
XP (Extreme Programming)
- which includes some management elements but emphasises technical practices
- Dynamic Systems Development Method, one of the earliest iterative development methods
Lean Software Development
- visual approach to management and/or development
Sprint Plans
Sprint Burndown
Do Tasks
Daily Scrum (or stand up)
Daily Scrum (or stand up)
Daily Scrum (or stand up)
Acceptance Criteria
Sprint retrospectives
Sprint review
Daily Scrum (or stand up)
Business Analyst is the Product Owner
Must have
authority to make decisions
be able to prioritise
authority to confirm work is 'done'
available to the rest of the team
Business Analyst as a Team Member
Must be able to:
work with developers and other team members
identify tasks required for completion of a user story
ensure acceptance criteria are robust
test functionality when required
detailed analysis when required
be available on a daily basis
Depends on the
project, product and person
Waterfall Methodology
known model - 1970s
sequential process
documentation before 'code' is written
requirements documented to an unambiguous / testable level
SCRUM Methodology
newer model
iterative process
'code' written before documentation
document only out of necessity
Requirements elicitation
Benefits elicitation
Knowledge elicitation
Requirements Documentation
Functional specification
User interface specification
Technical specification
Develop solution

Systems testing
User acceptance testing
The waterfall process
Working with Scrum, Agile and Waterfall
The role of the Business Analyst in Waterfall
Assist in development of business case
Elicit requirements / benefits
Stakeholder analysis
Documentation production
Use Cases
Requirements Catalogue
Class / Entity Models
Process Flows
Liaison with Systems Analysts, Testers, IT project managers, project managers etc
Depends on project
Not This!
Which is best?
and many more...
Full transcript