What Is Scrum?
•
5 likes•1,996 views
The document provides an overview of Scrum, including a definition, brief history, and description. Scrum is defined as a framework for developing complex products using empirical process control theory and iterative, incremental approaches. It originated from lean manufacturing principles and was popularized in the 1980s. Scrum uses Sprint Planning, Daily Scrums, Sprint Reviews and Retrospectives with roles of Product Owner, Scrum Master and Team.
Report
Share
Report
Share
Download to read offline
Recommended
Introduction To Agile Estimating and Planning
My presentation on Agile Estimating and Planning to PMI, Queensland (Australia) Chapter, on 17th June 2009.
Introduction into Scrum
A Reusable Scrum Presentation. Introduce Scrum to your team, ScrumMaster and Product Owner. Created by mountaingoatsoftware.com
Introduction to Agile scrum
The sole purpose of this presentation was to introduce Agile Scrum Methodology into our company. We were following sprints and agile methodology, but never planned it properly before this.
A few months back, I recalled my days of working with Limewire and having few scrum masters in DigiMantra Labs. So we gave a little introduction and after that most of our teams are following this method. We now have 2 qualified Scrum Masters and counting.
Scrum for Beginners
Scrum is a framework for project management developed by Ken Schwaber and Jeff Sutherland. It is lightweight, simple, and difficult to master. Scrum uses self-organizing cross-functional teams, sprints, daily stand-ups, and artifacts like product backlogs and sprint backlogs. The goals are transparency, inspection, and adaptation. Scrum aims to deliver working software frequently through short development cycles and continuous improvement.
Management fundamentals scrum 101
What is Scrum? How to implement Scrum?
- This presentation describes the basic elements of the Scrum Framework.
- My goal is to provide an organized view that will help a novice understand and implement the Scrum foundation quickly.
Quick intro to scrum agile
The document discusses Agile and Scrum frameworks for software development. It defines key aspects of Scrum including roles like Product Owner and Scrum Master, ceremonies like sprint planning and daily standups, and artifacts like product and sprint backlogs. Scrum was designed to address uncertainties in specifications and changing requirements by having self-organizing cross-functional teams work in short sprints to deliver working software.
Scrumban – lean software development
The document provides information about Naveen Kumar Singh, an agile coach and consultant with over 17 years of experience. It lists his certifications and contact details. It then discusses agile concepts like Scrum roles, ceremonies, and artifacts. The rest of the document discusses Kanban principles like visualize your work, limit work in progress, manage flow, test as soon as done, and deal with bottlenecks. It provides examples of using Kanban with Scrum and compares Kanban and Scrum approaches.
Introduction to Scrum - Agile Methods
Scrum is an agile framework for managing product development that emphasizes self-organizing cross-functional teams, sprints, daily stand-ups, and adaptive planning. It consists of roles like the product owner and Scrum master, artifacts like the product backlog and sprint backlog, and ceremonies like sprint planning and reviews. Scrum originated in the 1990s and aims to rapidly deliver working software through short development cycles and continuous improvement.
Recommended
Introduction To Agile Estimating and Planning
My presentation on Agile Estimating and Planning to PMI, Queensland (Australia) Chapter, on 17th June 2009.
Introduction into Scrum
A Reusable Scrum Presentation. Introduce Scrum to your team, ScrumMaster and Product Owner. Created by mountaingoatsoftware.com
Introduction to Agile scrum
The sole purpose of this presentation was to introduce Agile Scrum Methodology into our company. We were following sprints and agile methodology, but never planned it properly before this.
A few months back, I recalled my days of working with Limewire and having few scrum masters in DigiMantra Labs. So we gave a little introduction and after that most of our teams are following this method. We now have 2 qualified Scrum Masters and counting.
Scrum for Beginners
Scrum is a framework for project management developed by Ken Schwaber and Jeff Sutherland. It is lightweight, simple, and difficult to master. Scrum uses self-organizing cross-functional teams, sprints, daily stand-ups, and artifacts like product backlogs and sprint backlogs. The goals are transparency, inspection, and adaptation. Scrum aims to deliver working software frequently through short development cycles and continuous improvement.
Management fundamentals scrum 101
What is Scrum? How to implement Scrum?
- This presentation describes the basic elements of the Scrum Framework.
- My goal is to provide an organized view that will help a novice understand and implement the Scrum foundation quickly.
Quick intro to scrum agile
The document discusses Agile and Scrum frameworks for software development. It defines key aspects of Scrum including roles like Product Owner and Scrum Master, ceremonies like sprint planning and daily standups, and artifacts like product and sprint backlogs. Scrum was designed to address uncertainties in specifications and changing requirements by having self-organizing cross-functional teams work in short sprints to deliver working software.
Scrumban – lean software development
The document provides information about Naveen Kumar Singh, an agile coach and consultant with over 17 years of experience. It lists his certifications and contact details. It then discusses agile concepts like Scrum roles, ceremonies, and artifacts. The rest of the document discusses Kanban principles like visualize your work, limit work in progress, manage flow, test as soon as done, and deal with bottlenecks. It provides examples of using Kanban with Scrum and compares Kanban and Scrum approaches.
Introduction to Scrum - Agile Methods
Scrum is an agile framework for managing product development that emphasizes self-organizing cross-functional teams, sprints, daily stand-ups, and adaptive planning. It consists of roles like the product owner and Scrum master, artifacts like the product backlog and sprint backlog, and ceremonies like sprint planning and reviews. Scrum originated in the 1990s and aims to rapidly deliver working software through short development cycles and continuous improvement.
Scrumban
Scrum is an iterative agile software development method using sprints of 2-4 weeks to deliver working software. Kanban uses a pull-based scheduling system to determine production priorities and avoid overloading developers. Scrumban combines Scrum and Kanban by using Scrum's roles and meetings to maintain agility while adopting Kanban's continuous process improvement. It is suited for maintenance projects, help desk work, and projects with unpredictable requirements changes.
Scrumban - applying agile and lean practices for daily uncertainty by Vidas V...
In this presentation I have talked about scrumban - a mix of routines and techniques for daily use in dynamic environment. Like in startups, product manufacture, support or similar cases.
Introduction to Agile & Scrum
This document provides an overview of an introduction workshop on Agile and Scrum. The workshop covers topics such as the history and principles of Agile, an introduction to Scrum frameworks and roles, and exercises on writing user stories and estimating story points. Participants will learn about Agile and Scrum methodologies, how to write and evaluate user stories, and techniques for relative estimation like planning poker. The goal is for participants to understand key Agile and Scrum concepts and practices and be able to apply them.
Agile Scrum Training, Day 1 (1/2)
Training materials for Agile Scrum. Starts with an overview of Agile and Lean. Followed with the Agile Scrum key concepts like Product Owner, Scrum Master, Scrum Team and Product Backlog. Theory is complemented with learnings and best practices from real life software development.
Scrumban
Scrumban Demystified. Talk from Agile New England.
A few of the Scrumban Evolutions from Mamamoth bank from the upcoming book on Scrumban.
More excerpts can be found at facebook.com/scrumban
Learn more at scrumban.io
Do you have a case study of applying the Kanban Method in a Scrum context. We want to learn more from your experiments and results. Contact us at info@codegenesys.com
Using Scrum to Build a Jet Fighter? Yes!
How can Scrum be used to deliver complex integrated products, like a fighter aircraft?
It's been done, and done successfully.
How do you keep multiple teams aligned on the same delivery using Scrum?
This is a brief Infographic describing a quote from Jeff Sutherland published in HBR, May-June 2018 "Agile at Scale"
Link: https://hbr.org/2018/05/agile-at-scale
What is-agile henrik kniberg august 20 2013
This document discusses Agile project planning and estimation techniques. It notes that estimates are often wrong due to factors like changing requirements, irrelevant information, and anchoring biases. Instead of estimating time, Agile recommends estimating the relative size of features and measuring team velocity over iterations to forecast release plans and timelines. Estimates should be done by developers and re-estimated continuously throughout the project rather than relying on early estimates.
Agile Estimating and Planning Using Scrum
This presentation contracts the more traditional ways of planning and estimating projects with Agile/Scrum practices.
Scrum Introduction
This document provides an introduction to the Scrum framework for agile software development. It describes Scrum as an iterative, incremental framework that uses self-organizing cross-functional teams to deliver complex products. The key aspects of Scrum covered include the roles of product owner, Scrum master and development team, the Scrum events of sprint planning, daily stand-ups, sprint reviews and retrospectives, and the artifacts of product and sprint backlogs and burn-down charts. The document provides an overview of how Scrum is intended to provide transparency, inspection, and adaptation to optimize predictability and control of risk.
Lightning Talk: An Introduction To Scrum
Scrum is an agile development methodology that focuses on roles, backlogs, and time-boxed meetings. There are three core roles: the Scrum Master enforces practices and removes roadblocks, the Product Owner maintains the backlog and user stories, and the self-organizing Team delivers working software each sprint. Artifacts include the Product Backlog of prioritized user stories and the Sprint Backlog of selected stories. Sprints are 30-day cycles where selected stories are demonstrated as shippable at the end. Meetings include Planning, Daily Scrums, a Sprint Review, and Retrospective.
Scrum Basics
The document provides an overview of Scrum basics and components. It introduces Scrum as an Agile framework and discusses its core elements - events like sprints, planning and reviews; roles like product owner and scrum master; and artifacts like product backlog and sprint backlog. It also covers related concepts like capacity, velocity and how Scrum compares to Agile approaches. The document concludes by suggesting resources to learn more about Scrum and offers coaching for teams to understand how to apply Scrum.
Introduction to agile and scrum
1. The document provides an overview of practical scrum concepts including lean thinking, agile principles, scrum roles and ceremonies.
2. It discusses the roles of the product owner, scrum master and team in scrum and describes the four main scrum ceremonies: sprint planning, daily scrum, sprint review, and retrospective.
3. Key aspects of each ceremony are outlined such as their purpose, participants, and goals to continuously deliver working software and improve the process.
Modern Software Methodologies(Agile ,Scrum & Lean) + CASE STUDY(Google)
This document discusses modern software methodologies like Agile and Scrum. It provides an overview of Agile principles like valuing individuals, working software, customer collaboration and responding to change. Specific Agile frameworks like Scrum and Kanban are described, including Scrum processes like sprints, stand-up meetings and prioritizing a backlog. Google's software development methodology is also summarized, which focuses on tools like Percolator, Dremel and Pregel for incremental processing, analytics and graph processing. The document concludes with an overview of Google's 20% time rule for employees to work on self-directed projects.
Modern Professional Scrum using Flow and Kanban - Agile and Beyond Detroit 2019
Should you use Scrum or Kanban? You don’t have to choose: Scrum teams improve when they look at flows inside and outside their sprints from a Lean/Kanban perspective. In this session we will talk about Kanban-related myths prevalent in the Scrum world and identify common ground between them. We will look at ways to bring Kanban flow into your Scrum: the Kanban-based Sprint/product backlog, flow-based daily Scrum, visualizing aging work, and flow-based Sprint planning .We will describe ways to wrap Scrum with a Kanban flow system, and how DevOps fits into this picture.
You’ll leave with a better understanding of how Scrum, Kanban, and DevOps relate to each other and with ideas for experiments to try when back at work.
Scrum Gathering Shanghai - April 2010
This was my keynote speech at the the Scrum Gathering in Shanghai, 2010. it's about the use of Scrum with the XP technical practices.
Introduction To Agile And Scrum
The document introduces Agile and Scrum concepts. It discusses Scrum roles like ScrumMaster and Product Owner and the team. The Agile manifesto values individuals and interactions over processes and tools. Sprints occur over 24 hours and 2 weeks where a backlog of user stories is implemented in tasks. User stories follow a format of "As a <role> I want <goal> so that <benefit>". Metrics show Agile can increase productivity, quality, satisfaction while decreasing costs. Resources provided for learning more.
Introduction to Lean, Agile, Scrum, & XP
This document provides an introduction to Lean, Agile, Scrum, and XP. It defines Lean as focusing on identifying value and optimizing processes. Agile emphasizes responding quickly to change through principles like valuing individuals, working software, and customer collaboration. Scrum is a framework that uses short cycles, daily stand-ups, and product backlogs to organize complex work. XP includes practices like pair programming, test-driven development, and collective code ownership.
Scrumban - benefits of both the worlds
#Scrum is very popular these days but #kanban is suitable for better organizational level continuous improvement. We use #scrumban to get the benefits of both the worlds. Its a combination of good practices of scrum with kanban.
Scrum in an hour
Scrum is an agile framework for managing complex projects. It emphasizes transparency, inspection, and adaptation. Key aspects of Scrum include short sprints with fixed durations, daily stand-ups, sprint planning and reviews, and retrospectives. The product owner prioritizes features in the backlog and the cross-functional team works to complete them in sprints. Applying Scrum principles like frequent delivery, transparency, and process improvement can help manage uncertainty, deliver value faster, improve quality, and eliminate waste.
Scrum Master 101
This document provides an overview of the roles and responsibilities of a Scrum Master compared to a traditional Project Manager in a Waterfall methodology. It describes how a Scrum Master is primarily focused on facilitating Agile ceremonies like planning, daily standups, and retrospectives. Their key responsibilities include removing impediments for the team, coaching them in Agile practices, and helping to manage team dynamics. The document also provides examples of questions for clients and candidates to determine if a Scrum Master role and individual are a good fit.
What isscrum
Scrum is an agile framework for developing complex products using iterative incremental development. It is grounded in empirical process control theory and employs short development cycles called sprints to optimize predictability and control risk. Scrum uses four meetings - planning, daily scrum, sprint review, and retrospective - and three roles - product owner, scrum master, and team. The framework was developed in the 1990s based on lean principles and the rugby sport.
Why Scrum?
Why Scrum? Scrum is conceptually a very, very simple process framework. What is it about Scrum that is generating some much buzz in the software development community? Why are companies, both big and small, abandoning traditional approaches such as Water Fall and RUP, in favour of Scrum?
More Related Content
What's hot
Scrumban
Scrum is an iterative agile software development method using sprints of 2-4 weeks to deliver working software. Kanban uses a pull-based scheduling system to determine production priorities and avoid overloading developers. Scrumban combines Scrum and Kanban by using Scrum's roles and meetings to maintain agility while adopting Kanban's continuous process improvement. It is suited for maintenance projects, help desk work, and projects with unpredictable requirements changes.
Scrumban - applying agile and lean practices for daily uncertainty by Vidas V...
In this presentation I have talked about scrumban - a mix of routines and techniques for daily use in dynamic environment. Like in startups, product manufacture, support or similar cases.
Introduction to Agile & Scrum
This document provides an overview of an introduction workshop on Agile and Scrum. The workshop covers topics such as the history and principles of Agile, an introduction to Scrum frameworks and roles, and exercises on writing user stories and estimating story points. Participants will learn about Agile and Scrum methodologies, how to write and evaluate user stories, and techniques for relative estimation like planning poker. The goal is for participants to understand key Agile and Scrum concepts and practices and be able to apply them.
Agile Scrum Training, Day 1 (1/2)
Training materials for Agile Scrum. Starts with an overview of Agile and Lean. Followed with the Agile Scrum key concepts like Product Owner, Scrum Master, Scrum Team and Product Backlog. Theory is complemented with learnings and best practices from real life software development.
Scrumban
Scrumban Demystified. Talk from Agile New England.
A few of the Scrumban Evolutions from Mamamoth bank from the upcoming book on Scrumban.
More excerpts can be found at facebook.com/scrumban
Learn more at scrumban.io
Do you have a case study of applying the Kanban Method in a Scrum context. We want to learn more from your experiments and results. Contact us at info@codegenesys.com
Using Scrum to Build a Jet Fighter? Yes!
How can Scrum be used to deliver complex integrated products, like a fighter aircraft?
It's been done, and done successfully.
How do you keep multiple teams aligned on the same delivery using Scrum?
This is a brief Infographic describing a quote from Jeff Sutherland published in HBR, May-June 2018 "Agile at Scale"
Link: https://hbr.org/2018/05/agile-at-scale
What is-agile henrik kniberg august 20 2013
This document discusses Agile project planning and estimation techniques. It notes that estimates are often wrong due to factors like changing requirements, irrelevant information, and anchoring biases. Instead of estimating time, Agile recommends estimating the relative size of features and measuring team velocity over iterations to forecast release plans and timelines. Estimates should be done by developers and re-estimated continuously throughout the project rather than relying on early estimates.
Agile Estimating and Planning Using Scrum
This presentation contracts the more traditional ways of planning and estimating projects with Agile/Scrum practices.
Scrum Introduction
This document provides an introduction to the Scrum framework for agile software development. It describes Scrum as an iterative, incremental framework that uses self-organizing cross-functional teams to deliver complex products. The key aspects of Scrum covered include the roles of product owner, Scrum master and development team, the Scrum events of sprint planning, daily stand-ups, sprint reviews and retrospectives, and the artifacts of product and sprint backlogs and burn-down charts. The document provides an overview of how Scrum is intended to provide transparency, inspection, and adaptation to optimize predictability and control of risk.
Lightning Talk: An Introduction To Scrum
Scrum is an agile development methodology that focuses on roles, backlogs, and time-boxed meetings. There are three core roles: the Scrum Master enforces practices and removes roadblocks, the Product Owner maintains the backlog and user stories, and the self-organizing Team delivers working software each sprint. Artifacts include the Product Backlog of prioritized user stories and the Sprint Backlog of selected stories. Sprints are 30-day cycles where selected stories are demonstrated as shippable at the end. Meetings include Planning, Daily Scrums, a Sprint Review, and Retrospective.
Scrum Basics
The document provides an overview of Scrum basics and components. It introduces Scrum as an Agile framework and discusses its core elements - events like sprints, planning and reviews; roles like product owner and scrum master; and artifacts like product backlog and sprint backlog. It also covers related concepts like capacity, velocity and how Scrum compares to Agile approaches. The document concludes by suggesting resources to learn more about Scrum and offers coaching for teams to understand how to apply Scrum.
Introduction to agile and scrum
1. The document provides an overview of practical scrum concepts including lean thinking, agile principles, scrum roles and ceremonies.
2. It discusses the roles of the product owner, scrum master and team in scrum and describes the four main scrum ceremonies: sprint planning, daily scrum, sprint review, and retrospective.
3. Key aspects of each ceremony are outlined such as their purpose, participants, and goals to continuously deliver working software and improve the process.
Modern Software Methodologies(Agile ,Scrum & Lean) + CASE STUDY(Google)
This document discusses modern software methodologies like Agile and Scrum. It provides an overview of Agile principles like valuing individuals, working software, customer collaboration and responding to change. Specific Agile frameworks like Scrum and Kanban are described, including Scrum processes like sprints, stand-up meetings and prioritizing a backlog. Google's software development methodology is also summarized, which focuses on tools like Percolator, Dremel and Pregel for incremental processing, analytics and graph processing. The document concludes with an overview of Google's 20% time rule for employees to work on self-directed projects.
Modern Professional Scrum using Flow and Kanban - Agile and Beyond Detroit 2019
Should you use Scrum or Kanban? You don’t have to choose: Scrum teams improve when they look at flows inside and outside their sprints from a Lean/Kanban perspective. In this session we will talk about Kanban-related myths prevalent in the Scrum world and identify common ground between them. We will look at ways to bring Kanban flow into your Scrum: the Kanban-based Sprint/product backlog, flow-based daily Scrum, visualizing aging work, and flow-based Sprint planning .We will describe ways to wrap Scrum with a Kanban flow system, and how DevOps fits into this picture.
You’ll leave with a better understanding of how Scrum, Kanban, and DevOps relate to each other and with ideas for experiments to try when back at work.
Scrum Gathering Shanghai - April 2010
This was my keynote speech at the the Scrum Gathering in Shanghai, 2010. it's about the use of Scrum with the XP technical practices.
Introduction To Agile And Scrum
The document introduces Agile and Scrum concepts. It discusses Scrum roles like ScrumMaster and Product Owner and the team. The Agile manifesto values individuals and interactions over processes and tools. Sprints occur over 24 hours and 2 weeks where a backlog of user stories is implemented in tasks. User stories follow a format of "As a <role> I want <goal> so that <benefit>". Metrics show Agile can increase productivity, quality, satisfaction while decreasing costs. Resources provided for learning more.
Introduction to Lean, Agile, Scrum, & XP
This document provides an introduction to Lean, Agile, Scrum, and XP. It defines Lean as focusing on identifying value and optimizing processes. Agile emphasizes responding quickly to change through principles like valuing individuals, working software, and customer collaboration. Scrum is a framework that uses short cycles, daily stand-ups, and product backlogs to organize complex work. XP includes practices like pair programming, test-driven development, and collective code ownership.
Scrumban - benefits of both the worlds
#Scrum is very popular these days but #kanban is suitable for better organizational level continuous improvement. We use #scrumban to get the benefits of both the worlds. Its a combination of good practices of scrum with kanban.
Scrum in an hour
Scrum is an agile framework for managing complex projects. It emphasizes transparency, inspection, and adaptation. Key aspects of Scrum include short sprints with fixed durations, daily stand-ups, sprint planning and reviews, and retrospectives. The product owner prioritizes features in the backlog and the cross-functional team works to complete them in sprints. Applying Scrum principles like frequent delivery, transparency, and process improvement can help manage uncertainty, deliver value faster, improve quality, and eliminate waste.
Scrum Master 101
This document provides an overview of the roles and responsibilities of a Scrum Master compared to a traditional Project Manager in a Waterfall methodology. It describes how a Scrum Master is primarily focused on facilitating Agile ceremonies like planning, daily standups, and retrospectives. Their key responsibilities include removing impediments for the team, coaching them in Agile practices, and helping to manage team dynamics. The document also provides examples of questions for clients and candidates to determine if a Scrum Master role and individual are a good fit.
What's hot (20)
Scrumban - applying agile and lean practices for daily uncertainty by Vidas V...
Scrumban - applying agile and lean practices for daily uncertainty by Vidas V...
Modern Software Methodologies(Agile ,Scrum & Lean) + CASE STUDY(Google)
Modern Software Methodologies(Agile ,Scrum & Lean) + CASE STUDY(Google)
Modern Professional Scrum using Flow and Kanban - Agile and Beyond Detroit 2019
Modern Professional Scrum using Flow and Kanban - Agile and Beyond Detroit 2019
Similar to What Is Scrum?
What isscrum
Scrum is an agile framework for developing complex products using iterative incremental development. It is grounded in empirical process control theory and employs short development cycles called sprints to optimize predictability and control risk. Scrum uses four meetings - planning, daily scrum, sprint review, and retrospective - and three roles - product owner, scrum master, and team. The framework was developed in the 1990s based on lean principles and the rugby sport.
Why Scrum?
Why Scrum? Scrum is conceptually a very, very simple process framework. What is it about Scrum that is generating some much buzz in the software development community? Why are companies, both big and small, abandoning traditional approaches such as Water Fall and RUP, in favour of Scrum?
certificate in agile project management sample material
The document discusses various agile methodologies including Scrum, Extreme Programming, Test Driven Development, Lean, and Kanban. It provides details on Scrum, which is the most popular agile framework. Scrum uses short iterative development cycles called sprints where cross-functional teams work to deliver working software increments. It emphasizes self-organization and adaptive planning. The key roles in Scrum are the Product Owner, Development Team, and Scrum Master.
Intro to scrum
Introduction to Scrum bases, how the Scrum was developed, why the Scrum is widely used, what the Scrum framework defines
Intro to Scrum for Software Development Team
Here are the steps to break down a user story into a sprint backlog:
1. The product owner presents the user story to the team:
"As a vacation planner, I want to see potential destinations on a map so I can pick a location."
2. The team discusses what needs to be done to implement the story and breaks it into specific tasks:
- Design database schema for destinations
- Create destinations table
- Add sample destinations to database
- Design map view UI
- Integrate map view into app
- Display destinations on map
3. Estimates are made for each task. Tasks are ordered and pulled into the sprint backlog based on priority, dependencies, and team
2017 scrum-guide-us
The document is the Scrum Guide, which provides the definition and framework of Scrum. It describes Scrum as an agile framework for managing complex work, with roles of Product Owner, Development Team and Scrum Master. It outlines Scrum events like the Sprint, Sprint Planning, Daily Scrum, Sprint Review and Retrospective. It also describes Scrum artifacts like the Product Backlog, Sprint Backlog and Increment. The guide was created by Ken Schwaber and Jeff Sutherland, who developed the Scrum framework.
2020 scrum-guide | The Definitive Guide to Scrum: The Rules of the Game
This document provides an overview of the Scrum framework for project management. It defines Scrum and its core components: roles (Product Owner, Development Team, Scrum Master), events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Retrospective), and artifacts (Product Backlog, Sprint Backlog, Increment). It describes how Scrum uses an empirical, iterative process based on transparency, inspection, and adaptation to manage complex work. The document serves as a guide for using Scrum and was developed by its creators, Ken Schwaber and Jeff Sutherland.
2017-Scrum-Guide-US.pdf
The document is the Scrum Guide, which provides the definition and framework of Scrum. It describes Scrum as an agile framework for managing complex work. Key aspects of Scrum include self-organizing cross-functional teams, a Product Owner who prioritizes backlog items, Sprints which are time boxed iterations used to incrementally deliver working software, and events like the Sprint Planning Meeting, Daily Standup, Sprint Review, and Retrospective.
2017 scrum-guide-us
The document is the Scrum Guide, which provides the definition and framework of Scrum. It describes Scrum as an agile framework for managing complex work, with roles of Product Owner, Development Team and Scrum Master. It outlines Scrum events like the Sprint, Sprint Planning, Daily Scrum, Sprint Review and Retrospective. It also describes Scrum artifacts like the Product Backlog, Sprint Backlog and Increment. The guide was created by Ken Schwaber and Jeff Sutherland, who developed the Scrum framework.
APICS CSCP
Scrum is an agile framework that helps teams break down complex projects into small incremental goals called sprints to promote collaboration and continuous improvement. It is commonly used for software development projects. Some key advantages of the agile scrum methodology include increased flexibility to adapt to changes, improved quality from frequent feedback loops, higher employee satisfaction, and better alignment with customer needs. To learn scrum, individuals can take online or in-person training courses to understand the fundamentals and prepare for certifications like the Certified ScrumMaster which qualifies one to guide teams through the scrum process.
Adopting Scrum
This document provides an overview of adopting the Scrum framework for agile software development. It begins with an introduction to Scrum and its origins. The document then outlines the key steps to adopting Scrum, including finding a Product Owner, building a Product Backlog of prioritized user stories, defining what "Done" means, building a Sprint Backlog from the Product Backlog, and executing a Sprint. Visual tools like burndown charts and task boards are also discussed to provide transparency during a Sprint. The overall goal is to help teams and organizations understand and implement the Scrum framework to facilitate agile, iterative development.
scrum-1-10.pptx
The document provides an introduction to the Scrum framework for agile software development. It discusses that Scrum is an iterative framework that focuses on quickly delivering working software. The document then outlines the history of Scrum, defines its key roles, events, artifacts, and processes. It notes that Scrum uses sprints, daily stand-up meetings, product backlogs and sprint planning to help self-organizing teams deliver working increments of software. The advantages are listed as improved responsiveness and quality, while disadvantages include difficulty predicting future work and needing highly dedicated team members.
Seminar on Scrum
The document provides an overview of Scrum, an agile software development framework. It defines Scrum, discusses its history and introduction. It describes the Scrum framework, including roles like Product Owner and Scrum Master, events like sprint planning and review, and artifacts like product and sprint backlogs. It outlines the Scrum process and discusses applications of Scrum as well as its advantages and disadvantages. The document concludes that Scrum is an effective framework but requires experience and strict adherence to be successful.
Seminar On Scrum
The document provides an overview of Scrum, an agile software development framework. It defines Scrum, discusses its history and introduction. It describes the Scrum framework, including roles like Product Owner and Scrum Master, events like sprint planning and review, and artifacts like product and sprint backlogs. It outlines the Scrum process and provides examples of Scrum applications. It discusses advantages like adaptability and faster delivery, and disadvantages like lack of documentation. It concludes that Scrum is popular for experienced teams that can self-organize, but requires strict adherence to be effective.
2016 scrum-guide-us
The document is the Scrum Guide, which defines Scrum and its roles, events, artifacts, and rules. Scrum is a framework for developing complex products that is lightweight, simple, and difficult to master. It is based on empirical process control theory and values transparency, inspection, and adaptation. The Scrum Team consists of a Product Owner, Development Team, and Scrum Master. The Product Owner is responsible for maximizing product value and managing the Product Backlog.
2016-Scrum-Guide-US
This document outlines the Scrum Guide, which provides the definition and rules of Scrum. Scrum is an agile framework for managing complex work. Key aspects of Scrum include self-organizing cross-functional teams, a Product Owner who prioritizes work, and time-boxed sprint cycles for delivering working software. The guide describes Scrum values, roles, events, and artifacts to help teams use an empirical process of transparency, inspection, and adaptation.
2016 scrum-guide-us
This document outlines the Scrum Guide, which defines Scrum and its roles, events, artifacts, and rules. Scrum is an agile framework for managing complex work. Key aspects of Scrum include short "Sprints" of work, daily stand-up meetings, sprint planning and review sessions, and artifacts like the Product and Sprint Backlogs to track work. Scrum values self-organizing, cross-functional teams and transparency through its defined process of iteration and inspection.
MultiUni - IT150 Intro to Scrum and Agile
The document discusses key concepts in agile project management including Scrum. It defines Scrum as an agile approach to management and outlines its key roles, artifacts, activities, and processes. The main Scrum events include sprint planning meetings, daily stand-ups, sprints, sprint reviews, and retrospectives. Planning tools like product backlogs, sprint backlogs, and burn-down charts are also introduced.
Scrum guide
The document is a guide to the Scrum framework for developing products. It describes Scrum as a lightweight framework that is difficult to master. The Scrum framework consists of roles, events, artifacts, and rules. It is based on empirical process control and values transparency, inspection, and adaptation. The key Scrum roles are the Product Owner, Development Team, and Scrum Master. Main Scrum events are the Sprint, Daily Scrum, Sprint Review, and Retrospective. Main artifacts are the Product Backlog and Sprint Backlog. A Sprint is a fixed length period usually one month or less to develop a product Increment.
Scrum guide
This document provides an overview and definition of Scrum, an agile framework for managing complex product development projects. Key points include:
- Scrum uses empirical process control with transparency, inspection, and adaptation to optimize predictability and control risk.
- The Scrum Team consists of a Product Owner, Development Team, and Scrum Master. Teams are self-organizing and cross-functional.
- The Product Owner is responsible for maximizing product value and managing the Product Backlog. The Development Team does the work, while the Scrum Master ensures Scrum process is followed.
- Scrum uses short Sprints, daily Scrums, Sprint Planning, Reviews, and Retrospectives as
Similar to What Is Scrum? (20)
certificate in agile project management sample material
certificate in agile project management sample material
2020 scrum-guide | The Definitive Guide to Scrum: The Rules of the Game
2020 scrum-guide | The Definitive Guide to Scrum: The Rules of the Game
More from Kane Mar
Why scrum and Agile
Why Scrum and Agile ... by the numbers: A look at the numbers and growth of Scrum and Agile over the last 10 years.
A short history of Agile software development
My 'Short History of Agile Software Development' presentation at the Innovation Campus, University of Wollongong.
I only had 20 minutes to speak, so I did an overview of the origins of 'Software Engineering' ('68 NATO conference) through to some new and different approaches to software. Along the way I talked about the 'New New Product Development Game', Scrum, Extreme Programming, the Agile Manifesto and some thoughts about what the future holds.
Introducing Scrum to an Organization
This document introduces Scrum and provides guidance on introducing Agile and Scrum to an organization. It defines Scrum roles and meetings. It notes that adopting Scrum requires systemic change that is difficult but can make an organization more productive and innovative. It recommends adopting Scrum both top-down with executive support and bottom-up driven by teams, starting small with at-risk projects to minimize risk while gaining support.
Agile Games
Three games were presented to help Agile teams understand Agile principles and values: The Failure Bow, Go, and The Marshmallow Challenge. The Failure Bow involves teams of 10 people passing a ball around and allowing members to take each other's places. Go involves indicating someone you want to replace and waiting for "Go!" to take their space. The Marshmallow Challenge tasks building the tallest freestanding structure with a marshmallow on top within 18 minutes using materials like spaghetti, string or tape.
QCon Beijing - April 2010
The document discusses technical debt in software development. It defines technical debt as deferred work that accumulates when high quality standards are not enforced or corners are cut to achieve velocity targets. This debt makes code complex and hard to change, reducing a team's ability to meet business needs. The document recommends practices like continuous integration, test-driven development, and refactoring to avoid debt. It also discusses strategies for identifying and paying off existing debt over time.
Continuous Deployment
My Continuous Deployment talk that I gave at Agile Australia 2010. It was really a collection of different stories about how companies have used CD.
Agile Team Games
During Agile Australia 2010, I teamed up with Phil Abernathy to present a variety of different team exercises and games. The session starts quite gently and builds up pace culminating in the Ball Point Game right at the very end.
Agile Engineering Practices
1. Agile engineering practices like continuous integration, test-driven development, refactoring, and pair programming can help software teams build higher quality code more efficiently.
2. Continuous integration involves developers integrating code changes frequently through automated builds and tests to quickly detect errors.
3. Test-driven development uses short development cycles where developers write automated tests before code and refactor code to maintain test coverage.
Brisbane Scrum Users Group.2009 Feb25
This document discusses technical debt and what can be done about it. Technical debt occurs when necessary work is deferred, such as not upgrading compilers or conforming to guidelines. Over time, this deferred work accumulates and slows down a project. To address technical debt, it is important to make the debt visible by keeping a list. Technical debt can be avoided by enforcing high quality standards and not cutting corners. It can also be paid off over time by starting with continuous integration and writing tests around customer defects to build up testing around brittle code areas. An anti-pattern to avoid is trying to write a comprehensive testing framework for an entire product without focusing on the most important customer defects first.
More from Kane Mar (9)
Recently uploaded
OpenID AuthZEN Interop Read Out - Authorization
During Identiverse 2024 and EIC 2024, members of the OpenID AuthZEN WG got together and demoed their authorization endpoints conforming to the AuthZEN API
Main news related to the CCS TSI 2023 (2023/1695)
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
TrustArc Webinar - 2024 Global Privacy Survey
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
How to Get CNIC Information System with Paksim Ga.pptx
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
Digital Marketing Trends in 2024 | Guide for Staying Ahead
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
Generating privacy-protected synthetic data using Secludy and Milvus
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
UiPath Test Automation using UiPath Test Suite series, part 6
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
Best 20 SEO Techniques To Improve Website Visibility In SERP
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Project Management Semester Long Project - Acuity
Acuity is an innovative learning app designed to transform the way you engage with knowledge. Powered by AI technology, Acuity takes complex topics and distills them into concise, interactive summaries that are easy to read & understand. Whether you're exploring the depths of quantum mechanics or seeking insight into historical events, Acuity provides the key information you need without the burden of lengthy texts.
Webinar: Designing a schema for a Data Warehouse
Are you new to data warehouses (DWH)? Do you need to check whether your data warehouse follows the best practices for a good design? In both cases, this webinar is for you.
A data warehouse is a central relational database that contains all measurements about a business or an organisation. This data comes from a variety of heterogeneous data sources, which includes databases of any type that back the applications used by the company, data files exported by some applications, or APIs provided by internal or external services.
But designing a data warehouse correctly is a hard task, which requires gathering information about the business processes that need to be analysed in the first place. These processes must be translated into so-called star schemas, which means, denormalised databases where each table represents a dimension or facts.
We will discuss these topics:
- How to gather information about a business;
- Understanding dictionaries and how to identify business entities;
- Dimensions and facts;
- Setting a table granularity;
- Types of facts;
- Types of dimensions;
- Snowflakes and how to avoid them;
- Expanding existing dimensions and facts.
Recently uploaded (20)
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
Digital Marketing Trends in 2024 | Guide for Staying Ahead
Digital Marketing Trends in 2024 | Guide for Staying Ahead
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
UiPath Test Automation using UiPath Test Suite series, part 6
UiPath Test Automation using UiPath Test Suite series, part 6
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
What Is Scrum?
- 1. What is Scrum? Kane Mar Certified Scrum Coach and Trainer. http://KaneMar.com http://Scrumology.com.au
- 2. Creative Commons Attribution 3.0 Kane Mar and Others (see credits) You are free: to Share — to copy, distribute and transmit the work to Remix — to adapt the work Under the following conditions: Attribution. You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work) http://creativecommons.org/licenses/by/3.0/
- 3. Agenda About me. What is Scrum? A brief history of Scrum What is Scrum?
- 4. About Me.
- 5. What is Scrum? “Scrum is a framework for developing complex products and systems. It is grounded in empirical process control theory. Scrum employs an iterative, incremental approach to optimize predictability and control risk. ” -Ken Schwaber
- 6. A brief history of Scrum W. Edwards Deming Lean Manufacturing, Toyota Production System (TPS), TQM Deming’s philosophy: When people and organizations focus primarily on quality, quality tends to increase and costs fall over time. However, when people and organizations focus primarily on costs, costs tend to rise and quality declines over time.
- 7. A brief history of Scrum Act Plan Check Do
- 8. A brief history of Scrum “The New New Product Development Game,” by Hirotaka Takeuchi, Ikujiro Nonaka. Havard Business Review, Jan 1, 1986. Fuji-Xerox, Canon, Honda, NEC, Epson, Brother, 3M, Xerox, and HP. References the sport of Rugby
- 9. A brief history of Scrum “Scrum Development Process,” Ken Schwaber and Jeff Sutherland, OOPSLA 1995 “Agile Software Development with Scrum,” Ken Schwaber and Mike Beedle, 2001 “Agile Project Management with Scrum,” Ken Schwaber “Scrum and the Enterprise,” Ken Schwaber
- 10. What is Scrum?
- 11. What is Scrum? Sprint Planning
- 12. What is Scrum? Daily Sprint Sprint
- 13. What is Scrum? Sprint Review & Retro
- 14. 4 meetings, 3 roles Scrum is characterised by 4 meetings Planning Meeting, Daily Scrum, Review Meeting and Retrospective And, three roles Product Owner, ScrumMaster and Team
- 15. What is Scrum? “Scrum is a framework for developing complex products and systems. It is grounded in empirical process control theory. Scrum employs an iterative, incremental approach to optimize predictability and control risk. ” -Ken Schwaber
- 18. References “Agile Software Development with Scrum,” Ken Schwaber and Mike Beedle, 2001 “Agile Project Management with Scrum”, Ken Schwaber “Scrum and the Enterprise”, Ken Schwaber “Scrum in 5 minutes”, Softhouse Nordic AB http://www.softhouse.se/Uploades/Scrum_eng_webb.pdf
- 19. This Presentation http://KaneMar.com/downloads This presentation can be used for commercial purposes provide that the license and attribution information is retained.