The document discusses the principles of Agile and Scrum project management frameworks. It outlines the Agile Manifesto which values individuals and interactions, working software, customer collaboration, and responding to change over processes and tools, comprehensive documentation, contract negotiation, and following a plan. It then describes the basics of Scrum including common roles like Product Owner, Scrum Master, and Team. It explains Scrum events like the Sprint Planning Meeting, Daily Scrum, Sprint Review, and Retrospective and how they function to help teams work in short cycles to deliver working software.
Agile methodology is a framework for modern software development.
What is the philosophy behind Agile?
How does it differ from traditional project management strategies like waterfall?
What are the stages, meetings, tools, and team roles?
What is Scrum?
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
Agile methodology is a framework for modern software development.
What is the philosophy behind Agile?
How does it differ from traditional project management strategies like waterfall?
What are the stages, meetings, tools, and team roles?
What is Scrum?
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
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
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 presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
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
Agile Project Management - An introduction to Agile and the new PMI-ACPDimitri Ponomareff
The PMI-ACP recognizes knowledge of agile principles, practices and tools and techniques across agile methodologies. If you use agile practices in your projects, or your organization is adopting agile approaches to project management, then this PDM will provide a full overview about this new PMI certification while exploring key agile principles, practices and techniques. If you always wanted to learn more about agile, this presenter is a certified Agile practitioner, trainer and coach so you will receive up to date information about the state of Agile and how it can most help you in your organization or your career.
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/
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
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 presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
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
Agile Project Management - An introduction to Agile and the new PMI-ACPDimitri Ponomareff
The PMI-ACP recognizes knowledge of agile principles, practices and tools and techniques across agile methodologies. If you use agile practices in your projects, or your organization is adopting agile approaches to project management, then this PDM will provide a full overview about this new PMI certification while exploring key agile principles, practices and techniques. If you always wanted to learn more about agile, this presenter is a certified Agile practitioner, trainer and coach so you will receive up to date information about the state of Agile and how it can most help you in your organization or your career.
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/
Mobilised socialised: macro and micro view of mobile barney loehnisBarney Loehnis
Here I look at some of the macro implication of mobile - on how it is transforming society and different aspects of our life like eduction, health and empowering rural communities.
If small and under resourced groups can be so innovative, why is it that brands and marketing?
IN the second part we look at micro mobile and how brands can leverage its potential to drive services and communications.
Taking chinese brands global barney loehnis Barney Loehnis
Only 75 companies in the Fortune 500 and only 12 of the Top 100 worldwide brands are Chinese. This is about to change dramatically. In this presentation I exlpore some of the most successful Chinese brands and look at what has brought them success. I also review some of the challenges of launching International brands in China. What do CMO's need to know?How should digital, social and mobile play a role?
After an introduction to the basic tenets of Agile and some Agile practices, this presentation to Richmond SPIN (Software Process Improvement Network) talks about ways to convince your organization or clients to use Agile software development practices. Based on a presentation given at Agile 2009 by Arin Sime, Senior Consultant with OpenSource Connections.
The Agile Manifesto Values and Principles - Mandatory Study Material for PMI-...OSP International LLC
The PMI-ACP Exam will test your knowledge of many Agile concepts that cover a wide array of principles, tools, techniques and methods. So how do you know which of these concepts to concentrate on to create the most effective study plan? Well, a good start is to know and fully understand the Values and Principles of the Agile Manifesto. This is because it forms the basis for the majority of Agile concepts and constitutes the absolute minimum amount of knowledge required to correctly answer many questions on the PMI-ACP Exam.
Being Agile is an introduction to the 4 core values and 12 principles of the agile manifesto. If you're looking for something to explain it all to you in plain english, look no further!
Agile2009 - How to sell a traditional client on an Agile project planOpenSource Connections
12 suggestions for how to convince traditional clients to agree to an Agile project plan. Presented by Arin Sime of OpenSource Connections at Agile 2009 in Chicago.
An overview of the Agile Manifesto and why Agile SDLC is super important to excellent project management practices. Agile Software development is dominating the game these days. Whether you're going responsive, managing ecommerce, magento, or iphone apps Agile practices will help your efforts succeed.
Analysis With an Agile Mindset WorkshopKent McDonald
Analysis is often portrayed as eliciting and documenting requirements, frequently in terms that sound a lot like asking people what they want and writing it down. Analysis is about understanding your stakeholders and their needs, identifying the best solution for satisfying those needs in your particular context, and then building a shared understanding of that solution. Requirements play a part in that work, especially around describing the need, but they are certainly not the end product.
In this session, Kent McDonald will guide you through an approach to analysis in an agile manner. You’ll see examples of techniques that will help you understand stakeholders, context, and needs and then determine and describe possible solutions. You’ll then get an opportunity to try those techniques out on a case study. Along the way you’ll find out how to use analysis to determine if you are doing the right thing and how to determine how much analysis is just enough.
Key takeaways:
- Identify and understand potential users with user modeling.
- Determine the appropriate design approach for your project using the Purpose Based Alignment Model.
- Use decision filters to clearly state the desired outcome of your project and provide team with information for decision making.
- Identify and describe backlog items in more detail using collaborative modeling.
The Secret, Yet Obvious, Ingredient to Sustainable AgilityAhmed Sidky
This was a presentation I gave at Ciklum in Kiev, Ukraine and at ScrumTrek in Moscow, Russia. The presentation discuss the notion of Agile and agility and then talks about what people should do to have sustainable agile. They key to sustainable agile is education. By educated, and changing the mindset of everyone in the company, then you will have sustainable agility. However, if you just focus on strategy, structure, and processes, but don't change the mindset and culture and habits of people it will not be sustainable. The presentation introduces the learning roadmap developed by the International Consortium for Agile (ICAgile) as a path organizations should pursue to engage their people in a common educational journey about agile and agility not Scrum or any particular process.
The International Consortium for Agile (ICAgile) accredits training organizations, corporations, academic institutes and government entities, thereby providing their members with over 20 knowledge-based and competency-based certifications to pursue, based on the ICAgile Learning Roadmap created by experts from around the world.
ICAgile is the only certification and accreditation body to offer knowledge-based and competency-based certifications in every discipline needed to sustain agility in an organization. ICAgile has engaged over 40 International Agile gurus and experts to create the most comprehensive agile learning roadmap.
ICAgile's Learning Roadmap is intentionally designed to focus on the education of agile not on any particular flavor or methodology of agile to ensure that every organization, can utilize the educational roadmap as it matures and customizes it agile processes and practices. ICAgile’s Learning Roadmap includes over 20 different certifications covering the disciplines of Agile Executive Leadership, Agile Coaching and Facilitation, Agile Enterprise Coaching, Agile Project Management and Governance, Agile Value Management and Business Analysis, Agile Software Design and Programming, and Agile Testing.
The Agile Manifesto was published in 2001 and much has changed since then. Read on for an opportunity to rethink the Agile Manifesto. View Agile in a new light and deconstruct which concepts were home runs and which still need to evolve.
Many teams and individuals use agile tools and practices without understanding the "why" behind each practice. This presentation introduces the 12 agile principals to help teams and individuals make better decisions about which tools and practices to use for their given situation to be agile.
The evolution of agile development processDavid Tzemach
The Evolution of Agile Development Process
The main sections of this presentation
1. Overview
2. The Waterfall Model as a baseline
3. Waterfall Model – Phases of the process
4. The problem in traditional models
5. Agile Software Development as the Alternative
6. The Agile Manifesto – The Beginning
7. The Manifesto for Agile Software Development
8. The benefits of the agile methodology
Whole Agile - Unleashing People & Organizations Michael Sahota
In order to fully unleash the potential of workers we need to augment Agile/Scrum with Valuing People and rewire Organizational Governance.
Valuing People is about building a place where the whole person is welcome. Where there is safety, trust and authentic connection.
Organizational Governance refers to the approaches we use to run organizations: organizational structure, planning & control, roles & titles, compensation, performance management, information access, leadership and power. It has been well understood that these typically impact Scrum significantly.
The Power of an Agile Mindset - Linda RisingAgileSparks
I've wondered for some time whether much of Agile's success was the result of the placebo effect, that is, good things happened because we believed they would. The placebo effect is a startling reminder of the power our minds have over our perceived reality. Now cognitive scientists tell us that this is only a small part of what our minds can do. Research has identified what I like to call "an agile mindset," an attitude that equates failure and problems with opportunities for learning, a belief that we can all improve over time, that our abilities are not fixed but evolve with effort. What's surprising about this research is the impact of an agile mindset on creativity and innovation, estimation, and collaboration in and out of the workplace. I'll relate what's known about this mindset and share some practical suggestions that can help all of us become even more agile.
Scrum is an efficient framework within which you can develop software with teamwork. It is based on agile principles.
This presentation will help you understand agile development in general and Scrum in specific. You will get familiar with its associated terminology along with appropriate examples.
Benefit of scrum ceremonies presentationKnoldus Inc.
A group of seven sits and stands at a conference table while another person addresses the group. Scrum ceremonies can help teams improve their processes, increase efficiency and create innovative solutions during product development. These meetings allow team members to collaborate throughout the Scrum process so they can work together toward shared goals. Understanding the various types of Scrum ceremonies can help you implement and execute them successfully within your team.
Here is a presentation I presented to management describing how waterfall transitions into scrum. Couldn’t have been done without slideshare.com slides. This is me giving back.
In this slides deck, Avidan Hetzroni explains the basic concepts behind the Scrum Framework values and principles and how Scrum bind together the events, roles, and artifacts to govern the relationships and interaction between them.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
14. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Principle: # 8
15. Continuous attention to technical excellence and good design enhances agility. Principle: # 9
16. Simplicity--the art of maximizing the amount of work not done--is essential. Principle: # 10
17. The best architectures, requirements, and designs emerge from self-organizing teams. Principle: # 11
18. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Principle: # 12
20. The Basics of Scrum 1 2 3 4 5 6 ScrumMaster Daily ScrumMeeting 7 8 9 10 11 12 4-WeekSprint 13 Review Product Owner The Team 1 2 3 4 Potentially Shippable Product 5 6 7 8 9 10 11 12 13 Retrospective Commitment No Changes (in Duration or Deliverable)
21. The Basics of Scrum ScrumMaster Daily ScrumMeeting 4-WeekSprint Review Product Owner The Team 1 2 3 4 Potentially Shippable Product 5 6 7 8 9 10 11 12 13 Retrospective Commitment No Changes (in Duration or Deliverable)
22. Product Owner Responsible for the overall project vision and goals Responsible for managing project ROI vs. risk Responsible for taking all inputs into what the team should produce, and turning it into a prioritized list (the Product Backlog) Participates actively in Sprint Planning and Sprint Review meetings, and is available to team throughout the Sprint Determines release plan and communicates it to upper management and the customer
23. The Basics of Scrum ScrumMaster Daily ScrumMeeting 4-WeekSprint Review Product Owner The Team 1 2 3 4 Potentially Shippable Product 5 6 7 8 9 10 11 12 13 Retrospective Commitment No Changes (in Duration or Deliverable)
24. Team 7 people, + or – 2 Has worked with as high as 15, as few as 3 Can be shared with other teams (but better when not) Can change between Sprints (but better when they don’t) Can be distributed (but better when co-located) Cross-functional Possesses all the skills necessary to produce an increment of potentially shippable product Team takes on tasks based on skills, not just official “role” Self-managing Team manages itself to achieve the Sprint commitment
25. The Basics of Scrum ScrumMaster Daily ScrumMeeting 4-WeekSprint Review Product Owner The Team 1 2 3 4 Potentially Shippable Product 5 6 7 8 9 10 11 12 13 Retrospective Commitment No Changes (in Duration or Deliverable)
26. The Role of the ScrumMaster The ScrumMaster does everything in their power to help the team achieve success This includes: Serving the team Protecting the team Guiding the team’s use of Scrum
27. What the ScrumMaster Does Serves the team The ScrumMaster takes action to help remove impediments to the team’s effectiveness The ScrumMaster facilitates the team’s group interactions, to help the team achieve its full potential Protects the team The ScrumMaster protects the team from anything that threatens its effectiveness, such as outside interference or disruption The ScrumMaster will need to confront uncomfortable issues, both inside and outside the team Guiding the team’s use of Scrum The ScrumMaster teaches Scrum to the team and organization The ScrumMaster ensures that all standard Scrum rules and practices are followed The ScrumMaster organizes all Scrum-related practices
28. The Basics of Scrum ScrumMaster Daily ScrumMeeting 4-WeekSprint Review Product Owner The Team 1 2 3 4 Potentially Shippable Product 5 6 7 8 9 10 11 12 13 Retrospective Commitment No Changes (in Duration or Deliverable) Product Backlog
29. Product Backlog Product Owner lists items in descending order of priority (highest priority item is listed first, next-highest is second, etc.) Size estimates are rough estimates (can either be arbitrary “points”, or “ideal days”)
30. Product Backlog List of everything that could ever be of value to the business for the team to produce Ranked in order of priority Priority is a function of business value versus risk Product Owner can make any changes they want before the start of a Sprint Planning Meeting Items added, changed, removed, reordered How much documentation is up to the team and Product Owner to decide The farther down the list, the bigger and less defined the items become ~2 Sprints worth are defined in detail
31. The Basics of Scrum ScrumMaster Daily ScrumMeeting 4-WeekSprint Review Product Owner The Team 1 2 3 4 Potentially Shippable Product 5 6 7 8 9 10 11 12 13 Retrospective Commitment No Changes (in Duration or Deliverable) Product Backlog
32. Sprint Planning Meeting Takes place before the start of every Sprint Team decides how much Product Backlog it will commit to complete by the end of the Sprint, and comes up with a plan and list of tasks for how to achieve it What’s a good commitment? Clearly understood by all Shared among the team Achievable without sacrificing quality Achievable without sacrificing sustainable pace Attended by Team, Product Owner, ScrumMaster, Stakeholders May require 1-2 hours for each week of Sprint duration 2 week Sprint = 2-4 hours, 4 week Sprint = 4-8 hours
33. Not textbook Scrum, but many teams find it useful Takes place several days before the end of a Sprint (and start of the next Sprint) Product Owner spends an hour walking the team through the items at the top of the Product Backlog for the next Sprint Team asks questions, requests clarification, recommend items to be broken down further Review & Retrospective for Sprint 3 (afternoon) Sprint Planning Meeting forSprint 4 (morning) Sprint 4 Begins Pre-Meetingfor Sprint 4 Mon Tues Weds Thurs Fri Sprint Pre-Planning Meeting
34. Daily Scrum Meeting Every weekday Whole team attends Everyone stands Lasts 15 minutes or less Everyone reports 3 things only to each other What was I able to accomplish since last meeting What will I try to accomplish by next meeting What is blocking me No discussion, conversation until meeting ends Product Owner can attend and report Update of artifacts after standup
35. Table Exercise: Daily Scrum Meeting Do a Daily Scrum Meeting for your table One person plays the role of ScrumMaster The rest of the table are team-members Each team-member reports to the group: What I was able to get done since last Daily Standup Meeting What I will try to get done by the next Daily Standup Meeting What is blocking me? (If nothing, say “No Blocks”) But there is a twist…
36. Updating the Sprint Backlog Before or after the Daily Scrum, team members update the hours remaining on the Sprint Backlog
37. The Basics of Scrum ScrumMaster Daily ScrumMeeting 4-WeekSprint Review Product Owner The Team 1 2 3 4 Potentially Shippable Product 5 6 7 8 9 10 11 12 13 Retrospective Commitment No Changes (in Duration or Deliverable)
38. Sprint Review Purpose of the Sprint Review is Demo what the team has built Generate feedback, which the Product Owner can incorporate in the Product Backlog Attended by Team, Product Owner, ScrumMaster, functional managers, and any other stakeholders A demo of what’s been built, not a presentation about what’s been built no Powerpoints allowed! Usually lasts 1-2 hours Followed by Sprint Retrospective
39. The Basics of Scrum ScrumMaster Daily ScrumMeeting 4-WeekSprint Review Product Owner The Team 1 2 3 4 Potentially Shippable Product 5 6 7 8 9 10 11 12 13 Retrospective Commitment No Changes (in Duration or Deliverable)
40. Sprint Retrospective What is it? 1-2 hour meeting following each Sprint Demo Attended by Product Owner, Team, ScrumMaster Usually a neutral person will be invited in to facilitate What’s working and what could work better Why does the Retrospective matter? Accelerates visibility Accelerates action to improve
This deck is a compilation of the Agile manifesto, it’s 12 principles, and a few basic elements of the SCRUM process.The SCRUM process is a specific adaption of Agile. It outlines 3 roles of people involved in a project and different way to manage meetings and each SPRINT.A few link below to more resourceshttp://agilemanifesto.org/http://www.icescrum.org/en/http://www.scrumalliance.org/http://www.implementingscrum.com/section/blog/cartoons/