Topic: Agile/Scrum OverviewFocus should be on scrumI have uploaded my attempt to this assignment just to give guidance on what i am expectingThis is work assignmentThis is to present to a team/project that is new to agileAGILE/SCRUM
OVERVIEW
SCRUM FRAMEWORK
AGENDA

What is Agile/Scrum

Scrum Pillars

Scrum Roles

Scrum Values

Scrum Ceremonies/Events

Scrum Artifacts

Sprint report, Burndown Chart, Velocity
WHAT IS AGILE/SCRUM



Agile is a software development methodology. It deals with a set of
principles and values
Below are a few frameworks under agile

Scrum

Kanban

Safe
Scrum is the most popular framework. It aims to develop, deliver and
sustain complex products through collaboration, accountability and
iterative progress
SCRUM PILLARS

There are 3 Scrum Pillars
Transparency
Inspection
Adaptation
SCRUM ROLES

PRODUCT OWNER
The product owner is the one who represents the stakeholders and the voice of the
customer. They hold the vision of the product. His/her duties include:

Clearly express product backlog items (PBI)

Ordering the items in the backlog to best achieve goals and missions

Ensuring that the PBI is visible, transparent and clear to all and show what the
scrum team will work on next.

Ensuring that the development team understands items in the product backlog

DEVELOPMENT TEAM
The development team is a group of professionals such as developers, designers,
QA who deliver the product and create increment (the working product
functionality that is presented to the stakeholders at the end of the sprint and could
potentially be given to the customer)
SCRUM ROLES CONT’D

SCRUM MASTER
The scrum master is facilitator of the scrum ceremonies and a servant
leader that ensures the understanding and execution of scrum
ceremonies is followed
Ensures the team stays on track by identifying and blocking distractions
that may hinder the development process
Ensures all scrum roles understand scrum’s core aim
Scrum Ceremonies and Purpose
#
Agile Ceremony
Duration
Cadence
Attendees
Purpose
1
Sprint Planning
1 hour
Day #1
Required:
Team Lead
Scrum Master
Team Members
OIT Leads
1.
2.
3.
4.
5.
2 hours (Team 1)
Review and select User Stories/Tasks from the product backlog for the new sprint;
Team collectively determines story points
Team members subscribe to work/tasks
Identify any risks on planned stories
Team agrees/confirms to DOD
2
Daily Scrum
15 minutes each
Daily
Required:
Team Lead
Scrum Master Team
Members
Optional
OIT Leads
Daily stand-up where team members meet to bring everyone up to date on the information that is vital for coordination: each team
members briefly describes any “completed” contributions and any obstacles that stand in their way. The format of this meeting will be
centered around:
1.
Any changes since last scrum?
2.
What will you be doing today?
3.
Any Impediments?
3
Backlog Grooming, I
1 hour
2 hours
(Team 1)
Day #5
Required:
Team Lead
Scrum Master
Team Members
OIT Leads
1.
2.
3.
4
Backlog Grooming II
1 hours
2 hours
(Team 1)
Day #6
Required:
Team Lead
Scrum Master
Team Members
OIT Leads
In Prep for next sprint, refinement of the backlog will need to take place by:
1.
Breaking down large user stories to smaller stories/tasks
2.
Team discuses user stories with OIT leads and answering any related questions to smooth out any ambiguity
3.
Ensure upcoming user stories meet the teams “definition of ready” by adding key contextual information and acceptance
criteria
5
Sprint Review
1 hour
2 hours
(Team 1)
Day #10
Required:
Team Lead
Scrum Master
Team Members
OIT Leads
Team reviews/Demo what was accomplish in the sprint and OIT Lead provides final acceptance of work
6
Sprint Retrospective
30 minutes
Day #10
Required:
Team Lead
Scrum Master
Team Members
Team discusses how the sprint went and plan for improvements in the next sprint.
Using IdeaBoardz, the team will discuss the following:
1.
Identify what went well?
2.
What needs improvement?
3.
Create action items
4.
Action Items are also followed-up on which were captured in the previous Retrospective.
1 hour
(Team 1)
Identify stories that could potentially be worked on in upcoming sprints
Review/add items in the backlog to ensure the backlog contains the appropriate descriptions and acceptance criteria
Prioritize stories where the items at the top of the backlog are ready to begin work on
Scrum Artifacts

Artifacts are the tools need to deliver and complete the work.
Below are the primary artifacts in Scrum

Product Backlog – Managed by the PO, the product backlog is
where all the requirements needed for a viable product are listed in
order of priority

Sprint Backlog – It list the tasks and requirements that the team need
to accomplish in a sprint

Product Increment – It is the result of all the PBI accomplish during a
sprint. It is the working product functionality that is presented to the
stakeholders at the end of the sprint and it is considered a step
towards the end goal
SPRINT REPORT, BURNDOWN CHART,
VELOCITY

Burndown Chart – It is graph that illustrates the total work remaining.
It helps us track the progress of an ongoing sprint and predicts if we
will be meeting our sprint goals

Velocity _ It is the average number of work a team can complete at
the end of each sprint.

Sprint Report _ It illustrates the work completed or moved back to
the product backlog in each sprint. It helps us determine if the team
is over committing
Scrum Values

There are 5 Scrum Values

Openness

Focus

Commitment

Courage

Respect

Purchase answer to see full
attachment




Why Choose Us

  • 100% non-plagiarized Papers
  • 24/7 /365 Service Available
  • Affordable Prices
  • Any Paper, Urgency, and Subject
  • Will complete your papers in 6 hours
  • On-time Delivery
  • Money-back and Privacy guarantees
  • Unlimited Amendments upon request
  • Satisfaction guarantee

How it Works

  • Click on the “Place Order” tab at the top menu or “Order Now” icon at the bottom and a new page will appear with an order form to be filled.
  • Fill in your paper’s requirements in the "PAPER DETAILS" section.
  • Fill in your paper’s academic level, deadline, and the required number of pages from the drop-down menus.
  • Click “CREATE ACCOUNT & SIGN IN” to enter your registration details and get an account with us for record-keeping and then, click on “PROCEED TO CHECKOUT” at the bottom of the page.
  • From there, the payment sections will show, follow the guided payment process and your order will be available for our writing team to work on it.