Scrum Framework 1

Scrum Framework
Natalija Basekikj
209028
Agenda
• What is Scrum
• Scrum Framework
• Scrum Events
• Scrum Artifacts
• Roles in Scrum
• Scrum DoR/DoD
• Scrum Values
• Scrum Process and Workflow example
• Examples / Discussion
What is Scrum
Sprint Planning
• Goal: Collaboratively decide what US will be included in the
next sprint
• Up to 2 hours per week of the sprint
• Participants: Development Team, Scrum Master, PO
• DoR must be met
• Prioritization, Estimation, Sub-tasks
Daily – stand up
• 15 minutes maximum
• Participants: Development team, Scrum Master, (Product
Owner)
• What have I done since last time that is to do with working
towards our sprint goal?
• What am I planning to do until next time that is to do with
working towards our sprint goal?
• What impediments do I have?
Sprint Review
• Goal: Get feedback on the product / generate ideas for
product improvement
• 1 hour per sprint week
• Participants: Product Owner, Development team, Scrum
Master, Stakeholders
• Agenda
• DoD should be met
• Overview of planned and done
• Demonstration
• Feedback (PO, Stakeholders)
• Progress report and outlook (PO)
Sprint Retrospective
• Goal: Decide on improvements in process and collaboration
for next sprint
• 1 hour per week (example: 2 hours for bi-weekly sprint)
• Participants: Development Team, Scrum Master, (Product
Owner)
• Agenda (Retro Method, Notes Discussion, Voting, Action
Items)
• Set the stage
• Gather data
• Generate insights
• Decide what to do
• Close the retrospective
Scrum Artifacts
• Product Backlog - is a list of the new features, changes to
existing features, bug fixes, infrastructure changes or other
activities that a team may deliver in order to achieve a specific
outcome.
• Sprint Backlog - is a list of tasks identified by the Scrum team
to be completed during the Scrum sprint. During
the sprint planning meeting, the team selects some number of
product backlog items, usually in the form of user stories, and
identifies the tasks necessary to complete each user story.
• Increment - is the sum of all the Product Backlog items
completed during a Sprint and the value of the increments of
all previous Sprints.
Roles in Scrum
• Product Owner – single point of responsibility for product
• Owns and manages the Product Backlog
• Ensures highest value work is done
• Is a single person
• Their decision must be respected
• Scrum Master – ensures Scrum is understood
• Facilitates events as needed
• Serves the Product Owner, the Dev Team and the Organization
• Does not work on the product itself
• Development Team – create each product increment
• Gets work only from PO
• Self organizing – selects the work and chooses how to do it
• Cross – functional – has all skills needed to deliver an increment
DoR / DoD
• DoR – The DoR enables a team to define certain conditions
before an issue (e.g. a user story) in the product backlog can
change from the status "new" to the status "open". The focus
of the DoR is on the quality and completeness of an issue.
• DoD – is a shared understanding within the Scrum Team on
what it takes to make the Product Increment releasable.
DoR examples
• Detailed enough so that the team can estimate the complexity, look for alternatives,
plan and identify risks and develop a common understanding with the specialist
department.
• A user story contains a clear statement about the business added value that allows
the PDO to prioritize.
• The description of a user story is in the format “As a [role] I want [a solution] to
achieve [goal]. (WHO - WHAT - WHY).
• The user story is functionally sufficient and detailed enough to be able to prioritize.
• The user story has sufficient acceptance criteria that are accepted by the team.
• The GUI guidelines from the ISAR GUI style guide and the Premium repair guide style
guide are adhered to when defining the user story. Note: The responsibility for
adhering to the Stylequides guidelines rests with the dev team. Exceptions must be
agreed with the PO.
• The user story can be implemented and tested within a sprint (e.g. in two weeks).
• The complexity of the user story is estimated (story point attribute) and is based on
the agreed sizes.
• The user story is assigned to an EPIC,
• The following fields in JIRA are filled:Summary; Reporter; Acceptance criteria; Epic
link; Component (opt.); Fixed version (opt.)
DoD examples
• A user story is implemented when the following criteria are fully met:
• All acceptance criteria for a user story are met

• Agreed code guidelines observed
• no blockers and critical violations
• Test coverage of the program code with unit tests is at least 50%
• All general specifications (naming of user controls and implementation of
internationalization) from the ISAR GUI style guide, chap. 2. were complied with.
• Code review carried out and architecture conformity ensured
• User story was automatically deployed to a development environment as part of
the continuous integration process
• Test cases are up to date and carried out successfully
• Automated test cases (unit test) were created, which ran successfully on the build
server
• There are no errors preventing GO-Live (Critical and High)
• Relevant documentation (FITK, AWHB, SSK / SSP, editor rights matrix) is up to date.
Note: The documentation language is German.
• Release notes and necessary steps for commissioning are documented
• Non-functional requirements are met
Scrum Values
• Because we value:
• We will…
Discussion
• It is time for Sprint Review.
• One feature remains in the Sprint Backlog. It works as
expected with no known defects. It has not been fully
documented, which is part of the teams DoD. The team
member assures the team he will finish the documentation
right after the Sprint Review Meeting.
• Does this feature get shown at the Sprint Review?

• Does this feature get Closed?
Discussion
• A higher manager regularly stops by the Daily Scrum meetings
and uses that time to ‘inspire the troops’ by telling them how
important it is they complete all work forecast for the sprint.
• What is your advice to this team? What is your advise to this

manager?
Questions?

Scrum Framework 1

Uploaded by

Copyright:

Available Formats

Scrum Framework 1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Scrum Framework 1

Uploaded by

Copyright:

Available Formats

Scrum Framework

• All acceptance criteria for a user story are met

• Does this feature get shown at the Sprint Review?

• What is your advice to this team? What is your advise to this

You might also like