This document provides an overview of Scrum, an agile framework for project management. It describes the origins of Scrum, its key roles, ceremonies, artifacts, and processes. Scrum uses short "sprints" to iteratively develop products, with daily stand-ups, sprint planning meetings, reviews, and retrospectives. Teams self-organize to complete prioritized backlog items within each sprint.
PMI and Scrum - bridging the gap
Presentation for PMI members and Agilists in Montevideo, Uruguay, introducing commonalities between Project Management and Agile approaches.
Unleashing the Power of Automated Refactoring with JDTNaresh Jain
Refactoring is a series of small steps, each of which changes the program’s internal structure without changing its external behaviour. Refactoring, as a tool, to automate behaviour-preserving transformations to source code are not only very popular in agile development environments, but have been widely established as a cornerstone of the daily software development process, regardless of the methodology being used. Most major development environments such as Eclipse offer a set of powerful refactoring to substantially increase development productivity.
In this live demo, I’ll show
* the real value of refactoring,
* how we practice it safely,
* when and why we refactor,
* the power of refactoring tools and
* when we avoid refactoring.
I’ll be using two real-world examples of refactoring and sharing what I’ve learned about this important practice of the last 15 years.
Scrum/XP using Team System (devLink & Agile 2009)Tommy Norman
This is the slide deck from my devLink 09 and Agile 2009 conference presentations. I skipped the Scrum intro slides at Agile 2009 since most of the crowd already had the basics down. This was nainly a demo so for over half the presentation I was not using slides.
How to go beyond traditional Scrum principles and scale to globally distributed teams with Continuous Delivery and Subversion. Presented by Andy Singleton of Assembla and Scott Rudenstein of WANdisco. Presented Nov. 15, 2012. 30 minutes.
Agile development poses several challenges to effectively testing software. Many myths have become "common wisdom" about how testing is much more difficult, even impossible, in an agile environment. Aricent's software testing experts look at 7 of these myths, and based on their years of experience debunk them.
MeasureWorks - Velocity Conference Europe 2012 - a Web Performance dashboard ...MeasureWorks
For the Velocity Conference Europe 2012 workshop day this presentation is about the essentials for creation and building a Web Performance dashboard. This with ultimate goal of providing the audience a framework for designing and building a web performance dashboard. The session will cover the following 3 items:
Design guidelines: What defines a web performance dashboard? How to make sure it’s actionable and for people to actually use it on day to day basis?
Data collection: Why performance data? The various ways there are to collect data (e.g. synthetic versus RUM data, Webpagetest, Mobile) and how to correlate the different types of data and tools
Building the dashboard: How to build the actual dashboard, providing an overview of the tools/techniques used
At the end of the workshop you will be able to design and build your own dashboard based on the framework provided, or to optimize the current dashboards within your organization.
Naresh and Shyam's experience report how teams and their interactions evolved at various large enterprise thru their agile transition in the last 5-6 years.
PMI and Scrum - bridging the gap
Presentation for PMI members and Agilists in Montevideo, Uruguay, introducing commonalities between Project Management and Agile approaches.
Unleashing the Power of Automated Refactoring with JDTNaresh Jain
Refactoring is a series of small steps, each of which changes the program’s internal structure without changing its external behaviour. Refactoring, as a tool, to automate behaviour-preserving transformations to source code are not only very popular in agile development environments, but have been widely established as a cornerstone of the daily software development process, regardless of the methodology being used. Most major development environments such as Eclipse offer a set of powerful refactoring to substantially increase development productivity.
In this live demo, I’ll show
* the real value of refactoring,
* how we practice it safely,
* when and why we refactor,
* the power of refactoring tools and
* when we avoid refactoring.
I’ll be using two real-world examples of refactoring and sharing what I’ve learned about this important practice of the last 15 years.
Scrum/XP using Team System (devLink & Agile 2009)Tommy Norman
This is the slide deck from my devLink 09 and Agile 2009 conference presentations. I skipped the Scrum intro slides at Agile 2009 since most of the crowd already had the basics down. This was nainly a demo so for over half the presentation I was not using slides.
How to go beyond traditional Scrum principles and scale to globally distributed teams with Continuous Delivery and Subversion. Presented by Andy Singleton of Assembla and Scott Rudenstein of WANdisco. Presented Nov. 15, 2012. 30 minutes.
Agile development poses several challenges to effectively testing software. Many myths have become "common wisdom" about how testing is much more difficult, even impossible, in an agile environment. Aricent's software testing experts look at 7 of these myths, and based on their years of experience debunk them.
MeasureWorks - Velocity Conference Europe 2012 - a Web Performance dashboard ...MeasureWorks
For the Velocity Conference Europe 2012 workshop day this presentation is about the essentials for creation and building a Web Performance dashboard. This with ultimate goal of providing the audience a framework for designing and building a web performance dashboard. The session will cover the following 3 items:
Design guidelines: What defines a web performance dashboard? How to make sure it’s actionable and for people to actually use it on day to day basis?
Data collection: Why performance data? The various ways there are to collect data (e.g. synthetic versus RUM data, Webpagetest, Mobile) and how to correlate the different types of data and tools
Building the dashboard: How to build the actual dashboard, providing an overview of the tools/techniques used
At the end of the workshop you will be able to design and build your own dashboard based on the framework provided, or to optimize the current dashboards within your organization.
Naresh and Shyam's experience report how teams and their interactions evolved at various large enterprise thru their agile transition in the last 5-6 years.
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.
From Waterfall to Agile - from predictive to adaptive methodsBjörn Jónsson
In this introduction into Agile methods, the background and environment of Software Development is discussed. Results of the 1995 Chaos report are mentioned, as well as interests in adaptive "lightweight" methods. Agile methods are explained in general and Scrum method taken as a concrete sample.
This is a survey about Dialog System, Question and Answering, including the 03 generations: (1) Symbolic Rule/Template Based QA; (2) Data Driven, Learning; (3) Data-Driven Deep Learning. It also presents the available Frameworks and Datas for Dialog Systems.
Business Valuation Principles for EntrepreneursBen Wann
This insightful presentation is designed to equip entrepreneurs with the essential knowledge and tools needed to accurately value their businesses. Understanding business valuation is crucial for making informed decisions, whether you're seeking investment, planning to sell, or simply want to gauge your company's worth.
B2B payments are rapidly changing. Find out the 5 key questions you need to be asking yourself to be sure you are mastering B2B payments today. Learn more at www.BlueSnap.com.
Implicitly or explicitly all competing businesses employ a strategy to select a mix
of marketing resources. Formulating such competitive strategies fundamentally
involves recognizing relationships between elements of the marketing mix (e.g.,
price and product quality), as well as assessing competitive and market conditions
(i.e., industry structure in the language of economics).
Cracking the Workplace Discipline Code Main.pptxWorkforce Group
Cultivating and maintaining discipline within teams is a critical differentiator for successful organisations.
Forward-thinking leaders and business managers understand the impact that discipline has on organisational success. A disciplined workforce operates with clarity, focus, and a shared understanding of expectations, ultimately driving better results, optimising productivity, and facilitating seamless collaboration.
Although discipline is not a one-size-fits-all approach, it can help create a work environment that encourages personal growth and accountability rather than solely relying on punitive measures.
In this deck, you will learn the significance of workplace discipline for organisational success. You’ll also learn
• Four (4) workplace discipline methods you should consider
• The best and most practical approach to implementing workplace discipline.
• Three (3) key tips to maintain a disciplined workplace.
Building Your Employer Brand with Social MediaLuanWise
Presented at The Global HR Summit, 6th June 2024
In this keynote, Luan Wise will provide invaluable insights to elevate your employer brand on social media platforms including LinkedIn, Facebook, Instagram, X (formerly Twitter) and TikTok. You'll learn how compelling content can authentically showcase your company culture, values, and employee experiences to support your talent acquisition and retention objectives. Additionally, you'll understand the power of employee advocacy to amplify reach and engagement – helping to position your organization as an employer of choice in today's competitive talent landscape.
Premium MEAN Stack Development Solutions for Modern BusinessesSynapseIndia
Stay ahead of the curve with our premium MEAN Stack Development Solutions. Our expert developers utilize MongoDB, Express.js, AngularJS, and Node.js to create modern and responsive web applications. Trust us for cutting-edge solutions that drive your business growth and success.
Know more: https://www.synapseindia.com/technology/mean-stack-development-company.html
3.0 Project 2_ Developing My Brand Identity Kit.pptxtanyjahb
A personal brand exploration presentation summarizes an individual's unique qualities and goals, covering strengths, values, passions, and target audience. It helps individuals understand what makes them stand out, their desired image, and how they aim to achieve it.
Enterprise Excellence is Inclusive Excellence.pdfKaiNexus
Enterprise excellence and inclusive excellence are closely linked, and real-world challenges have shown that both are essential to the success of any organization. To achieve enterprise excellence, organizations must focus on improving their operations and processes while creating an inclusive environment that engages everyone. In this interactive session, the facilitator will highlight commonly established business practices and how they limit our ability to engage everyone every day. More importantly, though, participants will likely gain increased awareness of what we can do differently to maximize enterprise excellence through deliberate inclusion.
What is Enterprise Excellence?
Enterprise Excellence is a holistic approach that's aimed at achieving world-class performance across all aspects of the organization.
What might I learn?
A way to engage all in creating Inclusive Excellence. Lessons from the US military and their parallels to the story of Harry Potter. How belt systems and CI teams can destroy inclusive practices. How leadership language invites people to the party. There are three things leaders can do to engage everyone every day: maximizing psychological safety to create environments where folks learn, contribute, and challenge the status quo.
Who might benefit? Anyone and everyone leading folks from the shop floor to top floor.
Dr. William Harvey is a seasoned Operations Leader with extensive experience in chemical processing, manufacturing, and operations management. At Michelman, he currently oversees multiple sites, leading teams in strategic planning and coaching/practicing continuous improvement. William is set to start his eighth year of teaching at the University of Cincinnati where he teaches marketing, finance, and management. William holds various certifications in change management, quality, leadership, operational excellence, team building, and DiSC, among others.
An introduction to the cryptocurrency investment platform Binance Savings.Any kyc Account
Learn how to use Binance Savings to expand your bitcoin holdings. Discover how to maximize your earnings on one of the most reliable cryptocurrency exchange platforms, as well as how to earn interest on your cryptocurrency holdings and the various savings choices available.
An introduction to the cryptocurrency investment platform Binance Savings.
Redistributable introtoscrum
1. An Introduction
to Scrum
<your name here>
<date>
Mountain Goat Software, LLC
2. An Introduction to Scrum
Presented by
<you>
<date>
Mountain Goat Software, LLC
3. We’re losing the relay race
“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.
Mountain Goat Software, LLC
4. 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.
Mountain Goat Software, LLC
5. 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
Mountain Goat Software, LLC
6. Scrum has been used by:
•Microsoft •Intuit
•Yahoo •Nielsen Media
•Google •First American Real Estate
•Electronic Arts •BMC Software
•High Moon Studios •Ipswitch
•Lockheed Martin •John Deere
•Philips •Lexis Nexis
•Siemens •Sabre
•Nokia •Salesforce.com
•Capital One •Time Warner
•BBC •Turner Broadcasting
•Intuit •Oce
Mountain Goat Software, LLC
7. Scrum has been used for:
• Commercial software • Video game development
• In-house development • FDA-approved, life-critical
systems
• Contract development
• Fixed-price projects • Satellite-control software
• Financial applications • Websites
• ISO 9001-certified • Handheld software
applications • Mobile phones
• Embedded systems • Network switching applications
• 24x7 systems with 99.999% • ISV applications
uptime requirements
• Some of the largest applications in
• the Joint Strike Fighter use
Mountain Goat Software, LLC
8. 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”
Mountain Goat Software, LLC
9. The Agile Manifesto–a statement of
values
Individuals and
over Process and tools
interactions
Comprehensive
Working software over
documentation
Customer
over Contract negotiation
collaboration
Responding to change over Following a plan
Source: www.agilemanifesto.org
Mountain Goat Software, LLC
10. Project noise level
Far from
Agreement
Anarchy
Requirements
Complex
Co
m
pli
ca Source: Strategic Management and
te
d Organizational Dynamics by Ralph Stacey in
Agile Software Development with Scrum by
Close to Simple Ken Schwaber and Mike Beedle.
Agreement
Certainty
Close to
Technology
Certainty
Far from
Mountain Goat Software, LLC
12. Putting it all together
Image available at
www.mountaingoatsoftware.com/scrum
Mountain Goat Software, LLC
13. 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
Mountain Goat Software, LLC
14. Sequential vs. overlapping
development
Requirements Design Code Test
Rather than doing all of
one thing at a time...
...Scrum teams do a little
of everything all the time
Source: “The New New Product Development Game” by Takeuchi
and Nonaka. Harvard Business Review, January 1986.
Mountain Goat Software, LLC
15. No changes during a sprint
Change
• Plan sprint durations around how long you can
commit to keeping change out of the sprint
Mountain Goat Software, LLC
18. 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
Mountain Goat Software, LLC
19. 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
Mountain Goat Software, LLC
20. The team
• Typically 5-9 people
• Cross-functional:
• Programmers, testers, user experience designers,
etc.
• Members should be full-time
• May be exceptions (e.g., database administrator)
Mountain Goat Software, LLC
21. The team
• Teams are self-organizing
• Ideally, no titles but rarely a possibility
• Membership should change only between sprints
Mountain Goat Software, LLC
23. Team
Sprint planning meeting
capacity
Sprint prioritization
Product • Analyze and evaluate product Sprint
backlog backlog goal
• Select sprint goal
Business
conditions Sprint planning
• Decide how to achieve sprint goal
(design)
Current Sprint
product • Create sprint backlog (tasks) from
product backlog items (user stories backlog
/ features)
Technology • Estimate sprint backlog in hours
Mountain Goat Software, LLC
24. 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 Code the middle tier (8 hours)
planner, I want to Code the user interface (4)
see photos of the Write test fixtures (4)
Code the foo class (6)
hotels. Update performance tests (4)
Mountain Goat Software, LLC
25. 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
Mountain Goat Software, LLC
26. Everyone answers 3 questions
1
What did you do yesterday?
2
What will you do today?
3
Is anything in your way?
• These are not status for the ScrumMaster
• They are commitments in front of peers
Mountain Goat Software, LLC
27. 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
Mountain Goat Software, LLC
28. 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
Mountain Goat Software, LLC
29. Start / Stop / Continue
• Whole team gathers and discusses what they’d
like to:
Start doing
Stop doing
This is just one
of many ways to Continue doing
do a sprint
retrospective.
Mountain Goat Software, LLC
31. 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
This is the
• Reprioritized at the start of
each sprint
product backlog
Mountain Goat Software, LLC
32. 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
3
reservation.
As a hotel employee, I can run RevPAR
8
reports (revenue-per-available-room)
Improve exception handling 8
... 30
... 50
Mountain Goat Software, LLC
33. The sprint goal
• A short statement of what the work will be
focused on during the sprint
Life Sciences
Support features necessary for
Database Application population genetics studies.
Make the application run on SQL
Server in addition to Oracle.
Financial services
Support more technical indicators
than company ABC with real-time,
streaming data.
Mountain Goat Software, LLC
34. Managing the sprint backlog
• Individuals sign up for work of their own choosing
• Work is never assigned
• Estimated work remaining is updated daily
Mountain Goat Software, LLC
35. 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
Mountain Goat Software, LLC
36. A sprint backlog
Tasks Mon Tues Wed Thur Fri
Code the user interface 8 4 8
Code the middle tier 16 12 10 4
Test the middle tier 8 16 16 11 8
Write online help 12
Write the foo class 8 8 8 8 8
Add error logging 8 4
Mountain Goat Software, LLC
38. Tasks Mon Tues Wed Thur Fri
Code the user interface 8 4 8
Code the middle tier 16 12 10 7
Test the middle tier 8 16 16 11 8
Write online help 12
50
40
30
Hours
20
10
0
Mon Tue Wed Thu Fri
Mountain Goat Software, LLC
39. 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
Mountain Goat Software, LLC
42. Where to go next
• www.mountaingoatsoftware.com/scrum
• www.scrumalliance.org
• www.controlchaos.com
• scrumdevelopment@yahoogroups.com
Mountain Goat Software, LLC
43. 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
Mountain Goat Software, LLC
44. A Scrum 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
Mountain Goat Software, LLC
45. 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/
Mountain Goat Software, LLC
46. Contact information
Presentation by: Mike Cohn
mike@mountaingoatsoftware.com
www.mountaingoatsoftware.com
(720) 890-6110 (office)
e)
You can remove this (or any slid
but you must credit the source
somewhere in your presentation.
Use the logo and company name
or
(as at bottom left, for example)
include a slide somewhere saying
that portions (or all) of your
ce.
presentation are from this sour
Thanks.
Mountain Goat Software, LLC
Editor's Notes
would be nice to include a quote from Wicked Problems here