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.
This is one of the very best presentations about scrum that I know of and thought it worthwhile to have it up for people to be able to check it out. It's great that the authors went for a Creative Commons license.
Training materials for Agile Scrum. Starts with an overview of Agile and Lean. Followed with the Agile Scrum key concepts like Product Owner, Scrum Master, Scrum Team and Product Backlog. Theory is complemented with learnings and best practices from real life software development.
This is one of the very best presentations about scrum that I know of and thought it worthwhile to have it up for people to be able to check it out. It's great that the authors went for a Creative Commons license.
Training materials for Agile Scrum. Starts with an overview of Agile and Lean. Followed with the Agile Scrum key concepts like Product Owner, Scrum Master, Scrum Team and Product Backlog. Theory is complemented with learnings and best practices from real life software development.
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
I got a copy of this from the internet, and it was not written by me. yet I found this PPT quite helpful for you to understand the Scrum, so just enjoy it.
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 "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.
Scrumban - applying agile and lean practices for daily uncertainty by Vidas V...Vidas Vasiliauskas
In this presentation I have talked about scrumban - a mix of routines and techniques for daily use in dynamic environment. Like in startups, product manufacture, support or similar cases.
Introduction to Project Management with ScrumPierre E. NEIS
It's a small presentation to give the basic principles of scrum.
The presentation mode is made interactively with the audience.
The progression of the slides are scaled on progessive learning and fixing process: starting from theory to practice.
It's not enough to start a Scrum Project and do not replace a mature scrum training delivered by a senior Scrum Trainer.
This is my presentation from the Turku Agile Days 2013 #tad013 on 2013-05-14.
Created by my colleague Ralf Kruse, the agile42 Kanban Pizza Game is an excellent way of trying out how to create a kanban board from scratch and optimizing it, in a failsafe and accommodating environment. In fact, every new Kanban team needs to create their board from scratch, and as far as we know (and we know a few things) this is the only Kanban game that doesn't give you a ready made process.
If you want to run this game in your own team, be sure to check out the rules and the tips-n-tricks at http://www.agile42.com/en/training/kanban-pizza-game/.
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
I got a copy of this from the internet, and it was not written by me. yet I found this PPT quite helpful for you to understand the Scrum, so just enjoy it.
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 "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.
Scrumban - applying agile and lean practices for daily uncertainty by Vidas V...Vidas Vasiliauskas
In this presentation I have talked about scrumban - a mix of routines and techniques for daily use in dynamic environment. Like in startups, product manufacture, support or similar cases.
Introduction to Project Management with ScrumPierre E. NEIS
It's a small presentation to give the basic principles of scrum.
The presentation mode is made interactively with the audience.
The progression of the slides are scaled on progessive learning and fixing process: starting from theory to practice.
It's not enough to start a Scrum Project and do not replace a mature scrum training delivered by a senior Scrum Trainer.
This is my presentation from the Turku Agile Days 2013 #tad013 on 2013-05-14.
Created by my colleague Ralf Kruse, the agile42 Kanban Pizza Game is an excellent way of trying out how to create a kanban board from scratch and optimizing it, in a failsafe and accommodating environment. In fact, every new Kanban team needs to create their board from scratch, and as far as we know (and we know a few things) this is the only Kanban game that doesn't give you a ready made process.
If you want to run this game in your own team, be sure to check out the rules and the tips-n-tricks at http://www.agile42.com/en/training/kanban-pizza-game/.
If you’re a (mobile) startup, you probably know how hard it is to keep everything (and everyone) organised. Developers, testers, marketers, designers, product managers, investors and every other stakeholder have to be constantly communicating, so that all project specifications are understood and internalised simultaneously.
This is just an introduction to SCRUM and its multiple benefits.
What is Web 2.0 and what is Enterprise 2.0. Both turn traditional business models upside down, as customers become part of your production process. This allows internet companies to compete with traditional companies on quality.
Hello, my name is Illya Pavlichenko and I’m an Agile Coach and Professional Scrum Trainer (PST) at Unusual-Concepts. My job is all about dealing with Agile and Scrum dysfunctions and I love it. I work with multiple companies/teams and I see the same anti-patterns (symptoms) of using Scrum AGAIN and AGAIN. Well, I decided to create a list of them. It turned out to be exhaustively long. Then I removed less important items and finally got the list of 27 symptoms you can see below. Each of the symptoms potentially can lead to a separate article and/or discussion. That is why I attached quotes from best Scrum books (from my point of view) to make those symptoms as self-explanatory as possible.
So, are you ready for 27 Scrum dysfunctions? Here it is - Rotten Scrum.
This power point presentation is an introduction to Scrum and covers the following topics:
* Problems with a traditional approach
* What is Scrum?
* Why use Scrum?
* How does Scrum work?
* The Product Owner
* The Scrum Master
* The Team
* The Product Backlog
* Benefits of using a Product Backlog
* The Sprint Backlog
* The Scrum Cycle
* The Burn Down Chart
You can copy, distribute, and use the content of the presentation in accordance to Creative Commons Attribution 2.5 License.
Parce que l’agilité à grande échelle passe d’abord par une maîtrise parfaite de Scrum, nous proposons de revoir l’historique et les fondamentaux de la méthode, son application et les recommandations basées sur notre expérience.
Nous aborderons ensuite son utilisation à plus grande échelle sur plusieurs équipes.
Vladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mixVladimirs Ivanovs
Vladimirs Ivanovs, IPMA GYCW2013 Dubrovnik Croatia, interactive workshop/game "Agile - traditional or balanced mix" or "Creating children's book with SCRUM".
About trainer:
Vladimirs is consultant and trainer in Project Management and IT Service Management, IPMA-B and ITIL Expert certified. Board member at IPMA Latvia, assessor, developing Young Crew group. Teaching Programme and Project Portfolio Management for masters in Project Management. Has a degree in Computer Sciences and Executive MBA from Stockholm School of Economics. Worked for large telecoms and as CIO for global retail chain. Owner of ITSM LLC, company that is solving IT and Project Management issues, providing consulting and trainings, CIOs and PMs for rent. Have been recently speaking on global TFT12 conference, regional Agile and Project Management events.
Vladimirs Ivanovs - Creating children book in 45 minutes thanks to ScrumVladimirs Ivanovs
Creating a book is not a simple project however applying Agile principles to the process might make it much more easier to manage and give you better results. During the workshop we will create a children's book of "Goldilocks and the three bears" by using Scrum techniques. You will get familiar with Product Backlog, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective. You will also stay awake as workshop requires your active participation, gives ability to have fun and engage your creativity.
This workshop have been delivered by me at such locations as Agile Tour Vilnius 2013, IPMA Project Management congress 2013 in Dubrovnik, StartUp Latvia and Agile Latvia, telecom Orange Polska and IPMA Polska workshop. More to come ;)
Another name for this workshop is "Goldilocks and the Three Bears". A nice workshop to feel the agile process in action.
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.
Ao concluir este curso, o/a estudante mencionado/a acima adquiriu novas habilidades, incluindo como selecionar a melhor tecnologia para sua empresa e como integrar soluções tecnológicas aos seus negócios com sucesso.
Apresentado 4/7/2021
"Se tornando um Desenvolvedor Java NINJA" - Semana Integrada da PUC Campinas ...Cesar Augusto Nogueira
Palestra realizada na PUC Campinas durante a 19ª Semana Integrada em 13/09/2017 das 19h20min às 21h juntamente com Hivison Moura (@Hivison_Moura)
Mais informações da Semana Integrada em http://semanaintegrada.com.br
Nesta palestra apresentamos algumas boas práticas de codificação para desenvolvedores Java, dicas de carreira e informações úteis de como se tornar parte do grupo de usuários e desenvolvedores Java de Campinas e região, o SouJava Campinas JUG.
Nesta palestra, vamos introduzir conceitos de MapReduce de dados da cidade. Vamos explorar dados em BigData da cidade e importantes insights que podem ajudar o cidadão comum a descobrir o que está acontecendo em sua cidade e, assim, ajudar a política local a gastar dinheiro com projetos que realmente valham a pena serem investidos.
Palestra feita no Hacktown 2017, dia 9 de Setembro de 2017 (http://hacktown.com.br/palestra-minando-dados-de-sua-cidade-para-sua-comunidade-utilizando-java-ou-python/)
Apresentação feita na Trilha Java do #TDC2017 (http://www.thedevelopersconference.com.br/tdc/2017/saopaulo/trilha-java) com dicas úteis de como contribuir com a comunidade opensource de Java e como se tornar um verdadeiro desenvolvedor Java NINJA.
Faça parte do novíssimo slack de Java brasileiro oficial! Se cadastre pelo link > http://javadevbr.herokuapp.com
Siga o SouJava no Twitter > twitter.com/SouJava
É de Campinas e região? Participe das reuniões do twitter.com/SouJavaCampinas! Clique aqui > https://www.meetup.com/SouJavaCampinas/
Certificado de participação no Hackathon Globo 2016 - Cesar A. NogueiraCesar Augusto Nogueira
Selecionado dentre 1847 inscritos para o grupo de 50 participantes de todo o Brasil que participaram do Hackathon Globo 2016 que aconteceu nos dias 9 de 10 de Abril nos estúdios da Globo - Rio de Janeiro. A ideia da equipe 7 da qual participei foi de seguir um jogador ou um juíz em campo com uma câmera para o usuário acompanhar de perto o atleta preferido.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
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.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
3. What is Scrum?
• Scrum is a lightweight, simple to understand (but
difficult to master) agile process framework.
• Scrum is one of several agile software
development methods.
• Scrum and Extreme Programming (XP) are
probably the two best-known Agile methods. XP
emphasizes technical practices such as pair
programming and continuous integration. Scrum
emphasizes management practice such as the
role of Scrum Master.
• Many companies use the management practices
of Scrum with the technical practices of XP.
5. Mountain Goat Software, LLC
The Agile Manifesto–a statement of
values
Process and toolsProcess and toolsIndividuals and
interactions
Individuals and
interactions
over
Following a planFollowing a planResponding to changeResponding to change over
Source: www.agilemanifesto.org
Comprehensive
documentation
Comprehensive
documentationWorking softwareWorking software over
Contract negotiationContract negotiationCustomer
collaboration
Customer
collaboration
over
6. History of Scrum
• Ken Schwaber and Jeff Sutherland developed
the Scrum method in the early 1990’s. The
Scrum method has evolved somewhat over
the years.
• The definitive guide to the rules of Scrum,
The Scrum Guide, is maintained by Ken
Schwaber and Jeff Sutherland. [The most
recent edition of The Scrum Guide was
published in 2011.]
7. Origins of the idea
• The Scrum methodology was inspired by new approaches to
commercial product development being explored in the late
1980’s.
• In a 1986 article in the HBR, Hirotaka Takeuchi and Ikujiro Nonaka
urged companies to “Stop running the relay race and take up
rugby”.
“In today's fast-paced, fiercely competitive world of commercial new
product development, speed and flexibility are essential.
Companies are increasingly realizing that the old, sequential
approach to developing new products simply won't get the job
done. Instead, companies in Japan and the United States are using
a holistic method—as in rugby, the ball gets passed within the
team as it moves as a unit up the field.”
8. Mountain Goat Software, LLC
We’re losing the relay race
Hirotaka Takeuchi and Ikujiro Nonaka, “The
New New Product Development Game”,
Harvard Business Review, January 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.”
9. Mountain Goat Software, LLC
• 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.
Scrum in 100 words
10. Mountain Goat Software, LLC
Scrum origins
• Jeff Sutherland
• Initial scrums at Easel Corp in 1993
• IDX and 500+ people doing Scrum
• Ken Schwaber
• ADM
• Scrum presented at OOPSLA 96 with
Sutherland
• Author of three books on Scrum
• Mike Beedle
• Scrum patterns in PLOPD4
• Ken Schwaber and Mike Cohn
• Co-founded Scrum Alliance in 2002, initially
within the Agile Alliance
11. Mountain Goat Software, LLC
Characteristics
• Self-organizing teams
• Product progresses in a series of month-long
“sprints”
• Requirements are captured as items in a list of
“product backlog”
• No specific engineering practices prescribed
• Uses generative rules to create an agile
environment for delivering projects
• One of the “agile processes”
13. Mountain Goat Software, LLC
Putting it all together
Image available at
www.mountaingoatsoftware.com/scrum
14. Mountain Goat Software, LLC
Sprints
• Scrum projects make progress in a series of
“sprints”
• Analogous to Extreme Programming iterations
• 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
15. Mountain Goat Software, LLC
Sequential vs. overlapping
development
Source: “The New New Product Development Game” by Takeuchi
and Nonaka. Harvard Business Review, January 1986.
Rather than doing all of
one thing at a time...
...Scrum teams do a little
of everything all the time
Requirements Design Code Test
16. Mountain Goat Software, LLC
No changes during a sprint
• Plan sprint durations around how long you can
commit to keeping change out of the sprint
Change
19. Mountain Goat Software, LLC
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
20. Mountain Goat Software, LLC
The ScrumMaster
• Represents management to the project
• 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
21. Mountain Goat Software, LLC
The team
• Typically 5-9 people
• Teams are self-organizing
• Cross-functional:
• Programmers, testers, user experience designers, etc.
• Members should be full-time
• May be exceptions (e.g., database administrator)
22. Mountain Goat Software, LLC
The team
• Ideally, no titles but rarely a possibility
• Membership should change only between sprints
24. Mountain Goat Software, LLC
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
goal
Sprint
backlog
Sprint
backlog
Business
conditions
Business
conditions
Team
capacity
Team
capacity
Product
backlog
Product
backlog
TechnologyTechnology
Current
product
Current
product
25. Mountain Goat Software, LLC
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
As a vacation
planner, I want to
see photos of the
hotels.
As a vacation
planner, I want to
see photos of the
hotels.
Code the middle tier (8 hours)
Code the user interface (4)
Write test fixtures (4)
Code the foo class (6)
Update performance tests (4)
26. Mountain Goat Software, LLC
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 other unnecessary meetings
27. Mountain Goat Software, LLC
Everyone answers 3 questions
• These are not status for the ScrumMaster
• They are commitments in front of peers
What did you do yesterday?What did you do yesterday?
1
What will you do today?What will you do today?
2
Is anything in your way?Is anything in your way?
3
28. Mountain Goat Software, LLC
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
• No slides
• Whole team participates
• Invite the world
29. Mountain Goat Software, LLC
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
30. Mountain Goat Software, LLC
Start / Stop / Continue
• Whole team gathers and discusses what they’d
like to:
Start doingStart doing
Stop doingStop doing
Continue doingContinue doing
This is just one
of many ways to
do a sprint
retrospective.
32. Mountain Goat Software, LLC
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 sprintThis is the
product backlog
This is the
product backlog
33. Mountain Goat Software, LLC
A sample product backlog
Backlog item Estimate
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
34. Mountain Goat Software, LLC
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.
35. Mountain Goat Software, LLC
Managing the sprint backlog
• Individuals sign up for work of their own choosing
• Work is never assigned
• Estimated work remaining is updated daily
36. Mountain Goat Software, LLC
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
37. Mountain Goat Software, LLC
A sprint backlog
TasksTasks
Code the user interface
Code the middle tier
Test the middle tier
Write online help
Write the foo class
MonMon
8
16
8
12
8
TuesTues
4
12
16
8
WedWed ThurThur
4
11
8
4
FriFri
8
8
Add error logging
8
10
16
8
8
39. Mountain Goat Software, LLC
Hours
40
30
20
10
0
Mon Tue Wed Thu Fri
TasksTasks
Code the user interface
Code the middle tier
Test the middle tier
Write online help
MonMon
8
16
8
12
TuesTues WedWed ThurThur FriFri
4
12
16
7
11
8
10
16 8
50
40. Mountain Goat Software, LLC
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
• Scrum has been used on multiple 500+ person
projects
43. Mountain Goat Software, LLC
Where to go next
• www.mountaingoatsoftware.com/scrum
• www.scrumalliance.org
• www.controlchaos.com
• scrumdevelopment@yahoogroups.com
44. Mountain Goat Software, LLC
A Scrum 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
45. Mountain Goat Software, LLC
A Scrum reading list
• Agile Software Development Ecosystems by Jim Highsmith
• Agile Software Development with Scrum by Ken Schwaber and
Mike Beedle
• Scrum andThe Enterprise by Ken Schwaber
• Succeeding with Agile by Mike Cohn
• User Stories Applied for Agile Software Development by Mike Cohn
46. Mountain Goat Software, LLC
Copyright notice
• You are free:
• to Share to copy, distribute and and transmit the work―
• to Remix to adapt the work―
• Under the following conditions
• Attribution.You must attribute the work in the manner specified
by the author or licensor (but not in any way that suggests that
they endorse you or your use of the work).
• Nothing in this license impairs or restricts the
author’s moral rights.
• For more information see http://creativecommons.org/licenses/by/3.0/
47. Mountain Goat Software, LLC
Contact information
Presentation by: Mike Cohn
mike@mountaingoatsoftware.com
www.mountaingoatsoftware.com
(720) 890-6110 (office)
Presentation by: Mike Cohn
mike@mountaingoatsoftware.com
www.mountaingoatsoftware.com
(720) 890-6110 (office)
You can remove this (or any slide) but you
must credit the source somewhere in your
presentation. Use the logo and company
name (as at bottom left, for example) or
include a slide somewhere saying that
portions (or all) of your presentation are
from this source. Thanks.
Editor's Notes
Most slides are courtesy of Mike Cohn at Mountain Goat Software: http://www.mountaingoatsoftware.com/presentations/30-an-overview-of-scrum
Photo Credit: Jim McDougall [via Flicker] Rugby scrum explained: http://www.youtube.com/watch?v=nH5mi1H8lgs
rapidly changing or highly emergent requirements With Scrum no specific engineering practices are prescribed
Agile as an umbrella term that describes several lightweight development methods including Extreme Programming, Adaptive System Development, Dynamic System Development Method (DSDM), Feature Driven Development, Kanban and Crystal.
while there is value in the items on the right, we value the items on the left more.
[Quick definition] Major appeal of Scrum is the simplicity of its basic principles.
Few ideas are completely original. What is the “sequential approach’?
would be nice to include a quote from Wicked Problems here
Releasable software every iteration.
Sprints may be 1-4 weeks in length. “ One aspect of agile development is often missed or glossed over: a world view that organizations are complex adaptive systems. A complex adaptive system is one in which decentralized, independent individuals interact in self-organizing ways, guided by a set of simple, generative rules, to create innovative, emergent results . XP’s 12 practices, for example, were never intended to be all-inclusive rules; instead, they are generative rules that interact in concert when a team of individuals practices them.“ “ Most methodologies provide inclusive rules—all the things you could possibly do under all situations. Agile methods offer generative rules—a minimum set of things you must do under all situations to generate appropriate practices for special situations . Teams that follow inclusive rules depend on someone else to name in advance the practices and conditions for every situation. This obviously breaks down quickly. A team that follows generative rules depends on individuals and their creativity to find ways to solve problems as they arise. Creativity, not voluminous written rules, is the only way to manage complex software development problems and diverse situations.”
“ Sprints contain and consist of the Sprint Planning Meeting, Daily Scrums, the development work, the Sprint Review Meeting, and the Sprint Retrospective.”
“ The ScrumMaster's authority extends only to the process. The ScrumMaster is an expert on the process and on using it to get a team to perform to its highest level. But, a ScrumMaster does not have many of the traditional responsibilities—scope, cost, personnel, risk management among them—that a project manager does.” Who then does risk management?
“ The team itself assumes the responsibility for determining how to best achieve the product goals (as established by the product owner). Team members will collaboratively decide which person should work on which tasks, which technical practices are necessary to achieve stated quality goals, and so on.” “ Scrum relies on a self-organizing, cross-functional team. The scrum team is self-organizing in that there is no overall team leader who decides which person will do which task or how a problem will be solved. Those are issues that are decided by the team as a whole. The team is cross-functional so that everyone necessary to take a feature from idea to implementation is involved.”
“ Scrum recognizes no titles for Development Team members other than Developer, regardless of the work being performed by the person; there are no exceptions to this rule;” [Scrum Guide] Motivation for no-roles rule: “for a team of specialists to be successful each specialist must accept general responsibility for the system as a whole.”
Ceremonies = activities or things you do Could add release planning or “develop product backlog”
Release plan = “a roadmap of what can be expected after a couple of sprints, and what will be part of the release and what won’t.” Business condition example: 99 cent apps are popular Print goal or theme is defined by stories selected from product backlog. May select a story that is not the absolutely next highest priority story because it complements a theme related to the highest priority stories.
“ The two parts of the Sprint Planning Meeting answer the following questions, respectively: o What will be delivered in the Increment resulting from the upcoming Sprint? o How will the work needed to deliver the Increment be achieved?”
Chickens and pigs… “ Over the years, the labels have generated their share of controversy. Some argue that the terms are harmful to the process because they are derogatory. Others say that the negative connotation conjures a power dynamic that drives negative behaviour. Either way, you won't find any references to animals, barnyard or otherwise, in the new Scrum Guide.”
As a <role> I want to <feature> so that <business value>