Scrum is an agile framework that many large companies use for software development. It involves 3 roles - Product Owner, Development Team, and Scrum Master. The process involves sprint planning, daily stand-ups, and sprint reviews. Key artifacts include the product backlog, sprint backlog, and task board. The goal is rapid delivery of working software through short cycles of work called sprints, using an inspect and adapt approach.
This is a template for a slide deck I use to guide/facilitate my Scrum Teams through Sprint Review (Demo and Retrospective) and Sprint Planning sessions.
This is a template for a slide deck I use to guide/facilitate my Scrum Teams through Sprint Review (Demo and Retrospective) and Sprint Planning sessions.
Software development is quite a complex process because of ever changing design specs, non tracking of efforts by team member's and work load planning problems. SCRUM is an agile software development methodology to overcome above issues and others discussed in slides....
Introduction to JIRA & Agile Project ManagementDan Chuparkoff
Join me for a brief introduction to JIRA & Agile Project Management. I'll talk about basic Agile concepts. I'll show you basic JIRA planning and working with Scrum and Kanban. And I'll show you the most important reports to master so you can build great software just like Atlassian.
Scrum is the most popular Agile Framework; during this presentation the attendees will understand the value, and an overview of the powerful scrum framework: its roles, its artifacts and its ceremonies
Software development is quite a complex process because of ever changing design specs, non tracking of efforts by team member's and work load planning problems. SCRUM is an agile software development methodology to overcome above issues and others discussed in slides....
Introduction to JIRA & Agile Project ManagementDan Chuparkoff
Join me for a brief introduction to JIRA & Agile Project Management. I'll talk about basic Agile concepts. I'll show you basic JIRA planning and working with Scrum and Kanban. And I'll show you the most important reports to master so you can build great software just like Atlassian.
Scrum is the most popular Agile Framework; during this presentation the attendees will understand the value, and an overview of the powerful scrum framework: its roles, its artifacts and its ceremonies
The slide explains the basics of the Scrum Framework one of the most popular Agile implementations for beginners. You can learn fundamental knowledge about it.
Traditional software development models (such as Waterfall) are based upon a
defined methodology which attempts to define requirements up front, logically
break down the work estimate plan then begin development while trying to
SCRUM – How It Differs
work, estimate, plan, development, limit/control change which will threaten the plan. These are based upon Defined
Process Model theory which was adopted from manufacturing and applied to
software development.
Introduction to Scrum development process. Main concepts. The process. Examples. Issues
Slides for course Software engineering seminar @ Afeka College Of Engineering
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
the presentation gives brief description about a methodology of software engineering which is most using software engineering process in today's IT world and helps student to know how a software company runs and build software product using various software engineering methodologies.
Detail Information about Agile Process Frameworks such as SCRUM and CMMI along with agile manifesto. Comparison between scrum and capability maturity model integration
Scrum is a Agile framework which allows teams to work together in order to develop a product.
Building complex products for customers is an naturally difficult task.
In the Scrum methodology a sprint is the basic unit of development.
2. Who uses it?
• Afisha
• Adobe - use it in all of their developments, now, and began with Adobe
Lifecycle, Adobe Soundbooth and Adobe Audition
• Adwords in Google
• Epam systems widely use Scrum
• Amazon is heavily using Scrum in almost every layer of their business
• Microsoft widely use Scrum for software development
3. Overview
• Average team size 7 +/-2
• 3 roles
• Product owner
• The team
• Scrum Master
• 3 ceremonies
• Sprint planning
• Daily meeting
• Sprint review
5. Some history
• Was defined in 1986 by american professors Hirotaka Takeuchi and Ikujiro
Nanaka in their paper “The new software development game”
• Based on case studies from manufacturing firms in the automotive,
photocopier and printer industries (Fuji-Xerox, Honda,Toyota, Canon etc.)
• First Documented in 1993 by Jeff Sutherland, John Scumniotales and Jeff
McKenna. Sutherland formalized a Scrum process and influened to Kent
Beck a XP programming founder
• According to the 7th Annual State of Agile Development Survey, scrum or
variants of scrum are still the most popular agile methodologies used. Out of
the 4,048 software professionals that responded, 72% are practicing scrum
or some kind of hybrid
9. ... and voice of the business
He takes the stories that have the most business value
10. In a nutshell
• Holds the vision for the product
• Represents the interests of the business
• Represents the customers
• Owns the product backlog
• Creates acceptance criteria for the backlog items
• Prioritizes tasks
12. Not the team boss
Priority - high-performing, self-organized team
13. What does he do?
• Removes impediments to the ability of team to deliver
sprint goals
• Insures that scrum process is used as intended
• Facilitates changes
14. “One for one and one
for all”
“One for one and one
for all”
15. In a nutshell
• Complete user stories to incrementally increase the
value of the product
• Self-organizes to get all of the necessary work done
• Creates the estimates
• Owns the “how to do the work” decisions
• Avoid “not my job” thinking
17. The product backlog
Cumulative list of desired deliverables for the product
(features in user stories, bugs, documentation changes)
18. Product backlog item
• An estimate as to how much work the story requires to
implement
• Acceptance criteria that will help us know when it has
been implemented correctly
Contains:
19. Sprint backlog
• Finite life-span - length of current sprint
• Has all the stories that the team has commited to
accomplish in this sprint and their associated tasks
• Stories -- unit of value. Somethings that team delivers
• Tasks -- unit of work. Somethings that person delivers.
24. Definition of done
• Scrum teams create their own definition of the word
done for a user story
• I.e. code witten, reviewed, unit and regression test passing,
doc written, tester sign-off
• Print out their definition of done as a checklist and post it
next to their task board.
• When the team thinks a story is done, they gather
together and review each item.Then they declare the
story as done.
26. • Sprint planning
• Daily standup meeting
• Story time
• Sprint review
• Retrospective
27. Sprint planning
• 1 part
• What will we do?
• Commit to a set of deliverables for the sprint
• What will we do?
• Product owner presents the stories
• Team members discuss it and review acceptance criteria
• 2 part
• How will we do?