The document provides an overview of Scrum, an agile framework for project management. It discusses the core components of Scrum including roles, artifacts, ceremonies, and values. The key roles are Product Owner, Scrum Master, and self-organizing Team. Projects progress through a series of sprints where work is pulled from the prioritized Product Backlog to the Sprint Backlog and completed work is demonstrated at Sprint Review meetings. Daily stand-up meetings and retrospective meetings aid in transparency and process improvement.
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
The document provides an overview of the Agile Scrum process. It describes traditional waterfall methodologies and how Agile and Scrum differ by being more iterative, collaborative with stakeholders, and able to adapt to changes. The Scrum framework involves three main roles - Product Owner, Scrum Master, and Team. It also describes the four main Scrum ceremonies - Sprint Planning Meeting, Daily Standup, Sprint Review, and Sprint Retrospective - as well as the typical artifacts like Product Backlog and Sprint Backlog.
Scrum is a framework for managing complex product development that uses self-organizing cross-functional teams, short development iterations called sprints, and regular inspection and adaptation. Key roles include the Product Owner who manages the product backlog, the Scrum Master who facilitates the process, and the Scrum Team who does the work. Sprints involve planning, daily stand-ups, reviews, and retrospectives to continuously improve. The product backlog, sprint backlog, and burn down charts are used to track progress.
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 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 for managing product development. It involves self-organizing cross-functional teams who break their work into actions that can be completed within timeboxed iterations, called sprints, no longer than one month to build usable software. Key roles include the Product Owner who manages priorities from stakeholders, the Scrum Master who ensures Scrum is followed, and the Development Team. Artifacts include the Product Backlog of features, Sprint Backlog of tasks, and increments of functionality delivered each sprint. The process consists of sprints, daily stand-ups, sprint planning and review meetings, and retrospectives for continuous improvement.
The document discusses Scrum, an agile framework for managing product development. It describes Scrum roles like Product Owner and Scrum Master. Key Scrum events are also outlined such as sprint planning, daily standups, sprint demos and retrospectives. Benefits of Scrum mentioned are rapid development, transparency and embracing change.
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.
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
The document provides an overview of the Agile Scrum process. It describes traditional waterfall methodologies and how Agile and Scrum differ by being more iterative, collaborative with stakeholders, and able to adapt to changes. The Scrum framework involves three main roles - Product Owner, Scrum Master, and Team. It also describes the four main Scrum ceremonies - Sprint Planning Meeting, Daily Standup, Sprint Review, and Sprint Retrospective - as well as the typical artifacts like Product Backlog and Sprint Backlog.
Scrum is a framework for managing complex product development that uses self-organizing cross-functional teams, short development iterations called sprints, and regular inspection and adaptation. Key roles include the Product Owner who manages the product backlog, the Scrum Master who facilitates the process, and the Scrum Team who does the work. Sprints involve planning, daily stand-ups, reviews, and retrospectives to continuously improve. The product backlog, sprint backlog, and burn down charts are used to track progress.
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 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 for managing product development. It involves self-organizing cross-functional teams who break their work into actions that can be completed within timeboxed iterations, called sprints, no longer than one month to build usable software. Key roles include the Product Owner who manages priorities from stakeholders, the Scrum Master who ensures Scrum is followed, and the Development Team. Artifacts include the Product Backlog of features, Sprint Backlog of tasks, and increments of functionality delivered each sprint. The process consists of sprints, daily stand-ups, sprint planning and review meetings, and retrospectives for continuous improvement.
The document discusses Scrum, an agile framework for managing product development. It describes Scrum roles like Product Owner and Scrum Master. Key Scrum events are also outlined such as sprint planning, daily standups, sprint demos and retrospectives. Benefits of Scrum mentioned are rapid development, transparency and embracing change.
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.
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.
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.
This is my presentation from the 17th Agile Greece meetup. The event was a series of lightning talks about the events of Scrum.
My presentations has a collection of bad and good practices when implementing a Daily Scrum or Daily standup at Scrum.
http://www.meetup.com/Agile-Greece/
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.
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
UPDATE VERSION : https://www.slideshare.net/pmengal/scrum-in-ten-slides-v20-2018
This document provides an overview of different software development processes including the waterfall model, iterative model, Rational Unified Process (RUP), and Agile Development Process (ADP). It describes the key aspects of each process including phases, roles, artifacts, and ceremonies. Specifically, it provides detailed explanations of Scrum, an agile methodology, including Scrum roles like Product Owner and Scrum Master, ceremonies like the Daily Scrum, and artifacts like the Product Backlog and Sprint Backlog. The document concludes with references for further information.
This document provides an overview of Agile methodology and Scrum framework. It defines key Agile concepts like iterations called sprints and artifacts like product backlog, sprint backlog, and product increment. It describes Scrum roles of product owner, Scrum master, and team. It outlines Scrum activities like sprint planning, daily scrum, sprint review, and retrospective. Finally, it discusses tools like task boards and burn down charts used to provide transparency and track progress.
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
Scrum is an agile framework that focuses on delivering working software in short iterations called sprints, typically 2-4 weeks. Self-organizing teams work to complete items from a prioritized backlog list. Daily stand-up meetings and sprint planning, review, and retrospective ceremonies provide transparency and opportunities to inspect and adapt the process as needed. The framework aims to rapidly deliver business value through flexible and collaborative teamwork.
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
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.
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
This document provides an introduction to Scrum, an agile framework for project management. It discusses the principles of agile development and Scrum, including self-organizing cross-functional teams, short sprint cycles, daily stand-ups, product backlogs and user stories, estimation techniques, and retrospectives for continuous improvement. The Scrum framework emphasizes empiricism, adaptation, transparency, inspection, and frequent delivery of working software.
What is Scrum?
Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
The Scrum Team
-The Product Owner
-The Development Team
-The Scrum Master
The Scrum Events / Rituals / Ceremonies
-Sprint Planning
-Sprint
-Daily Scrum
-Sprint Review
-Sprint Retrospective
Scrum Artifacts
-The Product BackLog
-The Sprint BackLog
This document provides an overview of the Scrum framework for developing software. Some key points:
- Scrum is an empirical, lightweight framework that helps teams generate value through adaptive solutions to complex problems. It is based on empiricism, lean thinking, and values transparency, inspection, and adaptation.
- Scrum uses events like sprints, daily stand-ups, sprint reviews and retrospectives to inspect and adapt its processes. Sprints are time-boxed periods for delivering increments of work toward a sprint goal.
- Scrum teams are cross-functional and consist of developers, a product owner, and scrum master. The product owner manages the product backlog and maximizes value. The scrum
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 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.
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.
Scrum is an agile software development framework that emphasizes communication, collaboration, and flexibility. It was invented in 1993 to provide a more adaptive approach to project management compared to traditional waterfall models. Scrum uses short development cycles called sprints, daily stand-up meetings, and defined roles like Product Owner and Scrum Master to help self-organizing teams work together to deliver working software incrementally.
Scrum is an agile framework for managing product development that focuses on continuous delivery of working software in short cycles called sprints, typically two weeks or less. Scrum emphasizes self-organizing cross-functional teams and accountability, iterative development and progress transparency through regular inspection of working increments. Key Scrum practices include sprint planning, daily stand-up meetings, sprint reviews, and retrospectives. Scrum can scale to large, complex projects through techniques like Scrum of Scrums.
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.
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.
This is my presentation from the 17th Agile Greece meetup. The event was a series of lightning talks about the events of Scrum.
My presentations has a collection of bad and good practices when implementing a Daily Scrum or Daily standup at Scrum.
http://www.meetup.com/Agile-Greece/
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.
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
UPDATE VERSION : https://www.slideshare.net/pmengal/scrum-in-ten-slides-v20-2018
This document provides an overview of different software development processes including the waterfall model, iterative model, Rational Unified Process (RUP), and Agile Development Process (ADP). It describes the key aspects of each process including phases, roles, artifacts, and ceremonies. Specifically, it provides detailed explanations of Scrum, an agile methodology, including Scrum roles like Product Owner and Scrum Master, ceremonies like the Daily Scrum, and artifacts like the Product Backlog and Sprint Backlog. The document concludes with references for further information.
This document provides an overview of Agile methodology and Scrum framework. It defines key Agile concepts like iterations called sprints and artifacts like product backlog, sprint backlog, and product increment. It describes Scrum roles of product owner, Scrum master, and team. It outlines Scrum activities like sprint planning, daily scrum, sprint review, and retrospective. Finally, it discusses tools like task boards and burn down charts used to provide transparency and track progress.
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
Scrum is an agile framework that focuses on delivering working software in short iterations called sprints, typically 2-4 weeks. Self-organizing teams work to complete items from a prioritized backlog list. Daily stand-up meetings and sprint planning, review, and retrospective ceremonies provide transparency and opportunities to inspect and adapt the process as needed. The framework aims to rapidly deliver business value through flexible and collaborative teamwork.
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
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.
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
This document provides an introduction to Scrum, an agile framework for project management. It discusses the principles of agile development and Scrum, including self-organizing cross-functional teams, short sprint cycles, daily stand-ups, product backlogs and user stories, estimation techniques, and retrospectives for continuous improvement. The Scrum framework emphasizes empiricism, adaptation, transparency, inspection, and frequent delivery of working software.
What is Scrum?
Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
The Scrum Team
-The Product Owner
-The Development Team
-The Scrum Master
The Scrum Events / Rituals / Ceremonies
-Sprint Planning
-Sprint
-Daily Scrum
-Sprint Review
-Sprint Retrospective
Scrum Artifacts
-The Product BackLog
-The Sprint BackLog
This document provides an overview of the Scrum framework for developing software. Some key points:
- Scrum is an empirical, lightweight framework that helps teams generate value through adaptive solutions to complex problems. It is based on empiricism, lean thinking, and values transparency, inspection, and adaptation.
- Scrum uses events like sprints, daily stand-ups, sprint reviews and retrospectives to inspect and adapt its processes. Sprints are time-boxed periods for delivering increments of work toward a sprint goal.
- Scrum teams are cross-functional and consist of developers, a product owner, and scrum master. The product owner manages the product backlog and maximizes value. The scrum
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 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.
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.
Scrum is an agile software development framework that emphasizes communication, collaboration, and flexibility. It was invented in 1993 to provide a more adaptive approach to project management compared to traditional waterfall models. Scrum uses short development cycles called sprints, daily stand-up meetings, and defined roles like Product Owner and Scrum Master to help self-organizing teams work together to deliver working software incrementally.
Scrum is an agile framework for managing product development that focuses on continuous delivery of working software in short cycles called sprints, typically two weeks or less. Scrum emphasizes self-organizing cross-functional teams and accountability, iterative development and progress transparency through regular inspection of working increments. Key Scrum practices include sprint planning, daily stand-up meetings, sprint reviews, and retrospectives. Scrum can scale to large, complex projects through techniques like Scrum of Scrums.
ERP Implementation Using Agile Project Management with Scrumdj1arry
This document discusses using Agile project management and Scrum for ERP implementation. It introduces ERP systems and Agile project management approaches like Scrum. Scrum uses product owners, development teams, and scrum masters along with artifacts like product backlogs and sprints. Key Scrum ceremonies include sprint planning, daily stand-ups, and sprint reviews. Using Scrum for ERP implementation provides benefits like transparency, inspection, adaptation and aligning with Agile values.
The document provides an overview of the waterfall model and agile methodologies for software development projects. It discusses:
- The linear sequential phases of the waterfall model and when it is suitable.
- Issues with the waterfall model like inability to handle changes and lack of testing throughout.
- Benefits of agile like ability to adapt to changes, early delivery of working software, and improved success rates.
- Key aspects of the Scrum agile framework like sprints, daily stand-ups, and product backlogs.
- Differences in how development costs are treated as capital expenditures or operating expenses between waterfall, agile, and cloud-based models.
Updated version at https://www.slideshare.net/GiulioRoggero/kanban-board-82363781
Do you have a team that works on both project and maintenance? Do you need to organize your team activities? Do you have a lot of activities in parallel and the time to market it's a problem? With a Kanban board and an Agile approach you can solve your problems!
Take a look of the animation of the slides to discover how it works.
An Introduction to Scrum: presented at PyTexas 2012Tomo Popovic
This document provides an introduction to Scrum, an agile framework for project management. It defines key Scrum roles like the Product Owner and Scrum Master. Scrum uses short iterations called sprints to incrementally develop working software. Teams self-organize during daily stand-up meetings and track progress using artifacts like the product backlog and sprint backlog. Scrum aims to deliver business value continuously through inspection and adaptation at the end of each sprint.
Agile and Scrum 101 – basics of Agile and Scrum
Scrum in 100 words:
• Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time.
• It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month).
• The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features.
• Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.
In the presentation we discuss the basics of Agile and Scrum, the roles, ceremonies and artifacts. We add from our, from the trenches, lessons learned and better practices.
This document provides an overview of Scrum, an agile process for managing projects. It discusses:
1) Scrum uses short "sprints" (typically 2-4 weeks) where cross-functional teams work to deliver working software. Daily stand-up meetings are held to track progress.
2) Key Scrum roles include the Product Owner who prioritizes features, the Scrum Master who facilitates the process, and the self-organizing team.
3) Ceremonies like sprint planning, reviews, and retrospectives along with artifacts like product and sprint backlogs help manage the process.
This document provides an introduction to the Scrum framework for agile software development. It describes Scrum roles like the Product Owner, Scrum Master, and self-organizing team. It outlines Scrum ceremonies like sprint planning, daily stand-ups, sprint reviews, and retrospectives. It also discusses the product and sprint backlogs and how teams work in sprints to deliver working software increments every 2-4 weeks using the Scrum framework.
This document provides an overview of Agile and Scrum methodologies for software development. It discusses key Agile principles like early delivery, flexibility, and collaboration. Scrum is presented as a framework for Agile development with roles like Product Owner, Scrum Master, and Team. Ceremonies like sprint planning, daily stand-ups, sprint reviews and retrospectives are covered. Artifacts like the product and sprint backlogs are also summarized. Examples of companies using Scrum are provided.
This document provides an overview of Scrum, an agile framework for project management. It describes key Scrum roles like the Product Owner, Scrum Master, and self-organizing team. It outlines common Scrum events like sprint planning, daily stand-ups, sprint reviews, and retrospectives. It also explains main Scrum artifacts like the product backlog, sprint backlog, and burn down charts that are used to track work. The document aims to explain the basic concepts, roles, events, and artifacts that make up the Scrum framework.
Scrum is an agile framework for developing products using short cycles of work called sprints that are used to establish a regular rhythm for work. The key roles in Scrum include the Product Owner who manages the product backlog, the Scrum Master who facilitates the process, and a cross-functional team. The Scrum process involves sprint planning, daily stand-up meetings, sprint reviews, and retrospectives to continuously improve.
Scrum is an agile framework for developing products using short cycles of work called sprints, daily stand-ups, and emphasizing self-organizing cross-functional teams. It originated in the 1990s and focuses on delivering working software frequently in 2-4 week sprints. Key roles include the product owner who prioritizes features, the scrum master who facilitates the process, and the cross-functional team.
This document provides an introduction to the Scrum framework. It describes Scrum as an agile process that focuses on delivering high business value in short iterations called sprints. Key Scrum roles include the Product Owner who prioritizes features, the Scrum Master who facilitates the process, and cross-functional teams. Ceremonies like sprint planning, daily stand-ups, sprint reviews and retrospectives help teams self-organize their work.
Scrum is one of the leading agile software development processes. Over 12,000 project managers have become certified to run Scrum projects . Since its origin on Japanese new product development projects in the 1980s, Scrum has become recognized as one of the best project management frameworks for handling rapidly changing or evolving projects. Especially useful on projects with lots of technology or requirements uncertainty, Scrum is a proven, scalable agile process for managing software projects.
Through lecture, discussion and exercises, this fast-paced tutorial covers the basics of what you need to know to get started with Scrum. You will learn about all key aspects of Scrum including product and sprint backlog, the sprint planning meeting, the sprint review, conducting a sprint retrospective, activities that occur during sprints, measuring and monitoring progress, and scaling Scrum to work with large and distributed teams. Also covered are the roles and responsibilities of the ScrumMaster, the product owner, and the Scrum team.
This session will be equally suited for managers, programmers, testers, product managers and anyone else interested in improving product delivery.
Scrum is a framework for developing complex products and systems. It employs an iterative, incremental approach with three roles - Product Owner, Scrum Master, and Team - and four meetings - Planning, Daily Scrum, Review, and Retrospective. The Product Owner prioritizes items in the Product Backlog and accepts or rejects work results. The cross-functional Team selects and delivers the highest priority backlog items within a Sprint. The Scrum Master helps the Team achieve their goals and shields them from distractions.
The document provides an introduction and overview of Agile Scrum methodology. It describes Scrum as an agile process that focuses on delivering high business value in short iterations through working software. Key Scrum roles include the Product Owner who prioritizes features, the Scrum Master who removes impediments, and cross-functional self-organizing teams. Ceremonies like Sprints, Daily Stand-ups, Sprint Reviews and Retrospectives support iterative development. Product and Sprint Backlogs track work in progress.
This document discusses customizing the Scrum process for a startup company. It describes the author's experience being assigned the Product Owner and Scrum Master roles without previous Scrum experience. The author learned Scrum and implemented it in their own way for their company. The document then provides an overview of key Scrum concepts like sprints, product backlogs, daily standups, sprint reviews, and retrospectives. It also discusses tools that can be used to support the Scrum process.
The document discusses Scrum, an agile framework for managing complex projects. It describes Scrum's core components like sprints, roles, artifacts, and events. Sprints are short, timed iterations where self-organizing teams work on prioritized backlog items to create shippable increments. Key roles include the Product Owner who prioritizes features, and the Scrum Master who coaches the team. Artifacts include the Product and Sprint Backlogs and shippable increments. Events help the team inspect and adapt their process through planning, daily check-ins, reviews, and retrospectives. Many large companies have adopted Scrum to deliver working software frequently in response to changing requirements.
This document provides an overview of Scrum, an agile framework for project management. It discusses key Scrum concepts like sprints, daily stand-ups, product backlogs, and roles. Scrum aims to be more flexible than traditional "relay race" development by having cross-functional teams work on tasks simultaneously in sprints of 1-4 weeks to iteratively develop working software.
Scrum is an agile framework that focuses on rapid delivery of working software in short cycles called sprints. It involves self-organizing cross-functional teams, prioritized backlogs and artifacts like product backlogs, sprint backlogs and increments. Key roles include the product owner who prioritizes features, the development team who work on delivering features and the scrum master who facilitates the process. Ceremonies like sprint planning, daily standups, sprint reviews and retrospectives help ensure transparency and process improvement.
The document is a collection of manifestos from different domains, including software development, business analysis, testing, and more. Each manifesto presents a set of values or principles for that domain, contrasting items valued more on the left side versus those valued less on the right side. The manifestos range from well-known ones like the Agile Manifesto to more specialized ones focused on topics like software craftsmanship, business rules, lean product management, and testing.
A 2 hour presentation of Jeff Patton's concept User Story Mapping, which helps agile projects to sort out the requirements and greatly enhances the user understanding and user experience.
This document discusses 10 tools to become more lean and agile in software development. It outlines various lean concepts like eliminating waste (muda), uneven workflow (mura), and overburdened processes (muri). Specific tools covered include daily stand-ups, visualization of work, regular retrospectives, limiting work-in-progress, real options planning, rolling wave planning, and the Pomodoro technique. The overall message is that adopting these lean and agile tools can help organizations continuously improve, focus on delivering value, and eliminate inefficiencies in their development processes.
This document discusses how organizations can unleash innovation through being agile. It argues that innovation requires stimuli, communication through meetings, building trust to overcome fears, providing time and safe havens for experimentation and learning from failures. True innovation emerges from cross-functional collaboration, open communication, embracing uncertainty, and continually adapting processes through iterations. Being agile can help organizations establish these conditions for innovation to thrive.
Lean management focuses on maximizing customer value while minimizing waste. It draws from concepts like the Toyota Production System and Total Quality Management to optimize processes through continuous improvement. The core principles of lean include transparency and visualization of workflows, respecting people, empowering employees, removing waste, and optimizing flow and resources through systems thinking. The goal is to shorten lead times and increase quality by eliminating unnecessary steps and unevenness in production.
1-2 hour introduction to Agile that I made for students at Heriot-Watts University Dubai Campus. Updated it after doing it at UAE University in Al Ain, added a few slides.
This document provides a specification for a use case, including a short description, list of actors, activity diagram, included/extended use cases, preconditions, main and alternative flows, postconditions, quality attributes, scenarios, and references. It specifies the key elements of a use case to describe a process or function within a project.
How to run a great requirements workshop with Use CasesAndreas Hägglund
The slideshare tells how to run a great requirements workshop with use cases as well as defines the basic terms for doing use cases but most important - It tells how to do the teenage use case disco dance!
A short presentation containing proven, quick and easy techniques for getting a meeting, workshop, facilitation or modeling session moving when it's stuck!
Use Cases are not enough to specify requirements. You need to supplement them with other models and documents. This is my list of models to supplement a use case.
By Andreas Hägglund
Feel free to use the presentation when you give me credit.
http://se.linkedin.com/in/andreashagglund
http://www.systemvaruhuset.net
http://www.systemvaruhuset.se
Storytelling is an incredibly valuable tool to share data and information. To get the most impact from stories there are a number of key ingredients. These are based on science and human nature. Using these elements in a story you can deliver information impactfully, ensure action and drive change.
The Most Inspiring Entrepreneurs to Follow in 2024.pdfthesiliconleaders
In a world where the potential of youth innovation remains vastly untouched, there emerges a guiding light in the form of Norm Goldstein, the Founder and CEO of EduNetwork Partners. His dedication to this cause has earned him recognition as a Congressional Leadership Award recipient.
The APCO Geopolitical Radar - Q3 2024 The Global Operating Environment for Bu...APCO
The Radar reflects input from APCO’s teams located around the world. It distils a host of interconnected events and trends into insights to inform operational and strategic decisions. Issues covered in this edition include:
Unveiling the Dynamic Personalities, Key Dates, and Horoscope Insights: Gemin...my Pandit
Explore the fascinating world of the Gemini Zodiac Sign. Discover the unique personality traits, key dates, and horoscope insights of Gemini individuals. Learn how their sociable, communicative nature and boundless curiosity make them the dynamic explorers of the zodiac. Dive into the duality of the Gemini sign and understand their intellectual and adventurous spirit.
Anny Serafina Love - Letter of Recommendation by Kellen Harkins, MS.AnnySerafinaLove
This letter, written by Kellen Harkins, Course Director at Full Sail University, commends Anny Love's exemplary performance in the Video Sharing Platforms class. It highlights her dedication, willingness to challenge herself, and exceptional skills in production, editing, and marketing across various video platforms like YouTube, TikTok, and Instagram.
Discover timeless style with the 2022 Vintage Roman Numerals Men's Ring. Crafted from premium stainless steel, this 6mm wide ring embodies elegance and durability. Perfect as a gift, it seamlessly blends classic Roman numeral detailing with modern sophistication, making it an ideal accessory for any occasion.
https://rb.gy/usj1a2
Starting a business is like embarking on an unpredictable adventure. It’s a journey filled with highs and lows, victories and defeats. But what if I told you that those setbacks and failures could be the very stepping stones that lead you to fortune? Let’s explore how resilience, adaptability, and strategic thinking can transform adversity into opportunity.
Best practices for project execution and deliveryCLIVE MINCHIN
A select set of project management best practices to keep your project on-track, on-cost and aligned to scope. Many firms have don't have the necessary skills, diligence, methods and oversight of their projects; this leads to slippage, higher costs and longer timeframes. Often firms have a history of projects that simply failed to move the needle. These best practices will help your firm avoid these pitfalls but they require fortitude to apply.
How are Lilac French Bulldogs Beauty Charming the World and Capturing Hearts....Lacey Max
“After being the most listed dog breed in the United States for 31
years in a row, the Labrador Retriever has dropped to second place
in the American Kennel Club's annual survey of the country's most
popular canines. The French Bulldog is the new top dog in the
United States as of 2022. The stylish puppy has ascended the
rankings in rapid time despite having health concerns and limited
color choices.”
Top mailing list providers in the USA.pptxJeremyPeirce1
Discover the top mailing list providers in the USA, offering targeted lists, segmentation, and analytics to optimize your marketing campaigns and drive engagement.
4. Two big events in 1986...
“The… ’relay race’ approach to product
development…may conflict with the goals of
maximum speed and flexibility. Instead a
holistic or ’rugby’ approach — where a team
tries to go the distance as a unit, passing the
ball back and forth—may better serve today’s
competitive requirements.”
Hirotaka Takeuchi and Ikujiro Nonaka, “The
New New Product Development Game”,
Harvard Business Review, January 1986.
11K
5. • Scrum is an agile process that allows us to focus on delivering
the highest business value in the shortest time using empirical
process control.
• It allows us to rapidly and repeatedly inspect actual working
software (every two weeks to one month).
• The business sets the priorities. Teams self-organize to
determine the best way to deliver the highest priority features.
• Every two weeks to a month anyone can see real working
software and decide to release it as is or continue to enhance
it for another sprint.
Scrum in 100 words
11K
6. History of Scrum
● Pre 1986 Lean & Agile Practices
● 1986 The New New Product Development Game published
● 1993 Jeff Sutherland - Easel Corp, Ken Schwaber – ADM
● 1995 OOPSLA Conference
● 1999 Scrum patterns in PLOPD4 published
● 2001 Agile Manifesto signed
● 2001 Agile Software Development with Scrum published
● 2002 Scrum Alliance founded
● 2004 Agile Project Management with Scrum published
● 2009 Scrum.org founded
● 2010 Scrum Guide published
● 2013 Scrum Guide translated to Arabic
11K
7. Who’s using it?
● Microsoft
● Yahoo
● Google
● Electronic Arts
● Lockheed Martin
● Philips
● Siemens
● Nokia
● Ericsson
● Intuit
● Boeing
● Spotify
● John Deere
● Sabre
● Salesforce.com
● Time Warner
● Turner Broadcasting
● BBC
● IBM
● Thomson Reuters
11K
9. What are they developing?
● Commercial software
● In-house development
● Contract development
● Fixed-price projects
● Financial applications
● ISO 9001-certified applications
● Embedded systems
● 24x7 systems with 99.999%
uptime requirements
● the Joint Strike Fighter
● Video game development
● FDA-approved, life-critical systems
● Satellite-control software
● Websites
● Handheld software
● Mobile phones
● Network switching applications
● ISV applications
● Some of the largest applications in
use
11K
10. Scrum Characteristics
● No specific engineering practices prescribed
● Requirements are captured as items in a list of “product
backlog”
● Self-organizing teams
● Product progresses in a series of month-long “sprints”
● Uses generative rules to create an agile environment for
delivering projects
● Empirical Process
11K
12. Why is a sprint just a month long?
Plan sprint durations around how long you can commit to
keeping change out of the sprint
11K
13. What is a generative rule?
Generative Rules
● A minimum set of things you must always do, to learn what
to do in any specific situation
● Helps you help yourself
Inclusive rules
● All the things you should do under all situations.
● Solves the problem for you
11K
14. What is an Empirical Process
Empirical Process
● Unpredictable
● Unrepeatable
● Requires scientific use
of data to understand
process
Defined Process
● Predictable
● Repeatable
● Completely understood
● Automatable
11K
15. Software Development Is Unrepeatable!
Complex
Anarchy
Technology
Requirements
Far from
Agreement
Close to
Agreement
Closeto
Certainty
Farfrom
Certainty
Source: Strategic Management and
Organizational Dynamics by Ralph Stacey in
Agile Software Development with Scrum by
Ken Schwaber and Mike Beedle.
11K
Simple
17. The Agile Values
Process and toolsIndividuals and interactions over
Following a planResponding to change over
Comprehensive documentationWorking software over
Contract negotiationCustomer collaboration over
11K
20. Sprints
● Scrum projects make progress in a series of “sprints”
● Typical duration is 2–4 weeks or a calendar month at
most
● A constant duration leads to a better rhythm
● Product is designed, coded, and tested during the sprint
11K
23. Product Backlog
● The requirements
● A list of all desired work on the
project
● Ideally expressed such that
each item has value to the users
or customers of the product
● Prioritized by the product owner
● Reprioritized at the start of each
sprint
This is the
product backlog
11K
24. Rough Sizing: T-shirts or Story points
XL
L
M
S
XS
11K
0, 0.5, 1, 2, 3,
5, 8, 13, 20,
40, 100, ?
25. A Sample Product Backlog
Backlog item Size
Allow a guest to make a reservation 3
As a guest, I want to cancel a reservation. 5
As a guest, I want to change the dates of a reservation. 3
As a hotel employee, I can run RevPAR reports (revenue-
per-available-room)
8
Improve exception handling 8
... 30
... 50
11K
26. Managing the Sprint Backlog
● Individuals sign up for work of their own choosing
● Work is never assigned
● Estimated work remaining is updated daily
11K
27. Managing the Sprint Backlog
● Any team member can add, delete or change the sprint
backlog
● Work for the sprint emerges
● If work is unclear, define a sprint backlog item with a
larger amount of time and break it down later
● Update work remaining as more becomes known
11K
28. A Sample Sprint Backlog
Tasks
Code the user interface
Code the middle tier
Test the middle tier
Write online help
Write the foo class
Mon
8
16
8
12
8
Tues
4
12
16
8
Wed Thur
4
11
8
4
Fri
8
8
Add error logging
8
10
16
8
8
11K
35. Sprint planning meeting
Sprint prioritization
• Analyze and evaluate product backlog
• Select sprint goal
Sprint planning
• Decide how to achieve sprint goal
(design)
• Create sprint backlog (tasks) from
product backlog items (user stories /
features)
• Estimate sprint backlog in hours
11K
36. Sprint planning meeting
Sprint prioritization
• Analyze and evaluate product backlog
• Select sprint goal
Sprint planning
• Decide how to achieve sprint goal
(design)
• Create sprint backlog (tasks) from
product backlog items (user stories /
features)
• Estimate sprint backlog in hours
Business
conditions
Team
capacity
Product
backlog
Technology
Current
product
11K
37. Sprint planning meeting
Sprint prioritization
• Analyze and evaluate product backlog
• Select sprint goal
Sprint planning
• Decide how to achieve sprint goal
(design)
• Create sprint backlog (tasks) from
product backlog items (user stories /
features)
• Estimate sprint backlog in hours
Sprint
goal
Sprint
backlog
Business
conditions
Team
capacity
Product
backlog
Technology
Current
product
11K
38. The Sprint Goal
A short statement of what the work will be focused on during the sprint
Database Application
Financial services
Life Sciences
Support features necessary for population
genetics studies.
Support more technical indicators than
company ABC with real-time, streaming data.
Make the application run on SQL Server in
addition to Oracle.
11K
39. Sprint Planning
● Team selects items from the product backlog they can commit to
completing
● Sprint backlog is created
● Tasks are identified and each is estimated (1-16 hours)
● Collaboratively, not done alone by the ScrumMaster
● High-level design is considered
11K
As a vacation planner, I
want to see photos of the
hotels so that I will get
a feeling for them.
Code the middle
tier (8 hr)
Code UI
(8 hr)
Write tests
(4 hr)
Meet PO (2 hr) Code Foo-class
(6 hr)
Update
performance tests
(4 hr)
40. The Daily Scrum
Parameters
● Daily
● 15 Minutes
● Stand Up
Not for problem solving
● Whole world is invited
● Only team members, ScrumMaster, product owner, can talk
Helps avoid unnecessary meetings
11K
41. 3 Questions for everyone
These are not status for the ScrumMaster. They are
commitments in front of peers
What did you do yesterday?
1
What will you do today?
2
Is anything in your way?
3
11K
42. The Sprint Review
● Team presents what it accomplished during the sprint
● Typically takes the form of a demo of new features or underlying
architecture
● Informal (2-hour prep time rule)
● Whole team participates
● Invite the world
A Review:
https://www.youtube.com/watch?v=Q6jMgmPIxmk
11K
43. The Sprint Retrospective
● Periodically take a look at what is and is not working
● Typically 15–30 minutes
● Done after every sprint
● Whole team participates (ScrumMaster, Product owner,
Team, Possibly customers and others)
11K
46. Product Owner
● Define the features of the product
● Decide on release date and content
● Be responsible for the profitability of the product (ROI)
● Prioritize features according to market value
● Adjust features and priority every iteration, as needed
● Accept or reject work results
11K
47. Product Owner Videos
● Why it’s important to have a committed product owner:
https://www.youtube.com/watch?v=BTTdHW8Z668
● How to negotiate as a product owner:
https://www.youtube.com/watch?v=ZG-NgkHv52Y
● Product ownership in a nutshell:
https://www.youtube.com/watch?v=502ILHjX9EE
11K
48. ScrumMaster
● Communicates with management
● Responsible for enacting Scrum values and practices
● Removes impediments
● Ensure that the team is fully functional and productive
● Enable close cooperation across all roles and functions
● Shield the team from external interferences
The ScrumMaster:
https://www.youtube.com/watch?v=oheekef7oJk
11K
49. The Team
● Typically 5-9 people
● Cross-functional
● Members should be full-time
● May be exceptions (e.g., database administrator)
11K
51. Scalability
● Typical individual team is 7 ± 2 people
● Scalability comes from teams of teams
● Factors in scaling
● Type of application
● Team size
● Team dispersion
● Project duration
11K
52. Scaling
● Scrum of Scrums
● Nexus – Scrum.org
● LeSS - http://less.works/
● SAFe -
http://www.scaledagileframe
work.com/
Why synchronized sprint length
is important:
https://www.youtube.com/watch
?t=12&v=Suugn-p5C1M
11K
55. Where to go next
● www.agilemiddleeast.org
● stateofagile.com
● www.scrumguides.org
● www.scrumalliance.org
● www.scrum.org
● www.agilealliance.org
● www.enterprisescrum.com
● www.mountaingoatsoftware.com/scrum
11K
56. A Reading List
● Agile and Iterative Development: A Manager’s Guide by Craig
Larman
● Agile Estimating and Planning by Mike Cohn
● Agile Project Management with Scrum by Ken Schwaber
● Agile Retrospectives by Esther Derby and Diana Larsen
● Agile Product Management with Scrum by Roman Pichler
● User Story Mapping by Jeff Patton
● Scrum and XP from the trenches by Henrik Kniberg
11K
57. A Reading List
● Agile Software Development Ecosystems by Jim Highsmith
● Agile Software Development with Scrum by Ken Schwaber and
Mike Beedle
● Scrum and The Enterprise by Ken Schwaber
● Succeeding with Agile by Mike Cohn
● User Stories Applied for Agile Software Development by Mike Cohn
● Software in 30 days by Ken Schwaber & Jeff Sutherland
● Enterprise Scrum by Mike Beedle
● Agile Testing by Lisa Crispin
11K
58. Credit
This presentation is based on Mike Cohn’s reusable Scrum
presentation.
mike@mountaingoatsoftware.com
www.mountaingoatsoftware.com
https://www.mountaingoatsoftware.com/agile/scrum/a-reusable-scrum-
presentation
(720) 890-6110 (office)
11K
59. Lean & Agile Middle East
info@meagile.com
https://agilemiddleeast.org/
Contact
Information
https://www.facebook.com/AgileMiddleEast
https://twitter.com/MEAgile
https://www.linkedin.com/groups?home=&gid=8133203
11K
60. Lean & Agile Middle East
Upcoming
Events
Professional Scrum Master 22-23 July, Dubai
Call for papers: Agile ME Summit, Sept 30
Procurement and Agile PM, 4-5 Oct., Dubai
Introducing Lean & Agile, Abu Dhabi, Oct.
Introducing Lean & Agile, Dubai, Oct.
Agile ME Summit 2016, March 19, Dubai
11K
61. Andreas Hägglund
Learning is optional,
so is survival
I run projects and make organizations more efficient
by working as:
● Change Agent
● Trainer & Coach
● Project Manager/Scrum Master
● Product Owner/Business Developer
17 years of experience of Management & IT
11K