Scribd
Upload
76 views20 pages

Professional Practices: "Anatomy of A Software House"

The document discusses the Scrum framework for agile software development. It describes the key roles in Scrum as the Product Owner, Scrum Master, and Development Team. It outlines the Scrum ceremonies of sprint planning, daily stand-ups, sprint reviews, and retrospectives. It also mentions the main artifacts in Scrum like the product backlog, sprint backlog, and burn down charts.

Uploaded by

raahim majid
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
76 views20 pages

Professional Practices: "Anatomy of A Software House"

The document discusses the Scrum framework for agile software development. It describes the key roles in Scrum as the Product Owner, Scrum Master, and Development Team. It outlines the Scrum ceremonies of sprint planning, daily stand-ups, sprint reviews, and retrospectives. It also mentions the main artifacts in Scrum like the product backlog, sprint backlog, and burn down charts.

Uploaded by

raahim majid
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/ 20

Professional Practices

“ANATOMY OF A SOFTWARE HOUSE”


Contents

 SCRUM
 Anatomy
 • Software house
 • Anatomy of a typical software house
 • Case study // any scenario
SCRUM
 Scrum is a tool, a framework that can be used to build complex products.
 It is "a flexible product development strategy
SCRUM Roles

 In contrast to classical project management methods, Scrum doesn’t have and


doesn’t need a product manager, a task manager or a team leader.
 A scrum team has a slightly different composition than a traditional waterfall
project, with three specific roles:
  Product Owner,
  Scrum Master, and
  Development Team.
Roles
 The Product Owner is responsible for the vision of the product, the gathering and the prioritization of the
requirements, control over the budget.

 The Scrum Master takes care of the problems, takes responsibility that the rules of Scrum are appropriately
followed and he coaches the team too.

 A Scrum Master is not a project manager. Project managers don't really have a place in the scrum methodology.

 The Scrum Master does not interfere into the decisions of the team regarding specifically the development, but
rather is there for the team as an advisor. He only interferes actively when anyone within the team or any other
participant of a project (Stakeholder) does not obey the rules of Scrum.

 The team of Scrum is a self-organized group of people, responsible for the creation and the quality of the product.
And because scrum teams are cross-functional, "the development team" includes testers, designers, and ops
engineers in addition to developers
Scrum Process
Sprints
Scrum Framework
Roles

•Product owner
•ScrumMaster
•Team Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts

•Product backlog
•Sprint backlog
•Burndown charts
Scrum Framework
Roles

•Product owner
•ScrumMaster
•Team Ceremonies

•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts

•Product backlog
•Sprint backlog
•Burndown charts
Scrum Structure
Scrum Framework
Roles

•Product owner
•ScrumMaster
•Team
Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts

•Product backlog
•Sprint backlog
•Burndown charts
Scrum Board

Backlog Development Test Ready


The Daily Scrum
• Parameters
• Daily
• 15-minutes
• Stand-up
• Not for problem solving
• Whole world is invited
• Helps avoid other unnecessary meetings
Everyone Answers 3 Questions

1
What did you do yesterday?

2
What will you do today?

3
Is anything in your way?
Sprint Review
Preparation needed
Show complete features
Accept or reject results

1-2 hours
per sprint/week
The Sprint Review
• Team presents what it accomplished during the sprint
• Typically takes the form of a demo of new features or
underlying architecture
• Informal
• 2-hour prep time rule
• No slides
• Whole team participates
• Invite the world
Scrum Framework
Roles

•Product owner
•ScrumMaster
•Team Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts

•Product backlog
•Sprint backlog
•Burndown charts
Artifacts

Product Vision Product Backlog Release Plan

Sprint Backlog Sprint Burndown Impediment List


Product Backlog

You might also like