CS 111 SOFTWARE ENGINEERING 2

SOFTWARE
ENGINEERING
2
2 N D SEMESTER A.Y. 2024-2025

VENUS B. DORADO
Course Facilitator
Introduction to Scrum
 What is Scrum &
Agile?
 Agile Manifesto
 Scrum vs.
Traditional Methods
 Facts and Fiction
About Scrum
 Typical Scrum
Timeline
 What is SCRUM & AGILE?
Agile Project
Management

Agile Project Management is

an iterative approach to
managing software
development projects that
focuses on continuous
releases and incorporating
customer feedback with every
iteration.
 SCRUM vs AGILE

Scrum and Agile are terms

often used in the context of
project management and
software development, and
they are related concepts but
not interchangeable.
 SCRUM vs AGILE
AGILE is a set of principles and values
that guide a flexible and iterative
approach to software development
and project management.
SCRUM is one of the most popular
frameworks within the Agile
methodology. It provides a specific
set of roles, ceremonies, and
artifacts to help teams implement Agile
 SCRUM vs AGILE
•Agile is like the
mindset or philosophy.
•Scrum is like a step-
by-step guide or a
specific recipe within
 What is SCRUM?
Scrum Process

Scrum is a way of working that helps teams organize and

complete work effectively. It focuses on breaking big tasks
into smaller pieces, working on them step by step, and
constantly improving as a team.
It uses:
•Roles like the Scrum Master (coach), Product Owner
(planner), and the team (doers).
•Meetings to plan, check progress, and review work.
•Tools like lists of tasks (backlogs) to keep things
organized.
 What is SCRUM?
Scrum Process

The name comes from the sport

of rugby, where scrum is a
formation where everyone plays a
specific role, but everyone is
working towards a quick adoption
of strategies.
Scrum Methodology
An Introduction to Scrum
Process

The scrum methodology was

developed as a response to rigid
project management approaches
such as the waterfall method,
which didn’t adapt to the needs of
agile product and software
development teams.
Agile Manifesto
 The Agile Manifesto
The Agile Manifesto is a set of guiding values and
principles for agile software development. It was
created in 2001 by a group of software developers who
gathered at the Snowbird ski resort in Utah.

The four core values are:

Individuals and Working software
Interactions over over Comprehensive
Processes and Documentation
Tools

Customer Responding to
Collaboration over change over
Contract Following a Plan
Negotiation
Individuals and interactions
over Processes and Tools

Emphasizes the importance of

people working together effectively
and communicating directly, rather
than relying solely on tools or following
rigid processes.
 Working software over
Comprehensive Documentation
Prioritizes the creation of functional
software over extensive
documentation.
While documentation is important,
the focus should be on delivering a
working product to the customer.
Customer collaboration over
Contract Negotiation

Advocates for close collaboration

with customers throughout the
development process. This involves
actively involving customers in
discussions, getting feedback, and
adapting to their changing needs.
 Responding to Change over
Following a Plan

Recognizes the inevitability of

changes in requirements and priorities.
Agile teams should be adaptable and
responsive to change, rather than
strictly adhering to a predefined plan.
 Summary

The Agile Manifesto says:

1. Focus on working together, not just on rules and

tools.
2. Make working software, not just lots of documents.
3. Talk and work closely with customers, not just follow
contracts.
4. Be ready to change plans, not just stick to them.
Agile Manifesto
12 Principles
 The 12 Principles of Agile Manifesto
The 12 principles of the Agile Manifesto provide more specific
guidance on how to apply the four core values.

1.Customer satisfaction through continuous delivery of

valuable software:
• Prioritize delivering working software frequently, with a preference
for shorter timescales.
2.Welcome changing requirements, even late in development:
• Be responsive to changing customer needs and requirements,
even if changes occur late in the development process.
3.Deliver working software frequently, with a preference for
shorter timescales:
• Aim to have a working product at the end of each iteration or
sprint, delivering value to the customer regularly.
4.Collaboration between business stakeholders and developers
throughout the project:
 The 12 Principles of Agile Manifesto
The 12 principles of the Agile Manifesto provide more specific
guidance on how to apply the four core values.

5. Build projects around motivated individuals, giving them the

support and environment they need:
• Trust and empower the team members, providing them with the
resources and support necessary to accomplish their tasks.
6.Use face-to-face communication as much as possible:
• Prioritize direct and in-person communication, as it is often more
effective than written or electronic communication.
7. Working software is the primary measure of progress:
• Use functional software as the primary indicator of project progress
rather than relying solely on documentation or plans.
8.Maintain a sustainable pace of work for the team:
• Avoid overloading team members with excessive work. Sustainable,
steady progress is more important than working at an
 The 12 Principles of Agile Manifesto
The 12 principles of the Agile Manifesto provide more specific
guidance on how to apply the four core values.

9. Continuous attention to technical excellence and good

design:
• Emphasize the importance of quality and good design practices
throughout the development process.
10.Simplicity—the art of maximizing the amount of work not
done—is essential:
• Favor simplicity in both the software and the development process.
Eliminate unnecessary work and focus on what is truly essential.
11.Self-organizing teams make the best decisions:
• Encourage and trust teams to make decisions and organize
themselves, as they are often in the best position to determine
how to achieve their goals.
12.Regular reflections on how to become more effective, then
Ty p i c a l S c r u m T i m e l i n e