Scrum presentation designed to give readers basic understanding of Scrum's principles. Any copyrighted materials referenced in this document is for educational purposes only and protected under fair use.
The document discusses Agile SCRUM project development methodology. It provides an overview of SCRUM principles and processes including short iterative development cycles called sprints, daily stand-up meetings, sprint planning, tracking sprint backlogs and burn downs, sprint reviews and retrospectives. The roles of product owners, scrum masters and self-organizing cross-functional teams are also summarized.
Full course available at: http://masterofproject.com/courses/agile-project-management-scrum-framework-certification-prep
Course Description
The Agile & Scrum Certification Training course imparts knowledge on the Agile and Scrum values, helps you build the requisite skills and gain expertise in the domain. The course provides immense clarity on vital concepts of scrum and agile to help you clear the certification exam in your first attempt. The course aims to make you an expert in the Scrum ways, enhancing your capability to deliver shippable products by the end of each Sprint. With the practical application of the agile methodologies you would be able to maximize business value, while mitigating potential risks.
Features
50+ Lectures
10+ Hours
Lifetime Access
100% Online & Self Paced
30 day money back guarantee!
Course Completion Certificate
What am I going to get from this course?
Learn the Agile Methodologies and Agile Project Management
Learn Scrum Framework
Learn practical implications of Scrum over a sample project
Get ready for Scrum Certification exams (PMI-ACP, CSM, PSM, CSPO, PSPO, CSD, PSD)
Learn Scrum Team
Learn Scrum Events
Learn Scrum Artifacs
Learn Extreme Programming (XP) Agile Methodology briefly.
Learn Lean Agile Methodology briefly.
Learn Kanban Agile Methodology briefly.
Learn the differences of Agile & Scrum Certifications provided by different organizations
Qualify for the 21 Contact Hours Agile Training requirement of PMI for the PMI-ACP certification.
Earn 15 SEUs under Category E: Independent Learning of Scrum Alliance
Earn 14 PDUs if you are a PMP already.
What is the target audience?
The Agile & Scrum certification is best suited for:
Team Leaders
Project Managers
Members of Scrum teams such as developers, Scrum Masters, and Product Owners
Managers of Scrum teams
Teams transitioning to Scrum
Professionals intending to pursue the Scrum Master certification
The document discusses the different levels of planning in Agile development: release planning, iteration planning, and task planning. It provides details on each level, including who is involved, how to define a release plan, estimating velocity, common problems and solutions, and examples. The key aspects covered are the differences between releases and iterations, estimating at each level, and breaking down stories into tasks.
This document discusses the adoption and implementation of scrum, an agile software development framework. It begins with an overview of scrum and its alignment with the agile manifesto. It then addresses determining if scrum is suitable, comparing scrum to other agile methodologies, the increasing maturity and adoption of scrum. The document also discusses practical considerations for adopting scrum such as addressing common questions, challenges, and pains experienced. It concludes by listing some scrum project management tools available.
This document provides an overview of Scrum training. It introduces the trainer, Deniz Gungor, and their background. It then outlines the agenda, which will cover Scrum fundamentals, a Scrum simulation game, and the Scrum framework. Key aspects of Scrum are defined, including self-organizing Scrum teams, iterative delivery, the Product Owner, Scrum Master, Development Team, events like the Daily Scrum and Sprint Review, and artifacts like the Product Backlog and Sprint Backlog. The training will help participants understand and apply the Scrum framework to projects.
It is the team who does all the work. Team is self-organising. Team decides and plans. So what is the role of scrum master? Is it a full time role? How is it different from a project manager? Can a project lead or manager be a scrum master? It is probably the least understood and the most abused role in scrum. Let's explore these points in details further on April 10, 3:00 PM.
3 Roles in Scrum
Role of scrum master
Challenges of a scrum master
Skills, Knowledge & mindset required
Full time or part time?
Future career path of scrum master
Benefits:
Uncover the true role of a scrum master which is that of a facilitator, protector, negotiator and a coach.
Understand the true meaning of coaching.
Learn how scrum master can coach the team.
Understand the skills, knowledge and mindset required as a scrum master.
Perform better as a scrum master by getting introduced to some magical techniques and fad words like gamestorming, innovation games and visual thinking to facilitate collaborative decision making.
Learn points which you can use to make people understand the vital role a scrum master plays.
Appreciate the difference between project manager and a scrum master.
Learn who can be a good scrum master.
Attend the webinar and separate yourself from the crazy herd of people blindly accepting or discarding the role of scrum master!!
The document discusses various aspects of agile software development methodologies like Scrum. It describes the Scrum framework, including roles like Product Owner and Scrum Master. It also covers Scrum artifacts, events, and ceremonies like the sprint, daily standup, planning meeting, review, and retrospective. The document provides information on estimating work, defining done, and managing backlogs to support iterative development with Scrum.
The document discusses Agile SCRUM project development methodology. It provides an overview of SCRUM principles and processes including short iterative development cycles called sprints, daily stand-up meetings, sprint planning, tracking sprint backlogs and burn downs, sprint reviews and retrospectives. The roles of product owners, scrum masters and self-organizing cross-functional teams are also summarized.
Full course available at: http://masterofproject.com/courses/agile-project-management-scrum-framework-certification-prep
Course Description
The Agile & Scrum Certification Training course imparts knowledge on the Agile and Scrum values, helps you build the requisite skills and gain expertise in the domain. The course provides immense clarity on vital concepts of scrum and agile to help you clear the certification exam in your first attempt. The course aims to make you an expert in the Scrum ways, enhancing your capability to deliver shippable products by the end of each Sprint. With the practical application of the agile methodologies you would be able to maximize business value, while mitigating potential risks.
Features
50+ Lectures
10+ Hours
Lifetime Access
100% Online & Self Paced
30 day money back guarantee!
Course Completion Certificate
What am I going to get from this course?
Learn the Agile Methodologies and Agile Project Management
Learn Scrum Framework
Learn practical implications of Scrum over a sample project
Get ready for Scrum Certification exams (PMI-ACP, CSM, PSM, CSPO, PSPO, CSD, PSD)
Learn Scrum Team
Learn Scrum Events
Learn Scrum Artifacs
Learn Extreme Programming (XP) Agile Methodology briefly.
Learn Lean Agile Methodology briefly.
Learn Kanban Agile Methodology briefly.
Learn the differences of Agile & Scrum Certifications provided by different organizations
Qualify for the 21 Contact Hours Agile Training requirement of PMI for the PMI-ACP certification.
Earn 15 SEUs under Category E: Independent Learning of Scrum Alliance
Earn 14 PDUs if you are a PMP already.
What is the target audience?
The Agile & Scrum certification is best suited for:
Team Leaders
Project Managers
Members of Scrum teams such as developers, Scrum Masters, and Product Owners
Managers of Scrum teams
Teams transitioning to Scrum
Professionals intending to pursue the Scrum Master certification
The document discusses the different levels of planning in Agile development: release planning, iteration planning, and task planning. It provides details on each level, including who is involved, how to define a release plan, estimating velocity, common problems and solutions, and examples. The key aspects covered are the differences between releases and iterations, estimating at each level, and breaking down stories into tasks.
This document discusses the adoption and implementation of scrum, an agile software development framework. It begins with an overview of scrum and its alignment with the agile manifesto. It then addresses determining if scrum is suitable, comparing scrum to other agile methodologies, the increasing maturity and adoption of scrum. The document also discusses practical considerations for adopting scrum such as addressing common questions, challenges, and pains experienced. It concludes by listing some scrum project management tools available.
This document provides an overview of Scrum training. It introduces the trainer, Deniz Gungor, and their background. It then outlines the agenda, which will cover Scrum fundamentals, a Scrum simulation game, and the Scrum framework. Key aspects of Scrum are defined, including self-organizing Scrum teams, iterative delivery, the Product Owner, Scrum Master, Development Team, events like the Daily Scrum and Sprint Review, and artifacts like the Product Backlog and Sprint Backlog. The training will help participants understand and apply the Scrum framework to projects.
It is the team who does all the work. Team is self-organising. Team decides and plans. So what is the role of scrum master? Is it a full time role? How is it different from a project manager? Can a project lead or manager be a scrum master? It is probably the least understood and the most abused role in scrum. Let's explore these points in details further on April 10, 3:00 PM.
3 Roles in Scrum
Role of scrum master
Challenges of a scrum master
Skills, Knowledge & mindset required
Full time or part time?
Future career path of scrum master
Benefits:
Uncover the true role of a scrum master which is that of a facilitator, protector, negotiator and a coach.
Understand the true meaning of coaching.
Learn how scrum master can coach the team.
Understand the skills, knowledge and mindset required as a scrum master.
Perform better as a scrum master by getting introduced to some magical techniques and fad words like gamestorming, innovation games and visual thinking to facilitate collaborative decision making.
Learn points which you can use to make people understand the vital role a scrum master plays.
Appreciate the difference between project manager and a scrum master.
Learn who can be a good scrum master.
Attend the webinar and separate yourself from the crazy herd of people blindly accepting or discarding the role of scrum master!!
The document discusses various aspects of agile software development methodologies like Scrum. It describes the Scrum framework, including roles like Product Owner and Scrum Master. It also covers Scrum artifacts, events, and ceremonies like the sprint, daily standup, planning meeting, review, and retrospective. The document provides information on estimating work, defining done, and managing backlogs to support iterative development with Scrum.
Scrum is an agile framework that focuses on rapid delivery of working software in short cycles called sprints. It consists of self-organizing cross-functional teams, regular sprints with daily stand-ups, and artifacts like a product backlog, sprint backlog, and burn-down charts. The product owner prioritizes the backlog, the scrum master facilitates the process, and teams work to complete items in sprints usually 2-4 weeks long. Scrum enables rapid, flexible response to change through inspection and adaptation at the end of each sprint.
Introduction to the scrum framework: roles, activities and artifacts.
Scrum is an agile methodology for project management, to create a high quality product.
www.nieldeckx.be
The document discusses Scrumban, which combines elements of Scrum and Kanban. It outlines 5 guiding questions about value, flow, quality, joy, and continuous improvement. It then describes 5 steps of evolution away from sprints, including removing artificial goals and delays. Estimation is de-emphasized in favor of proper slicing and forecasting using throughput. Metrics like WIP, flow diagrams and scatterplots with cycle times are recommended. Finally, it promotes several referenced books and resources on Scrumban and Kanban.
Scrum vs SAFe | Differences Between Scrum and Scaled Agile Framework | EdurekaEdureka!
YouTube Link: https://youtu.be/c2e0BchglOc
** Certified Scrum Master Training: https://www.edureka.co/certified-scrum-master-certification-training **
This Edureka PPT on "Scrum vs SAFe" video will help you understand the key differences between the two most popular frameworks Scrum and Scaled Agile Framework (SAFe). The topics discussed in this course are listed below:
What is Scrum?
What is SAFe?
Major Differences Between Scrum and SAFe
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Castbox: https://castbox.fm/networks/505?country=in
Scrum is an agile framework for managing projects that uses short cycles of work called sprints to incrementally deliver working software. There are three main roles in Scrum - the Product Owner prioritizes features in the Product Backlog, the Scrum Master facilitates the process, and the self-organizing Team works to complete the highest priority items each sprint. Key Scrum artifacts include the Product Backlog, Sprint Backlog, and Burn Down Chart. The main Scrum ceremonies are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective meetings.
This document provides an introduction to Agile Scrum methodology. It defines Agile and Scrum, outlines the history and principles of Scrum, and describes the core components and processes in Scrum including roles, ceremonies, artifacts, and sprints. The document explains that Scrum is an iterative Agile framework used for managing complex projects, with self-organizing cross-functional teams working in short sprints to deliver working software increments based on prioritized backlogs.
Scrum is an agile software development methodology where self-organizing teams work in short development cycles called sprints to build software incrementally. It focuses on collaboration, flexibility, and delivering working software frequently. Key components of Scrum include roles like the product owner and scrum master, a product backlog to track requirements, sprints for incremental development, and daily stand-up meetings. Scrum aims to be flexible and adaptive to changing requirements while maximizing productivity through its empirical process control methods.
This is a short introduction to the practice of Sprint Planning in Scrum. It would be useful for people new to Scrum or Agile. For more, comment or write to read my blog : http://agilediary.wordpress.com/
This document provides information on Scrumban, which is a hybrid agile approach that combines elements of Scrum and Kanban. It discusses why Scrumban works by starting with the current process and respecting existing roles while enabling gradual change. It also lists some of the top reasons why agile adoptions fail, such as not having a clear reason for changing or forcing top-down changes. The document then explores Kanban principles and practices and how they can be applied in a Scrum context. It provides examples of when and how Scrumban can be useful for teams.
The first part of this presentation is a situational assessment of typical challenges in IT project delivery using the SCRAP (Situation, Complication, Resolution, Action, Proof) model. This is essentially a business case for Agile. So if you are looking for ways to get buy-in for Agile, this is the place to be.
The second part of this presentation shows you what Agile is from 50,000 ft. From this high up, we'll be covering the essential elements from a business and management perspective. We'll cover what Agile is, what it does, how it works and what it achieves.
If you are interested in learning or communicating the value of Agile, then this is the presentation for you!
Please email me if you would like a download.
This document provides an overview of agile methodology for software development. It discusses how agile practices arose in response to the limitations of traditional waterfall approaches. The core principles of agile include valuing individuals and interactions, working software, customer collaboration, and responding to change. Agile methods embrace changing requirements, frequent delivery of working software, collaboration between business and technical teams, self-organizing teams, and continuous improvement.
This document provides an introduction to Agile project management frameworks like Scrum and Kanban. It discusses the limitations of traditional waterfall project management and how Agile aims to address these issues through iterative development, collaboration, and flexibility. Key aspects of Scrum like roles, events, artifacts, estimation and user stories are explained. Kanban concepts such as visualizing workflow, limiting work in progress, and managing flow are also covered. The document recommends resources for learning more about Agile, Scrum, Kanban and hybrid approaches.
The document discusses agile project management and compares it to the traditional approach. It outlines the key phases and characteristics of the Scrum framework, an agile method for managing iterative development projects. Scrum uses short "sprints" to iteratively develop software in increments, with daily stand-ups and involvement from customers and stakeholders. At the end of each sprint, completed work is reviewed and new work is planned for the next sprint. Scrum provides flexibility to adapt the project as requirements change compared to the traditional sequential approach.
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.
The "2017 Scrum by Picture" is something you can call Scrum Guide illustrated. It is based on the newest version of "Scrum Guide".
You will find the theory, scrum values, scrum team, scrum events including sprint, sprint planning, daily scrum, review and retrospective as well as scrum artifacts. All of those is explained in easy to follow, illustrated nicely presentation, which can assist you to catch the idea behind Scrum.
Feel free to share "2017 Scrum by Picture" with your Scrum friends.
Increase productivity and improve the predictability of software projects. Interest in the Scrum Agile process framework is exploding as companies discover that Scrum enables them to manage software projects with greater reliability and improve responsiveness to customers. This class introduces the skills that project managers and team leaders need to perform the basic steps of a Scrum process for software development.
-Learn how Scrum practices relate to project management fundamentals
-Learn the essentials of Scrum as a software development process
-Learn the three Scrum roles, three Scrum meetings, and three Scrum artifacts
-Project Managers and team leads learn basic planning, tracking, and management skills
-Product Managers learn how to develop and prioritize requirements
-Team members learn how to estimate and break down work
Scrum is an agile framework for managing product development that uses short cycles of work called sprints to incrementally build a product. Key aspects of scrum include self-organizing cross-functional teams, a product backlog maintained by a product owner, and regular sprints, daily scrums, sprint planning and retrospectives to facilitate collaboration and continuous improvement. Scrum provides principles for iterative development and adaptation to change throughout the product life cycle.
Scrum is a framework for managing product development that divides work into sprints. Key roles include the Product Owner who manages the product backlog, the Development Team who does the work, and the Scrum Master who facilitates the process. The team holds regular stand-up meetings, sprint planning meetings, sprint reviews, and retrospectives. They track progress using artifacts like the product backlog, sprint backlog, and burndown charts. The framework aims to be transparent, inspect progress frequently, and adapt as needed.
This document provides an introduction to Agile SCRUM methodology. It defines Agile as an iterative approach to software delivery that builds incrementally from the start. SCRUM is described as the most commonly used Agile framework. The core components of SCRUM include roles like Product Owner and Scrum Master, ceremonies such as Sprint Planning and Daily Scrum, and artifacts like the Product Backlog and Sprint Backlog. The document outlines the SCRUM process, which involves prioritizing work, committing to sprints, and delivering working software incrementally in short cycles with daily stand-ups and sprint reviews.
This document provides a summary of key concepts from Chapter 4 of the book "Essential Scrum". It describes the Scrum framework, roles, artifacts, and events. The Scrum roles include the Product Owner, Scrum Master, and Development Team. Key artifacts are the Product Backlog and Sprint Backlog. Main events are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. The goal is to help teams self-organize to deliver working software in short cycles through transparency, inspection, and adaptation.
Scrum is an agile framework that focuses on rapid delivery of working software in short cycles called sprints. It consists of self-organizing cross-functional teams, regular sprints with daily stand-ups, and artifacts like a product backlog, sprint backlog, and burn-down charts. The product owner prioritizes the backlog, the scrum master facilitates the process, and teams work to complete items in sprints usually 2-4 weeks long. Scrum enables rapid, flexible response to change through inspection and adaptation at the end of each sprint.
Introduction to the scrum framework: roles, activities and artifacts.
Scrum is an agile methodology for project management, to create a high quality product.
www.nieldeckx.be
The document discusses Scrumban, which combines elements of Scrum and Kanban. It outlines 5 guiding questions about value, flow, quality, joy, and continuous improvement. It then describes 5 steps of evolution away from sprints, including removing artificial goals and delays. Estimation is de-emphasized in favor of proper slicing and forecasting using throughput. Metrics like WIP, flow diagrams and scatterplots with cycle times are recommended. Finally, it promotes several referenced books and resources on Scrumban and Kanban.
Scrum vs SAFe | Differences Between Scrum and Scaled Agile Framework | EdurekaEdureka!
YouTube Link: https://youtu.be/c2e0BchglOc
** Certified Scrum Master Training: https://www.edureka.co/certified-scrum-master-certification-training **
This Edureka PPT on "Scrum vs SAFe" video will help you understand the key differences between the two most popular frameworks Scrum and Scaled Agile Framework (SAFe). The topics discussed in this course are listed below:
What is Scrum?
What is SAFe?
Major Differences Between Scrum and SAFe
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Castbox: https://castbox.fm/networks/505?country=in
Scrum is an agile framework for managing projects that uses short cycles of work called sprints to incrementally deliver working software. There are three main roles in Scrum - the Product Owner prioritizes features in the Product Backlog, the Scrum Master facilitates the process, and the self-organizing Team works to complete the highest priority items each sprint. Key Scrum artifacts include the Product Backlog, Sprint Backlog, and Burn Down Chart. The main Scrum ceremonies are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective meetings.
This document provides an introduction to Agile Scrum methodology. It defines Agile and Scrum, outlines the history and principles of Scrum, and describes the core components and processes in Scrum including roles, ceremonies, artifacts, and sprints. The document explains that Scrum is an iterative Agile framework used for managing complex projects, with self-organizing cross-functional teams working in short sprints to deliver working software increments based on prioritized backlogs.
Scrum is an agile software development methodology where self-organizing teams work in short development cycles called sprints to build software incrementally. It focuses on collaboration, flexibility, and delivering working software frequently. Key components of Scrum include roles like the product owner and scrum master, a product backlog to track requirements, sprints for incremental development, and daily stand-up meetings. Scrum aims to be flexible and adaptive to changing requirements while maximizing productivity through its empirical process control methods.
This is a short introduction to the practice of Sprint Planning in Scrum. It would be useful for people new to Scrum or Agile. For more, comment or write to read my blog : http://agilediary.wordpress.com/
This document provides information on Scrumban, which is a hybrid agile approach that combines elements of Scrum and Kanban. It discusses why Scrumban works by starting with the current process and respecting existing roles while enabling gradual change. It also lists some of the top reasons why agile adoptions fail, such as not having a clear reason for changing or forcing top-down changes. The document then explores Kanban principles and practices and how they can be applied in a Scrum context. It provides examples of when and how Scrumban can be useful for teams.
The first part of this presentation is a situational assessment of typical challenges in IT project delivery using the SCRAP (Situation, Complication, Resolution, Action, Proof) model. This is essentially a business case for Agile. So if you are looking for ways to get buy-in for Agile, this is the place to be.
The second part of this presentation shows you what Agile is from 50,000 ft. From this high up, we'll be covering the essential elements from a business and management perspective. We'll cover what Agile is, what it does, how it works and what it achieves.
If you are interested in learning or communicating the value of Agile, then this is the presentation for you!
Please email me if you would like a download.
This document provides an overview of agile methodology for software development. It discusses how agile practices arose in response to the limitations of traditional waterfall approaches. The core principles of agile include valuing individuals and interactions, working software, customer collaboration, and responding to change. Agile methods embrace changing requirements, frequent delivery of working software, collaboration between business and technical teams, self-organizing teams, and continuous improvement.
This document provides an introduction to Agile project management frameworks like Scrum and Kanban. It discusses the limitations of traditional waterfall project management and how Agile aims to address these issues through iterative development, collaboration, and flexibility. Key aspects of Scrum like roles, events, artifacts, estimation and user stories are explained. Kanban concepts such as visualizing workflow, limiting work in progress, and managing flow are also covered. The document recommends resources for learning more about Agile, Scrum, Kanban and hybrid approaches.
The document discusses agile project management and compares it to the traditional approach. It outlines the key phases and characteristics of the Scrum framework, an agile method for managing iterative development projects. Scrum uses short "sprints" to iteratively develop software in increments, with daily stand-ups and involvement from customers and stakeholders. At the end of each sprint, completed work is reviewed and new work is planned for the next sprint. Scrum provides flexibility to adapt the project as requirements change compared to the traditional sequential approach.
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.
The "2017 Scrum by Picture" is something you can call Scrum Guide illustrated. It is based on the newest version of "Scrum Guide".
You will find the theory, scrum values, scrum team, scrum events including sprint, sprint planning, daily scrum, review and retrospective as well as scrum artifacts. All of those is explained in easy to follow, illustrated nicely presentation, which can assist you to catch the idea behind Scrum.
Feel free to share "2017 Scrum by Picture" with your Scrum friends.
Increase productivity and improve the predictability of software projects. Interest in the Scrum Agile process framework is exploding as companies discover that Scrum enables them to manage software projects with greater reliability and improve responsiveness to customers. This class introduces the skills that project managers and team leaders need to perform the basic steps of a Scrum process for software development.
-Learn how Scrum practices relate to project management fundamentals
-Learn the essentials of Scrum as a software development process
-Learn the three Scrum roles, three Scrum meetings, and three Scrum artifacts
-Project Managers and team leads learn basic planning, tracking, and management skills
-Product Managers learn how to develop and prioritize requirements
-Team members learn how to estimate and break down work
Scrum is an agile framework for managing product development that uses short cycles of work called sprints to incrementally build a product. Key aspects of scrum include self-organizing cross-functional teams, a product backlog maintained by a product owner, and regular sprints, daily scrums, sprint planning and retrospectives to facilitate collaboration and continuous improvement. Scrum provides principles for iterative development and adaptation to change throughout the product life cycle.
Scrum is a framework for managing product development that divides work into sprints. Key roles include the Product Owner who manages the product backlog, the Development Team who does the work, and the Scrum Master who facilitates the process. The team holds regular stand-up meetings, sprint planning meetings, sprint reviews, and retrospectives. They track progress using artifacts like the product backlog, sprint backlog, and burndown charts. The framework aims to be transparent, inspect progress frequently, and adapt as needed.
This document provides an introduction to Agile SCRUM methodology. It defines Agile as an iterative approach to software delivery that builds incrementally from the start. SCRUM is described as the most commonly used Agile framework. The core components of SCRUM include roles like Product Owner and Scrum Master, ceremonies such as Sprint Planning and Daily Scrum, and artifacts like the Product Backlog and Sprint Backlog. The document outlines the SCRUM process, which involves prioritizing work, committing to sprints, and delivering working software incrementally in short cycles with daily stand-ups and sprint reviews.
This document provides a summary of key concepts from Chapter 4 of the book "Essential Scrum". It describes the Scrum framework, roles, artifacts, and events. The Scrum roles include the Product Owner, Scrum Master, and Development Team. Key artifacts are the Product Backlog and Sprint Backlog. Main events are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. The goal is to help teams self-organize to deliver working software in short cycles through transparency, inspection, and adaptation.
This document provides an overview of Agile and Scrum frameworks. It begins with introductions and then discusses what Agile is, comparing it to the traditional Waterfall model. Key aspects of Scrum like roles, meetings, events and artifacts are explained. The document argues that Agile is not just for software teams and discusses how Atlassian uses Agile to promote innovation through a culture that provides employees freedom, time, collaboration, funding and experimentation.
This document provides an overview of the Scrum framework for agile software development. It defines Scrum and agile development, describes when Scrum is applicable, and outlines the core components of Scrum including values, roles, events, artifacts, and a Scrum board. It also discusses pros and cons of the Scrum framework.
Scrum is an agile framework for managing software delivery that uses iterative sprints to frequently deliver working software. Sprints are short, timed iterations where teams select backlog items to complete. There are ceremonies like sprint planning, daily scrums, sprint reviews, and retrospectives. Roles include the product owner who manages requirements and priorities, the scrum master who removes impediments, and the cross-functional scrum team which self-organizes to deliver working software every sprint.
Scrum is an agile framework that focuses on rapid delivery of working software in short cycles called sprints. It consists of self-organizing cross-functional teams, regular sprints with daily stand-ups, and artifacts like a product backlog, sprint backlog, and burn-down charts. The process involves sprint planning, daily scrums, sprint reviews, and retrospectives. Scrum roles include the product owner who prioritizes the backlog, the scrum master who facilitates the process, and the development team.
Scrum is an agile software development framework that focuses on self-organizing cross-functional teams, sprints of work lasting 2-4 weeks, daily stand-up meetings, and empirical process control. The key roles are the Product Owner who prioritizes features, the Scrum Master who facilitates the process, and the self-organizing Development Team. Scrum uses sprints, daily scrums, sprint planning meetings, sprint reviews, and retrospectives to deliver working software frequently in an iterative and incremental fashion.
Scrum is an agile software development framework that focuses on self-organizing cross-functional teams, sprints of work lasting 2-4 weeks, daily stand-up meetings, and artifacts like a product backlog, sprint backlog, and burndown chart. The process involves sprints where teams work through a prioritized backlog, daily scrums for status updates, and sprint reviews and retrospectives at the end of each iteration to inspect work and improve processes.
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 is an agile framework for managing projects, originally used for software development. It uses short development cycles called sprints that usually last 2-4 weeks, within which self-organizing teams focus on delivering working software. Each sprint involves planning, daily standups, and a sprint review and retrospective. The product owner prioritizes features in the backlog and the team works through them in sprints while the Scrum master facilitates the process.
This document provides an overview of Agile and the Scrum framework. It describes the origins of the Agile Manifesto and how Scrum aligns with Agile values. The key aspects of Scrum covered include the framework, theory, values, artifacts, events, roles and scaling. Scrum is presented as an iterative approach using short cycles (sprints) to manage complex work with feedback to continually improve the product.
This document provides an overview of Scrum methodology. It defines Scrum as an agile framework that can help address complex problems and deliver high value products. The document outlines Scrum roles like Product Owner and Scrum Master. It also describes Scrum artifacts like Product Backlog and Sprint Backlog and events like the Daily Scrum. Finally, it provides a high-level overview of the Scrum process where a product backlog is created, sprints are planned and executed, and work is reviewed and improved upon iteratively until the product is complete.
The document provides an overview of agile software development using the SCRUM framework and planning poker estimation technique. It describes the key elements of SCRUM including roles like the product owner and scrum master, events like sprint planning and daily standups, and artifacts like the product and sprint backlogs. It also explains planning poker as a consensus-based estimation method where the team discusses user stories and privately selects story point cards to estimate them before revealing and reconciling estimates. The document includes an example planning poker workshop for estimating user stories for an online survey application.
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.
Scrum is an agile framework for managing projects developed by Jeff Sutherland in 1993 based on earlier work. It uses short "sprints" to iteratively develop work items prioritized in a backlog. Key roles include the Product Owner who prioritizes the backlog, the Scrum Master who facilitates the process, and the cross-functional Scrum Team. Each sprint involves planning, daily stand-ups, development, review, and retrospective. The process is intended to be flexible and transparent compared to traditional sequential models like waterfall.
The document provides an overview of the Scrum model for agile software development. Scrum divides projects into short sprints of 2-4 weeks to focus development. It utilizes daily stand-up meetings, sprint planning and reviews, and retrospectives. Key roles include the product owner who prioritizes the backlog, the scrum master who facilitates the process, and the cross-functional development team. Scrum aims to provide structure while allowing for flexibility, feedback and adapting to changes.
The document provides an overview of agile scrum testing methodology. It describes agile testing as testing practices that follow the agile manifesto and treat development as the customer of testing. It then outlines the key aspects of scrum testing including product backlogs, sprints, daily standup meetings, sprint planning and retrospectives. It also discusses the proposed scrum testing process of identifying test scenarios, writing test cases per sprint, delayed execution, and inclusion of defects in the product backlog.
Software Development Guide To Accelerate PerformanceZaid Shabbir
Scrum is the most widely used framework across all software and business industries. By following complete scrum framework you can improve the quality product deliver in more adaptive way.
Slides contents content guidelines related to scrum framework and how some one become a certified scrum master. Slides elaborate scrum framework by using user friendly diagrams and bulleted points. After grasping the slides any one can easily pass certified scrum examination.
I am sure you will enjoy the contents and its really helpful to become a certified scrum practitioner.
Similar to Scrum 101 Brownbag: Intro to Scrum (20)
Carrer goals.pptx and their importance in real lifeartemacademy2
Career goals serve as a roadmap for individuals, guiding them toward achieving long-term professional aspirations and personal fulfillment. Establishing clear career goals enables professionals to focus their efforts on developing specific skills, gaining relevant experience, and making strategic decisions that align with their desired career trajectory. By setting both short-term and long-term objectives, individuals can systematically track their progress, make necessary adjustments, and stay motivated. Short-term goals often include acquiring new qualifications, mastering particular competencies, or securing a specific role, while long-term goals might encompass reaching executive positions, becoming industry experts, or launching entrepreneurial ventures.
Moreover, having well-defined career goals fosters a sense of purpose and direction, enhancing job satisfaction and overall productivity. It encourages continuous learning and adaptation, as professionals remain attuned to industry trends and evolving job market demands. Career goals also facilitate better time management and resource allocation, as individuals prioritize tasks and opportunities that advance their professional growth. In addition, articulating career goals can aid in networking and mentorship, as it allows individuals to communicate their aspirations clearly to potential mentors, colleagues, and employers, thereby opening doors to valuable guidance and support. Ultimately, career goals are integral to personal and professional development, driving individuals toward sustained success and fulfillment in their chosen fields.
This presentation by Professor Giuseppe Colangelo, Jean Monnet Professor of European Innovation Policy, was made during the discussion “The Intersection between Competition and Data Privacy” held at the 143rd meeting of the OECD Competition Committee on 13 June 2024. More papers and presentations on the topic can be found at oe.cd/ibcdp.
This presentation was uploaded with the author’s consent.
Collapsing Narratives: Exploring Non-Linearity • a micro report by Rosie WellsRosie Wells
Insight: In a landscape where traditional narrative structures are giving way to fragmented and non-linear forms of storytelling, there lies immense potential for creativity and exploration.
'Collapsing Narratives: Exploring Non-Linearity' is a micro report from Rosie Wells.
Rosie Wells is an Arts & Cultural Strategist uniquely positioned at the intersection of grassroots and mainstream storytelling.
Their work is focused on developing meaningful and lasting connections that can drive social change.
Please download this presentation to enjoy the hyperlinks!
This presentation by OECD, OECD Secretariat, was made during the discussion “Pro-competitive Industrial Policy” held at the 143rd meeting of the OECD Competition Committee on 12 June 2024. More papers and presentations on the topic can be found at oe.cd/pcip.
This presentation was uploaded with the author’s consent.
This presentation by Katharine Kemp, Associate Professor at the Faculty of Law & Justice at UNSW Sydney, was made during the discussion “The Intersection between Competition and Data Privacy” held at the 143rd meeting of the OECD Competition Committee on 13 June 2024. More papers and presentations on the topic can be found at oe.cd/ibcdp.
This presentation was uploaded with the author’s consent.
This presentation by Professor Alex Robson, Deputy Chair of Australia’s Productivity Commission, was made during the discussion “Competition and Regulation in Professions and Occupations” held at the 77th meeting of the OECD Working Party No. 2 on Competition and Regulation on 10 June 2024. More papers and presentations on the topic can be found at oe.cd/crps.
This presentation was uploaded with the author’s consent.
The importance of sustainable and efficient computational practices in artificial intelligence (AI) and deep learning has become increasingly critical. This webinar focuses on the intersection of sustainability and AI, highlighting the significance of energy-efficient deep learning, innovative randomization techniques in neural networks, the potential of reservoir computing, and the cutting-edge realm of neuromorphic computing. This webinar aims to connect theoretical knowledge with practical applications and provide insights into how these innovative approaches can lead to more robust, efficient, and environmentally conscious AI systems.
Webinar Speaker: Prof. Claudio Gallicchio, Assistant Professor, University of Pisa
Claudio Gallicchio is an Assistant Professor at the Department of Computer Science of the University of Pisa, Italy. His research involves merging concepts from Deep Learning, Dynamical Systems, and Randomized Neural Systems, and he has co-authored over 100 scientific publications on the subject. He is the founder of the IEEE CIS Task Force on Reservoir Computing, and the co-founder and chair of the IEEE Task Force on Randomization-based Neural Networks and Learning Systems. He is an associate editor of IEEE Transactions on Neural Networks and Learning Systems (TNNLS).
This presentation by Juraj Čorba, Chair of OECD Working Party on Artificial Intelligence Governance (AIGO), was made during the discussion “Artificial Intelligence, Data and Competition” held at the 143rd meeting of the OECD Competition Committee on 12 June 2024. More papers and presentations on the topic can be found at oe.cd/aicomp.
This presentation was uploaded with the author’s consent.
This presentation by OECD, OECD Secretariat, was made during the discussion “Artificial Intelligence, Data and Competition” held at the 143rd meeting of the OECD Competition Committee on 12 June 2024. More papers and presentations on the topic can be found at oe.cd/aicomp.
This presentation was uploaded with the author’s consent.
XP 2024 presentation: A New Look to Leadershipsamililja
Presentation slides from XP2024 conference, Bolzano IT. The slides describe a new view to leadership and combines it with anthro-complexity (aka cynefin).
This presentation by OECD, OECD Secretariat, was made during the discussion “The Intersection between Competition and Data Privacy” held at the 143rd meeting of the OECD Competition Committee on 13 June 2024. More papers and presentations on the topic can be found at oe.cd/ibcdp.
This presentation was uploaded with the author’s consent.
This presentation by Tim Capel, Director of the UK Information Commissioner’s Office Legal Service, was made during the discussion “The Intersection between Competition and Data Privacy” held at the 143rd meeting of the OECD Competition Committee on 13 June 2024. More papers and presentations on the topic can be found at oe.cd/ibcdp.
This presentation was uploaded with the author’s consent.
The remarkable life of Sir Mokshagundam Visvesvaraya.pptx
Scrum 101 Brownbag: Intro to Scrum
1. Scrum 101 Brownbag:
Introduction to Scrum
Latesha Goodman
August 9, 2019
This presentation is for educational purposes only.
Any copyrighted material used herein this presentation is fair use.
2. About Me
• My name is Latesha Goodman, I am certified
consultant with more than six years of experience
supporting IT projects.
• After working on numerous government projects, I
decided to pursue a certification in Agile.
• In May, I earned my Certified Scrum Master (CSM)
certificate--which brings us to today’s brown bag.
• The following sections will give you a basic
understanding of Scrum’s principles and hopefully
inspire you to learn more.
• Connect with me on LinkedIn:
https://www.linkedin.com/in/lateshaagoodman/
4. Scrum's History
1986
Hirotaka Takeuchi and Ikujiro Nonaka
introduced the term Scrum in their
HBR article, “New New Product
Development Game”.
1993
Jeff Sutherland introduced Scrum at
his job Easel Corporation using the
study by Takeuchi and Nonaka.
1995
Jeff Sutherland and Ken Schwaber
jointly presented Scrum as a formal
process at the OOPSLA.
2001
Sutherland, Schwaber, and other
scrum thinkers joined forces to create
the Agile Manifesto.
2010
Sutherland and Schwaber
published the Scrum Guide.
10. Scrum Team: Product Owner
Responsibilities include
- One person, not a committee.
- Creating ordered list for the
Product Backlog.
- Ensuring that the Product Backlog
shows what the Scrum Team will
work on next.
- Determining Release Dates.
11. Scrum Team: Development Team
Responsibilities include
- Self-organizing into a team of 3-7
professionals.
- Turning Product Backlog into
Increments.
- Delivering a potentially releasable
Increment of "Done" product at the
end of each Sprint.
12. Scrum Team: Scrum Master
Responsibilities include
- Servant leader for the Scrum Team.
- Finding techniques for effective
Product Backlog management.
- Facilitating Scrum events as
requested or needed.
14. Sprint Planning and Daily Scrums
SprintPlanning •Scrum Team meets to
discuss the work to be
done in a Sprint.
•Crafts a Sprint Goal to be
met during the Sprint.
•Time-boxed to a
maximum of eight (8)
hours for a one-month
Sprint or 2 hours/week.
DailyScrums
•Development Team
meets daily to inspect
progress toward Sprint
Goal.
•Development Team
plans work for the next
24 hours.
•Daily Scrums are 15-
minute time-boxed
events.
16. Sprint Review and Sprint Retrospective
SprintReview
• Scrum Team and key
stakeholders
collaborate about
what was done in
the Sprint.
• Event held at the
end of the Sprint.
• Maximum four (4)
hour meeting for
one-month Sprints.
SprintRetrospective
• Occurs after the Sprint
Review and prior to the
next Sprint Planning.
• Allows team to inspect
itself and make
actionable commitments.
• Maximum three (3) hour
meeting for one-month
Sprints.
18. Product Backlog and Sprint Backlog
ProductBacklog
Lists the features,
functions, requirements,
enhancements, and fixes
to be made in future
releases.
It is dynamic and
constantly changing as the
product changes.
Prioritized by the Product
Owner.
SprintBacklog
Contains a set of Product
Backlog items selected for
the Sprint and a plan for
delivering the product
Increment and achieving
the Sprint Goal.
Only Development Team can
change its Sprint Backlog
during a Sprint.
25. Scrum
Resources
Books, Blogs, Games, and Tools
• 12 Agile Manifesto
Principles – Website
• Agile: An Umbrella View
(Blog Post) (Fig. 1)
• Agile in an Hour
Bernie Maloney –
Presentation
• Agile NOVA Meetup
• Scrum.org and Scrum Co-
Founder
Ken Schwaber
(Fig.4 and Fig.7)
• Scrum Games -
TastyCupcakes
• Scrum PM Tools
• Atlassian Jira (Fig. 11)
• Asana (Free Tool)
• GitScrum
• Mountain Goat Tools
(Fig 10 and Fig. 12)
• Rally
• Taiga
• Art of Doing Twice the Work
in Half the Time (Book)
• Essential Scrum (Book)
• PowerPoint History
Template (Slide 4)
• Planning Poker (Game)
• Scrum Alliance Website
• Scrum Guides – Website
• Scrum Inc. –
Scrum Co-Founder
Jeff Sutherland (Fig.9)
• The Scrum Fieldbook (Book)
• Scrum Master Toolbox
Podcast
• Visual Paradigm
(Blog Post)
• Washington DC Scrum User
Group Meetup
Scrum Resources
Editor's Notes
LG Presenter Notes
Show this slide during attendance call, so viewers can learn a little about me.
LG Presenter Notes
Show this slide during attendance call, so viewers can see what this brown bag covers up front.
LG Presenter Notes
1 - 1986 - Scrum has been around for more than 30 years, the first appeared in Hirotaka Takeuchi and Ikujiro Nonaka’s Harvard Business Review’s article.
2 - 1993 - In his book, the “Art of Doing Twice the Work in Half the Time” Jeff Sutherland discussed using Takeuchi and Nonaka scrum principles to implement Scrum practices at his job.
3 -1995 - This led to Sutherland and Ken Schwaber collaborating to present Scrum as a formal process for software development at Object-oriented Programming, Systems, Languages, and Applications research conference.
4 - 2001 – Sutherland and Schwaber along with other Scrum practitioners developed the Agile Manifesto.
LG Presenter Notes
1 – Scrum falls under the Agile umbrella it is not synonymous with Agile.
As you can see Scrum is just one of many ways for a team be agile.
Agile uses incremental, iterative work sequences that are known as sprints.
Sprints allows teams to continuously align a delivered product that reflects the changing requirements needs of a client.
2 – Waterfall vs Agile Approach
Requirements (Documentation Heavy)->Design (Documentation Heavy)->Implementation (Unverified Code)->Verification (Testing/Product Ready SW)->Production (Fully Deployed SW)
LG Presenter Notes:
1a - Scrum Values - Scrum is framework that is built on the five values shown in Figure 2.
1b - Scrum Values Definitions
Commitment: People personally commit to achieving the goals of the Scrum Team.
Courage: Scrum Team members have the courage to do the right thing and work on tough problems.
Focus: Everyone focuses on the work of the Sprint and the goals of the Scrum Team.
Openness: The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work.
Respect: Scrum Team members respect each other to be capable, independent people
2 – Empirical Process
Scrum implements an empirical process where progress is based on unknowns and experimentation instead of upfront planning and knowns. “Learn as we grow approach”
The three pillars of empiricism is shown in Figure 3.
LG Presenter Notes
1 – Figure 4 shows the Scrum is a framework that uses cross-functional teams to address complex adaptive problems, while productively and creatively delivering products of the highest possible value. (Reference: The Scrum Guide)
Bottom Line: The business / customer sees real progress and makes decisions based on working software.
There are no paper reports, updated Gantt charts, or PowerPoints.
And, the Development Team does not waste time building features the customer in the end does not want (anymore).
2 – Sprint Duration
A Sprint is a time-box of month or less during which a potentially releasable product Increment is created.
Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened.
Excluding any of these events results in reduced transparency and is a lost formal opportunity to inspect and adapt.
LG Presenter Notes
1 – The following sections explains Scrum’s roles, events and artifacts in more detail.
LG Presenter Notes
1 - Scrum framework in Figure 5 consists of the following roles:
Scrum Master
Product Owner
Development Team
2 - The following slides provide the responsibilities for each role.
Reader note - Orange represents the Scrum Team in Figure 5.
LG Presenter Notes
As a Product Owner:
You ensure the Product Backlog is visible, transparent, and clear to all.
Represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner.
Funnel all work requests intended for Dev. Team into the ordered Product Backlog by making trade-offs between various items.
Explain what has been “Done” and what has not been “Done” during Sprint Review meeting.
Use the Velocity and the Burndown Chart to view Team’s progress toward a successful sprint release.
You can cancel the Sprint.
Reader Note – Orange represents scrum team in the Scrum Framework.
LG Presenter Notes
As the Development Team
You provide estimates for delivering a “Done” product.
You use the Scrum Board tool to make the tasks on the Sprint Backlog visible for all team members.
LG Presenter Notes
As a Scrum Master
Helping everyone understand Scrum theory, practices, rules, and values.
Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value;
LG Presenter Notes
Figure 6 shows the formal events designed to enable transparency and inspection:
1 – Scrum Events (Ceremonies)
Sprint Planning
Daily Scrums
Sprint Review
Sprint Retrospective
2 – These four Scrum events create regularity and reduce the need for meetings not defined in Scrum.
Reader Note - Gray represents the following Scrum Events (Ceremonies) in in Figure 6.
LG Presenter Notes
During a Sprint Planning the Scrum Team answers the following questions:
What can be delivered in the Increment resulting from the upcoming Sprint?
How will the work needed to deliver the Increment be achieved?
When will the work be done?
A Sprint Goal is an output of Sprint Planning:
Dev. Team determines what can be done this Sprint.
Product Owner discusses the objective the Sprint should achieve, this is called a Sprint Goal.
Daily Scrums:
Dev. Team uses Daily Scrums to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog.
Dev. Team can use the following questions to structure the Daily Scrum:
What did I do yesterday that helped the Dev. Team meet the Sprint Goal?
What will I do today to help the Dev. Team meet the Sprint Goal?
Do I see any impediment that prevents me or the Dev. Team from meeting the Sprint Goal?
LG Presenter Notes
Retrospective Commitments: Scrum Team talks about what it is currently doing that works well, and solicit someideas about what it should be doing more or less of.
LG Presenter Notes
During a Sprint Review:
Product Owner explains what has been “Done” and what has not been “Done” during Sprint Review meeting.
Dev. Team demonstrates the work that it has been “Done” and answers stakeholders questions about the Increment.
The entire group including key stakeholders discuss what to do next, so that the Sprint Review provides valuable input into subsequent Sprint Planning.
The output of the Sprint Review is a revised Product Backlog.
During a Sprint Retrospective:
Offers Scrum Team opportunity to inspect how the last Sprint went with regards to people, relationships, process and tools.
LG Presenter Notes – Purple represents Scrum Artifacts in Figure 7.
Figure 8 provides the three Artifacts in Scrum.
Product Backlog: List of sponsor’s requirements prioritized by Product Owner.
Sprint Backlog: Contains what the Development Team will be completing during the Sprint.
Increment (Most Viable Product): Releasable product, feature, code delivered at the end of Sprint.
LG Presenter Notes
1 - Product Owner is responsible for refining (or grooming) the Product Backlog.
Product Backlog Refinement is the act of adding detail, estimates, and order to items in the Product Backlog.
2 - Sprint Backlog contains:
What the Development Team will be completing during the sprint.
It includes at least one (1) high priority process improvement identified in the previous Retrospective meeting
3 – Figure 9
Illustrates how the Product Backlog and Sprint Backlog are ordered during a typical Sprint.
Reader Note: Purple represents scrum artifacts in Scrum Framework.
LG Presenter Notes
1 – What is Velocity in Scrum?
Velocity is calculated at the end of the Sprint by totaling the Points for all fully completed User Stories.
Points from partially-completed or incomplete stories are not counted in calculating velocity.
Velocity is a measure of the amount of work a Scrum Team can tackle during a single Sprint.
2 – How does the Dev. Team know its Velocity?
The Development creates estimates for every item in the Sprint Backlog.
Common estimating methods include numeric sizing (1 through 10), t-shirt sizes (XS, S, M, L, XL, XXL, XXXL) or the Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, 34, etc.).
2a – Why is Velocity Important?
The Development Team uses velocity from previous sprints to estimate how much work it can tackle in future sprints.
2b – Velocity helps Product Owner with Ordering Product Backlog Items
Higher ordered Product Backlog items are usually clearer and more detailed than lower ordered ones. More precise estimates are made based on the greater clarity and increased detail; the lower the order, the less detail.
LG Presenter Notes
1 – What is a Scrum Board?
The Sprint Board is a visual tool used to manage the Sprint Backlog and is visible to all team members at all times. The Scrum Board is what is going on in this particular sprint, with user stories broken down into smaller, technical, descriptions for the team to work on.
The Development Team uses a Scrum Board to show the items that need to be completed for the current Sprint.
2 – Types of Scrum Boards
As you can see from a quick Google Search, Scrum Boards come in many forms and include various categories. However, the traditional scrum include: To-Do column, Work in Progress column, and Done column.
LG Presenter Notes
1- Jira and other Agile Tools
Figure 10 illustrates a Scrum Board using Jira.
2 – I provide a list of Agile tools on Slide 24.
LG Presenter Notes
In addition to Scrum Boards, the Development Team uses a Sprint Burndown Chart to show the team’s progress in completing work during the sprint.
1 – How to use Sprint Burndown Chart?
In the Daily Scrum the Development Team updates the Sprint Burndown Chart and plots the remaining work of the day.
The Product Owner uses the Sprint Burndown Chart for release planning and reporting.
LG Presenter Notes – Purple represents Scrum Artifacts in Scrum Framework.
Previous Sprints Increments: Each Increment is additive to all prior Increments and thoroughly tested, ensuring that all Increments work together.
Increment (Most Viable Product):
The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current definition of "Done".
If the definition of "Done" for an increment is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum.
If "Done" for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of "Done" appropriate for the product. If there are multiple Scrum Teams working on the system or product release, the Development Teams on all the Scrum Teams must mutually define the definition of "Done".
LG Presenter Notes:
Ask peers if they have any questions, if not then do a pop quiz to ensure they understand the material.
LG Presenter Notes:
There are various Agile tools to assist the Scrum Team with conducting Sprints including Atlassian Jira https://www.atlassian.com/agile/tutorials/sprints
Dev. Teams use Planning Poker / Scrum Poker during the estimation process https://www.scrum-institute.org/Effort_Estimations_Planning_Poker.php