Scribd
Upload
38 views15 pages

Unit-2-Lecture 1-2

The document discusses the Scrum framework and its key aspects like roles, artifacts, sprints and events. It describes the Scrum team, product owner, and scrum master roles. It also explains the product backlog, sprint backlog, burndown chart, increment and retrospectives which are important Scrum artifacts and events.

Uploaded by

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

Unit-2-Lecture 1-2

The document discusses the Scrum framework and its key aspects like roles, artifacts, sprints and events. It describes the Scrum team, product owner, and scrum master roles. It also explains the product backlog, sprint backlog, burndown chart, increment and retrospectives which are important Scrum artifacts and events.

Uploaded by

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

Unit 2

Lecture 1 Agile Development Methodology, Devops


Scrum framework, Scrum Artifacts:

Prepared By Ms Rupali Dave


Assistant Professor CSE
Foundations of Scrum
• The three pillars of Scrum methodology are Transparency, Inspection,
and Adaptation.
• Transparency:
• All aspects of the process or project must be visible to those
responsible for the outcome.
• Use Information radiators, through which key information like product
backlog, sprint backlog, impediments, risks, and project progress are
made transparent to all the stakeholders.
Foundations of Scrum
• Inspection: • The team regularly inspects their performance and
progress towards the project goal. They constantly look for
problematic areas and deviations from the plan.
• Adaptation: • Based on the observations made during an inspection,
essential changes are made to the process to avoid problem relapse
and improve the project delivery position.
Scrum Team
• Scrum Team A Scrum Team is a group of individuals working together
to deliver the requested and committed product increments.
• To work effectively it is important for a Scrum Team that everyone
within the team follows a common goal. Within the Scrum Framework
all work delivered to the customer is done by dedicated Scrum Teams.
• A Scrum Team is a collection of individuals working together to
deliver the requested and committed product increments.
Scrum Teams always have the following
characteristics:
• Team members share the same norms and rules
• The Scrum team is held responsible for the delivery
• The Scrum Team is empowered
• It is working as autonomous as it is possible
• The Scrum Team is self-organizing
• The skills within the Scrum team are balanced
• A Scrum Team is small and has no sub-teams
• The people within the Scrum Team work full time in the team
Roles of Scrum Team,
• In Scrum, there are three roles: Product Owner, Development Team, and Scrum Master. Together

these are known as the Scrum Team.

• Product Owner: The Product Owner is responsible for maintaining this list and revising priorities for

items as the project progresses and the business environment changes. The Product Owner is

responsible for the success of the product. He or she defines the features and release schedule and

is responsible for determining the business value of the various features. The Product Owner

constantly refines and reprioritizes the Product Backlog.

• Scrum Master: The ScrumMaster manages the Scrum process, ensuring that the Scrum practices

are properly executed and that Scrum values are understood by the team members. He or she

ensures that the team is fully productive by eliminating impediments and shielding them from

outside interference.
Sprints
• Agile projects are broken down into sprints or iterations.
• A sprint is a short, time-boxed period when a scrum team works to
complete a set amount of work.
• Time duration of 3 to 4 week.

Definition of Ready
• Definition of ready is a working agreement between the team and
product owner on what readiness means. It is an input criterion to
plan a story in a sprint.
Scrum Artifacts:

• Product Backlog: Requirements are documented as items in the Product Backlog. This is one of
the most important artifacts in a scrum project. It is a prioritized list of all desired work or
features for the project.

• Sprit Backlog: The Scrum team and Scrum Master hold a Sprint Planning meeting at the start of
each sprint. At this meeting, the product owner presents the features from the Product Backlog
that are most desired for the upcoming sprint, describing them so that the team can grasp what
is expected. The product owner and team agree on a goal for the sprint. This is essentially a
vision statement focused on the work for the next two to four weeks. The team then
determines how to accomplish the sprint goal and breaks the features down into the tasks
required. This list of tasks becomes the Sprint Backlog.
• Sprint Burndown chart: As items from the Product Backlog are selected for
completion during the sprint planning meeting, they become part of a Sprint
Backlog. As mentioned previously, the Sprint Backlog contains specific tasks
associated with the features from the Product Backlog. During the sprint, the
status of the work items in the Sprint Backlog is updated daily. The updated
status makes it possible to generate a Sprint Burndown chart. This chart is a
graphical display of the amount of work remaining in the project. It is also
common for it to include an "ideal" line that indicates a smooth progression of
the work from start to finish of the sprint. The ideal line indicates how work
would progress if even proportions of it are completed each day of the sprint.

• Impediment List: When there are impediments or blocks to progress, the scrum
master might maintain an Impediments List as an additional scrum artifact.
An Impediment is anything that keeps the Team from getting work Done and that
slows Velocity.
• Product Increment: The Product Increment is the sum of all
the Product Backlog items completed during a Sprint and the value of
the increments of all previous Sprints. At the end of a Sprint, the
new Increment must be “Done,” which means it must be in useable
condition and meet the Scrum Team's definition of “Done”
• Product Increment is the combination of all the completed list of
Product Backlog items during the sprint. Product Increment keeps
getting incremented in the subsequent sprints.
• Sprint Retrospective: The Scrum Team inspects how the last Sprint went with regards
to individuals, interactions, processes, tools, and their Definition of Done. ... They may
even be added to the Sprint Backlog for the next Sprint. The Sprint
Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a
one-month Sprint.
• The sprint retrospective is usually the last thing done in a sprint. Many teams will do it
immediately after the sprint review. The entire team, including both the ScrumMaster
and the product owner should participate. You can schedule a scrum retrospective for
up to an hour, which is usually quite sufficient.

• The Sprint Retrospective concludes the Sprint. It is timeboxed to a maximum of three


hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
• During the Sprint Retrospective, the team discusses:
• What went well in the Sprint
• What could be improved
• What will we commit to improve in the next Sprint
Sprint Review:

• The purpose of the Sprint Review is to inspect the Product


Increment delivered in the Sprint and to adapt the Product
Backlog (if needed). During the Sprint Review a demonstration
of the Product Increment and Product Backlog is given to the
stakeholders.
• In Scrum, each sprint is required to deliver a potentially
shippable product increment. This means that at the end of
each sprint, the team has produced a coded, tested and usable
piece of software. During this meeting, the Scrum team shows
what they accomplished during the sprint

You might also like