AGILE METHODOLOGIES AND SCRUM, Slides of Software Engineering

The above uploaded documents covers the following topic in details..these are some verified and important lectures for those studnts or teachers who want to have some knwldge about the following topic along with pratice questions

Typology: Slides

2021/2022

Available from 08/18/2022

SamenKhan
SamenKhan 🇵🇰

231 documents

1 / 43

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
SOFTWARE REQUIREMENTS
ENGINEERING
LECTURE # 2
AGILE
METHODOLOGIES
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a
pf2b

Partial preview of the text

Download AGILE METHODOLOGIES AND SCRUM and more Slides Software Engineering in PDF only on Docsity!

SOFTWARE REQUIREMENTS

ENGINEERING

LECTURE # 2

AGILE

METHODOLOGIES

Presentation

Outline

Agile

Methodologies

Scru

m

Extreme Programming

Adaptive Software

Development

Feature Driven

Development

Lean Development

Some Agile

Methodologies

6

Scrum

 Extreme Programming

(XP)

 Adaptive Software Process

 Feature-Driven

Development (FDD)

 Lean Development

Scrum

Roles

 Scrum

Master

 Team

 Product

Owner

The SCRUM

Master [3,5]

9

 In the Scrum process, Scrum Master

has a role of coach , director of

movie script

 The job of the scrum master is to make

sure that the project is progressing

smoothly

 He sets the meetings, monitor the

work and facilitate release

planning

 Two important task of scrum

master are:

 Protecting the team from outside

disturbance

 Clears the ways for the team by helping

them to solve their

problems

The Product

Owner [6]

11

 In Scrum, the Product Owner is the

one person

responsible for a project‟s success.

 The Product Owner outlines work

in the Product

backlog

 Product Owner makes sure that right

features to be included in the product

backlog

 Of course, he or she must also

consider the stakeholders and the

team

Scrum

Artifacts

 Product

Backlog

 Sprint

Backlog

 Sprint

 Burn down

Chart

Sprint

Backlog

14

 Contains the set of prioritized Product Backlog items that

are currently being

worked

on

Sprint

[7]

15

 The product is developed in a series of 1-to-4-week

iterations, or sprints.

 The sprint has 4 major steps:

Develop the product further.

Wrap up the work - get it ready to be evaluated and

integrated.

Review the work done in this sprint. Adjust for any changes in

requirements or plans.

 Results in an incremental delivery of

usable product

Scrum

Meetings

 Release Planning

Meeting

 Sprint Planning Meeting

 Sprint Review Meeting

 Sprint Retrospective

Meeting

 Daily Scrum Meeting

Release

Planning

18

Sprint Planning

Meeting

20

 A meeting at the beginning of a sprint where the

sprint is planned.

 Items from the Product Backlog are selected to be

completed in the sprint ,

based on the priorities set by the Product Owner.

Eight hour time limit

 (1st four hours) Product Owner + Team: dialog for prioritizing the

Product Backlog

 (2nd four hours) Team only: plan for the Sprint, resulting in the

Sprint Backlog

Sprint Review

Meeting [7]

21

 Review the work that was completed and not

completed

 Present the completed work to the stakeholders

(a.k.a. “the demo”)

 Four hour time limit