Software

Engineering 1
Week 7
Agenda
• What is Agile ?
• Agile Principles
• Scrum Framework
• Advantage and disadvantages of Scrum
• Scrum Artifacts
• Scrum roles
Agile
• an approach based on: delivering requirements iteratively and incrementally
throughout the project lifecycle
• The most popular frameworks are Scrum, Kanban, Hybrid, Lean, Bimodal, and
XP.
 Principles of Agile
• Ability to create and respond to change
• Satisfy Customers Through Early & Continuous Delivery
• Customer collaboration over contract negotiation
• Individuals and interaction over process and tools
• Responding to change over following a structured plan
• Prototyping/working solutions over comprehensive documentation
• Self-organized project teams
• Early detection of defects and problems
 Scrum Framework
• Scrum is an iterative, incremental framework for projects and product or application
development.
• Scrum structures development in cycles of work called Sprints
• A basic unit of work in scrum – Sprint – is a short development cycle that is needed
to produce a shippable product increment
• A sprint is a short, time-boxed period when a scrum team works to complete a set
amount of work.
• Sprints are at the heart of scrum and agile methodologies, and getting sprints right
will help your agile team ship better software with highest quality in shortest time
• The Sprint’s duration is from one to four weeks.
• The team should strictly follow a work plan for each Sprint
• Today, Scrum is used in small, mid-sized and large software corporations all over the
world
At the end of each sprint, stakeholders and team members meet to plan next steps
 Advantges of Scurm
• Scrum ensures effective use of time and money
• Large projects are divided into easily manageable sprints
• Developments are coded and tested during the sprint review
• Works well for fast-moving development projects
• Short sprints enable changes based on feedback a lot more easily
• adopts feedback from customers and stakeholders
Disadvantges of Scrum
• The framework can be successful only with experienced team
members
• The chances of project failure are high if individuals aren't very
committed or cooperative
• Scrum often leads to scope creep, due to the lack of a definite
end-date
• Adopting the Scrum framework in large teams is challenging
• No Big picture of the project from the beginning.
 Scrum Framework
• Scrum relies on three main artifacts which are used to manage the
requirements and track progress – the Product Backlog, the Sprint
Backlog, the Sprint Burndown Chart
• “ a backlog is a list of what’s needed to improve the product, broken
down into the necessary steps”
Scrum artifacts – Product backlog
• The Product Backlog is an ordered list of feature items that might be
needed in the project’s final product. It is a single source of
requirements.
• The product Backlog updates as new requirements, fixes, features, and
details are being changed or added
• The contents of the product backlog are prioritized according to a variety
of factors,
• including product value, complexity (of the product or user needs), dependencies
(such as one functionality relying on another dictating their order of
development), finances (for example, cost of development, or potential revenue
generation), market fit and likely performance, project risk, and even corporate
values
1
 Scrum artifacts – Sprint backlog

• The Sprint Backlog is a list of tasks the team must complete to deliver an increment
of functional software at the end of each Sprint. In other words, team members agree
on which
• A sprint backlog is a list of tasks and achievable for the current sprint, just one period
of activity in the project.
• The difference between Product backlog and sprint backlog is The product backlog
gives an overview of the entire product. A sprint backlog gives a closer focus on the
work of the product during a specific time period
User stories in scrum
• A user story is the smallest unit of work in an agile framework.
It’s an end goal expressed from the software user’s perspective.
• A user story is an informal, general explanation of a software
feature written from the perspective of the end user or customer
• User stories are a few sentences in simple language that outline
the desired outcome. They don't go into detail
• a user story is a brief, plain-language explanation of a feature or
functionality written from a user’s point of view
How to create user story
• As a [description of user], I want [functionality] so that
[benefit].

• description of user --- Who are we building this for?

• Functionality Here we’re describing their intent
• benefit What’s the overall benefit they’re trying to achieve?
 Examples of User stories
• As a user, I want to login, so I can access the application.
• As a user, I want to login with my Facebook account, so that I
• can login faster
• As a System Admin I want to be able to add users accounts .
• As a Teller I want to be able to find clients by last name, so that I can
find their profile faster
• As a user, I want to reserve a hotel room.
• As a user, I want to cancel a reservation.
• As a vacation traveler, I want to see photos of the hotels.
Example

Epic is a large body of work that can be broken down into a number of smaller stories,
 W h o creates user stories in scrum ?

•In many agile organizations, the product owner takes primary

responsibility for writing user stories and organizing them on the product
backlog.
•In reality, this is a shared responsibility among the entire cross- functional
product team.
8

Scrum artifacts – Burndown Chart

• The Sprint Burndown Chart is an illustration of the work

remaining in a Sprint. It helps both the team and the Scrum
Master as it shows progress on a day-to-day basis and can
predict whether the Sprint goal will be achieved on schedule
Scrum Majors
roles
1) Scrum Master

2) Product Owner

3) Scrum Team
1. Scrum master
• A Scrum Master is responsible for ensuring a Scrum team is
operating as effectively as possible with Scrum values. This
means they keep the team on track, plan and lead meetings,
and work out any obstacles the team might face.

• Scrum Masters might also work in a larger role within an

organization to help it incorporate Scrum concepts into their
work
2. Product owner
• Represents the voice of the customer and has the authority to
make decisions about the product.
• Product Owner has the vision of what to build and conveys that to
the team.
• Product Owner focuses on business and market requirements,
prioritizing the work that needs to be done, managing the backlog,
providing guidance on which features to ship next, and interacting
with the team and other stakeholders to make sure everyone
understands the items on the product backlog.
 3- Scrum Team

• is a cross-functional and self-organizing group of people that is

responsible for the product implementation. It should consist of up to
seven team members, in order to stay flexible and productive
• Cross-functional (e.g., includes members with testing skills, and
others not traditionally called developers: business analysts,
designers, domain experts, etc.)

• Plans one Sprint at a time with the Product Owner.

• The Development Team(scrum team) includes all the expertise
necessary to deliver the potentially shippable product each Sprint