Scribd
Upload
42 views12 pages

Software Development Process: Agile + Scrum Help Implementing A Simple & Workable Process !

The document discusses software development processes and the agile Scrum framework. It defines heavyweight and lightweight methodologies, describing Scrum as a lightweight agile methodology. It outlines Scrum values and roles, including the product owner who defines goals and features, the Scrum master who coaches the team, and the Scrum team who selects requirements and is responsible for development. The document explains Scrum artifacts like the product and sprint backlogs and burn down chart. It also details Scrum meetings and processes, emphasizing that everything in Scrum is time-boxed.

Uploaded by

vinh1964
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
42 views12 pages

Software Development Process: Agile + Scrum Help Implementing A Simple & Workable Process !

The document discusses software development processes and the agile Scrum framework. It defines heavyweight and lightweight methodologies, describing Scrum as a lightweight agile methodology. It outlines Scrum values and roles, including the product owner who defines goals and features, the Scrum master who coaches the team, and the Scrum team who selects requirements and is responsible for development. The document explains Scrum artifacts like the product and sprint backlogs and burn down chart. It also details Scrum meetings and processes, emphasizing that everything in Scrum is time-boxed.

Uploaded by

vinh1964
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

Software Development Process

Agile + Scrum help implementing


a simple & workable process !

[email protected]

Software Development in Internet time

Quality Model

Faster time to market

Higher quality

Processes based on
these models are good
but not enough

Agile/Lightweight Methodologies
Software Methodology
Set of rules and practices
Heavyweight
Many rules, practices and documents (ISO, CMMI, RUP)
Lightweight
Few rules and practices or some that are easy to follow.

Scrum
XP (eXtreme Programming)
ASD (Adaptive Software Development)
Crystal
FDD (Feature-driven Development)

Agile movement
3

Scrum Value stream

Product Demo after each Sprint


(1-4 weeks)

Late Product Demo

Not good

Agile + Scrum Values


Deliver working software frequently, from a couple of weeks to
a couple of months
Working software is the primary measure of progress
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Simplicity: do the simplest things
that could possible work.
Designs have to be as simple
as possible and still work
Do we dream ?

What does it mean Scrum ?

Making a list of things that


you need to get done for the
project (product backlog)
Prioritizing that list
Estimating how long each
item in the list will take
Meeting regularly to see the
status of items and make
small adjustments
Keep track of how much
work remains until the project
is finished (burndown chart)
Everything is time-boxed
6

Global view of Scrum

Documentation in Scrum ?
Only 3 main artifacts
Product backlog
a single list of features prioritized
by value delivered to the customer

Sprint backlog
a list of the specific development
tasks required to implement a
feature

Burndown Chart
show the progress
8

Roles in Scrum
Product owner

defines the goals of the development, the


features to be realized and their proirities
(create Product Backlog). He also
assumes responsibility for the project.

Scrum Master

coaches the development team, help the team


for realizing the goals fixed for the Sprint.

Scrum Team
consisting of 59 people, to discuss with
Product Owner to select requirements to
be developed for each Sprint, responsible
for development
9

Scrum process

10

Scrum: everything is time-boxed


Sprint planning meeting
8h for a Sprint of 4 weeks
4h for a Sprint of 2 weeks
Daily meeting
No longer than 15 minutes
Answer 3 questions: what
done, what to do today, issue
need help to resolve
Sprint Review meeting
to discuss what was done and
what was not done
to demonstrate what was built
to the product owner and get
her feedback

Sprint Retrospective meeting


to identify what worked and
what did not work during the
current Sprint

11

Is Scrum suitable for you ?

12

You might also like