This document provides an overview of an introduction to Scrum training session. It includes an agenda with topics like introduction, games and exercises, parking lot for questions, and forming teams. There is also background on the trainer, Elad Sofer, including his experience and roles. Key aspects of Scrum like the roles of Product Owner, Scrum Master and Development Team are defined. Concepts like the product backlog, user stories, story points, planning poker and backlog refinement are introduced and explained. Exercises are included to help illustrate estimating and splitting stories.
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.
Scrum Master Lessons from my 4 Year Old SonRyan Ripley
Â
At a recent cookout, my 4 year old son, Dawson, ran for the back yard and easily joined a game of hide and seek. Watching this unfold, I realized that these kids are naturally agile. They got straight to playing (the value) and didnât need a lot of ceremony to get there. They kids all did a quick hello, told Dawson what game they were playing, and invited him to join in (daily scrum). Then they played.
He and his friends self-organize, self-manage, and solve problems on the fly. They naturally exhibit the agile values and scrum practices that many adults struggle with daily.
For example, most parents have been bombarded with an unending stream of âWhyâs?â from their child. Why does this work? Why did that happen? Why? Why? Why? While this line of questioning can be stressing, it is also invaluable to finding the root cause of an issue. Scrum teams use this approach â called The 5-Whyâs â to get past technical issues and down to interpersonal issues that could be hindering the team.
This session is a fun discussion about the behaviors Iâve noticed in my son and how they translate to important lessons that all scrum master need to learn to better serve their teams.
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.
Scrum Master Lessons from my 4 Year Old SonRyan Ripley
Â
At a recent cookout, my 4 year old son, Dawson, ran for the back yard and easily joined a game of hide and seek. Watching this unfold, I realized that these kids are naturally agile. They got straight to playing (the value) and didnât need a lot of ceremony to get there. They kids all did a quick hello, told Dawson what game they were playing, and invited him to join in (daily scrum). Then they played.
He and his friends self-organize, self-manage, and solve problems on the fly. They naturally exhibit the agile values and scrum practices that many adults struggle with daily.
For example, most parents have been bombarded with an unending stream of âWhyâs?â from their child. Why does this work? Why did that happen? Why? Why? Why? While this line of questioning can be stressing, it is also invaluable to finding the root cause of an issue. Scrum teams use this approach â called The 5-Whyâs â to get past technical issues and down to interpersonal issues that could be hindering the team.
This session is a fun discussion about the behaviors Iâve noticed in my son and how they translate to important lessons that all scrum master need to learn to better serve their teams.
General introduction to agile practices like Scrum and Kanban. Also covers what situations Agile is best at, what situations Agile doesn't help with, and what an Agile team should look like. This deck is a general intro to Agile for OpenSource Connections clients.
An overview of IT challenges and how Perficient China uses agile frameworks, methodologies, and practices to address these challenges and consistently deliver valued results to our clients.
People say they are doing Scrum, but in fact "We are doing Scrum, but...." And the Butts are not pretty. That is, when they move away from Scrum, almost always it is less effective. Here is the ScrumButt Test, to help.
General introduction to agile practices like Scrum and Kanban. Also covers what situations Agile is best at, what situations Agile doesn't help with, and what an Agile team should look like. This deck is a general intro to Agile for OpenSource Connections clients.
An overview of IT challenges and how Perficient China uses agile frameworks, methodologies, and practices to address these challenges and consistently deliver valued results to our clients.
People say they are doing Scrum, but in fact "We are doing Scrum, but...." And the Butts are not pretty. That is, when they move away from Scrum, almost always it is less effective. Here is the ScrumButt Test, to help.
Introduction to Agile & scrum, but a bit from an HR perspective.
This presentation was given at "JobInfo" as some background material for a better understanding of recruitment in an agile world.
Infrastructure code in Agile software developmentElad Sofer
Â
This presentation i gave in an ILTAM group meeting discusses common problems with Infrastructure code development and how Agile helps to deal with them
Increasing the company's profitability and impact is the dream of every company. Nowadays Agility / Agile is the buzz word and the whole world want's it but most of the time companies are confused about how we can achieve the agility dream.
The written material provides a visible how, why and what of agility and what the best practices we need to execute to achieve agility.
Jeff Lopez Presentation for Agile Impact Conference 2018 Day 1.
"Learn speedy affinity facilitation techniques to eliminate waste and boost productivity in creating, prioritizing and estimating a backlog."
Slides from a 5/10/2017 talk at the Nasdaq Entrepreneurial Center (@theCenter) about a lean research mindset, the mechanics of learning from users, and the structure of a research prototype test session.
A keynote to help people involved in software product development to execute the right agile and lean practices in order to see a successful relationship among stakeholders.
This one weird trick will fix all your Agile problemsAnthony Marter
Â
In this presentation I cover the importance of a well functioning Product Management practice to following the 12 Agile principles. Often we focus just on the process parts of Scrum, and here I cover why this misses half of the principles.
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
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.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
Â
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
⢠The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
⢠Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
⢠Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
⢠Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
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.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
Â
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
Â
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Â
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Â
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Â
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
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
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Â
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
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.
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!
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.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...
Â
Scrum training day 1
1. You walk into a class, you have
been invited to attend a training.â¨
You read the text on the slide on
the projector. You first ignore it, the
second time you see it you start
reading... Once you finish reading
the slide, you find someone at a
table. You sit down, and exchange
all you know about Agile and Scrum
with each other until the session is
going to start.
3. ⢠No answers, just questions.
⢠Donât believe anything.
⢠Discussion!
⢠The agenda is a draft.
⢠Games & exercises
⢠Use the parking lot.
⢠A-Ha wall.
14. ⢠S/W Engineer.
⢠Agile coach.
⢠Blogger
⢠Co-Founder of âPractical-Agileâ
⢠Co-Organizer of âAgile â¨
Practitioners ILâ group
⢠Married to Keren
⢠Father of 2 boys.
17. The waterfall development model originates in
the manufacturing and construction industries
The first description of waterfall
is a 1970 article by Winston W. Royce
Royce presented this model as an
example of a flawed, non-working model
"I believe in this concept, but the implementation
described above is risky and invites failure"
[Royce 1970]
18. Division of work to specialized teams
(specification, design and testing) is
efficient
It is possible to âcollectâ or even
âknowâ all the requirements up-front
The harder we plan and analyze in the
beginning, the less thereâs change in
the project and the more successful
the project.
Multiple parallel programs speed up
the development
Multiple programs create big
management overhead and risk of
overloading the pipeline, R&D works
most efficiently in continuous mode
There is change always and
responding to it is vital. Uncertainty is
best reduced by learning from actual
implementation
Requirements evolve as customers
and our knowledge increases â based
on experience
Cross-functional teams reduce the
amount of handovers and delays, thus
they are more productive
19. You can save time by âgood-enoughâ
development.
Itâs possible to transfer information
effectively on written documents
without much of human contact.
Resource usage and cost optimization
is the key to increased productivity
Product development process can be
defined as a predictable and
repeatable process
Product development is an evolving
and adaptive process, unique for every
organization.
Concentrating on value stream
optimization, removing waste and
sustainable flow increases
productivity
Essential knowledge is lost in every
handover and human interaction is
needed to overcome it.
Any technical debt will slow
development down and thus we
donât allow technical debt to
accumulate.
22. 1. Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software
2. Welcome changing requirements, even late in development. Agile
processes harness change for the customerâs competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a
couple of months, with a preference to a shorter timescale.
4. Business people and developers must work together daily
throughout the project.
5. Build project around motivated individuals. Give them the
environment and support they need, and trust them to get the job
done.
6. The most efficient and effective method of conveying information to
and within development team is face-to-face conversation.
23. 7. Working software is the primary measure for progress.
8. Agile processes promote sustainable development. The
sponsors, developers, and users should be able to maintain a
constant pace indefinitely.
9. Continuous attention to technical excellence and good design
enhances agility.
10. Simplicity â the art of maximizing the amount of work not done â
is essential.
11. The best architectures, requirements, and designs emerge from
self-organizing teams.
12. At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly.
26. â¨
"Scrum is a team of eight individuals in Rugby.
Everyone in the pack acts together with everyone else
to move the ball down the field in small incremental
steps. Teams work as tight, integrated units with
whole team focusing on a single goal."â¨
â¨
27. ⢠Understanding that we cannot predict the future.
⢠One size does not fit all.
⢠Constant improvement.
⢠Transparency
⢠Team work
⢠As simple as possible & as little as possible.
⢠Prioritizing â Industry statistics show: 65% of all
features are rarelynever used.
⢠Empirical approach
⢠Fun !!!
28.
29. ⢠Defines the features of the product
⢠Defines release dates and content
⢠Responsible for ROI.
⢠Prioritizes features.
⢠Can change features and priority â¨
once every predefined interval.
⢠Decides what will be worked on in each â¨
iteration
⢠Accepts or rejects results.
30. ⢠Responsible for the scrum process.
⢠Protects the team.
⢠Helps removing impediments.
⢠He is standing at the nexus between:
⢠The product management that â¨
believes that any amount of work â¨
can be done.
⢠Developerâs that have the willingness to cut quality
to support the managements belief.
⢠Probably the least loved person in the world.
32. ⢠Scrum helps prevent such things by
encouraging:
â Team productivity
â High quality
â Top-notch engineering practices
⢠Unit testing TDD
⢠BDD
⢠Pair work
⢠Continuous integration
⢠Refactoring.
32
The Scrum master
34. ⢠Typically 5-9 people
⢠Cross-functional:
â˘âArchitectsâ, Programmers, testers â¨
UI designers, etc.
â˘Members should be full-time
â˘May be exceptions (e.g., database administrator)
⢠Teams are self-organizing
â˘Ideally, no titles but rarely a possibility
⢠Membership should change as little as possible
â˘only between sprints
35. ⢠List of features, Technology, issues.
⢠Items should deliver value for customer.
⢠Constantly prioritized & Estimated.
⢠Anyone can contribute.
⢠Visible to all.
⢠Derived from business plan, may be â¨
created together, with the customer.
⢠Can be changed every sprint!!!
⢠Customer is not âprogrammedâ to think â¨
of everything in advance.
36. Backlog item Estimate
As a user I would like to register 3
As a user I would like to login 5
As a buyer I would like to make a bid 3
As a buyer I would like to pay with a credit card 8
As a seller I would like to start an auction 8
... âŚ
Test register feature 10
Create infrastructure for login 20
37. DeďŹne 3 users for a â¨
social network â¨
targeted for kidsâ¨
38. Create a 3 LARGE user
stories for a Social
network special â¨
for kids
39. ⢠Also called backlog refactoring Sniffing.
⢠Done by the team and the PO.
⢠The goal is to have the backlog ready for the sprint
planning.
⢠Grooming = Splitting, clarifying & estimating.
⢠Usually grooming just enough for 2-3 sprints
ahead.
⢠Recommended to allocate ~5% of sprint time for
this task.
⢠NEVER allow the PO to reach a sprint planning
meeting with a backlog not in good shape.
Product backlog reďŹnement
40. ⢠Different scenarios
⢠Splitting across the data model.
â Support only a subset of attributes
⢠Splitting across operations
â CRUD parts of a protocol
⢠Splitting on results
â Success and failure scenarios.
⢠Splitting cross-cutting concerns
â Logging Security.
⢠Splitting functional & non-functional
requirements
43. Exercise
⢠Estimate the following based on
Weight in Kilograms.â¨
[NO GOOGLE PLEASE!!!]
⢠Chihuahua
⢠Great Dane
⢠Staffordshire bull terrier.
⢠Appalachian mountain dog.
⢠Border Collie
⢠American Cocker spaniel
43
46. Story points
⢠Name is derived from user stories.
⢠They reflect the âbignessâ of a user story.
âHow hard it is ?
âHow risky it is ?
âHow much of it there is ?
⢠Relative values matters.
⢠Unitless.
⢠Point values âinclude uncertaintyâ.
⢠Easy and quick
âA little effort helps a lot
âA lot of effort helps a little more
46
47. Planning poker
1. Each person gets a deck of cards.
2. The item to be estimated is read to all.
3. Attendants ask clariďŹcations for the item.
4. Each person selects a card and puts it on the
table facing down.
5. When everyone is done, cards are exposed.
6. If the estimations do not match a short
discussion is done. -> Goto 4.
7. Handle next item.
47
48. Exercise
⢠Estimate the following based on
size using planning poker.
⢠Spain
⢠China
⢠Luxembourg
⢠Denmark
⢠South Africa - 8 (Reference point)
⢠Belize
48
49. Why planning poker works ?
⢠Those who do the work estimate it.
⢠Emphasizes relative estimation
⢠Estimates are within one order of
magnitude.
⢠Reduces anchoring - Everyone's
opinion is heard.
49
53. Given anchor
â˘Group A
â˘Customer thinks 500
â˘customer has no technical knowledge
â˘Donât let the customer influence you
â˘Group B
555 hours
456 hours
â˘Same as B â¨
customer thinks 50
â˘Group C
99 hours
55. ⢠Usually the longest meeting of all.
⢠The meeting takes place prior to â¨
every sprint.
⢠Participants:
⢠All Team members , PO, Scrum master.
⢠Is divided into two Parts:
⢠Part I
â Team and PO discuss and clarify the top priority items
â Team and PO selects sprint Goal.
⢠Part II
â Team creates the sprint backlog
â Team commits on content of coming sprint.
56. ⢠The sprint backlog is defined by understanding â¨
and agreeing on the sprint goal(s) and selecting â¨
the appropriate items from the product backlog.
⢠The goal is determined by the customersproduct owner
team.
⢠The team compiles a list of tasks that are â¨
needed in order to complete the sprint goal(s).
⢠A task should be as small as possible and should not exceed a
time period of 2 days (time not effort).
⢠If a task X can not be defined, there will be a task to define
the task X.
⢠The sprint backlog can be modified throughout the sprint.
57.
58. ⢠The sprint is the productive part of the scrum
⢠It is a fixed, predefined, period of time.
⢠During this time the work load, the scope or â¨
nature of work must not be changed. The only âmanagerâ of the
scope is the sprint backlog.
⢠The team is free to accomplish the sprint goal as it seeâs fit, within
the limits of the teamâs procedures and the time limits.
⢠During the sprint, the team has total freedom over how it works:
⢠Work as many hours as it wants.
⢠Hold meetings whenever it wants
â During the sprint the team is accountable for only two things
⢠Daily scrum
⢠Sprint backlog.
59. 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
Design Code Integrate Test
60. ⢠A meeting that occurs daily at the same time. â¨
anyone who wants attend , can do so.
⢠Each of the team members needs to answer â¨
briefly these three questions:
1. What have you done since the last daily scrum?
2. What will you do until the next daily scrum?
3. What got in your way of doing work?
⢠The team does not report to anyone but the team.
⢠During the meeting only one of the team members is allowed to
speak, others should keep quiet.
⢠All of problems raised in the meeting should be written down and
resolved by the scrum masterteam.
⢠The daily scrum is not a technical meeting.
63. ⢠At the end of each sprint there is a â¨
meeting called the sprint review.
⢠The purpose of the meeting is to let the â¨
âcaptainâ to know where the ship is heading and where it is in itâs
route. In addition all new features will be presented to the product
owner.
⢠During this meeting the team presents to the management
customersusersproduct owner, what work has been DONE and
what was not.
⢠The only form of âautomatedâ presentations allowed is working
software, Slideware is banned.
⢠The things that were not accomplished will be returned to the
product backlog.
64. ⢠We have in Scrum â DOD â Definition of
Done.
⢠Terms of satisfaction of the PO
⢠Only DONE items count
⢠Success is well defined
⢠Example:
⢠Unit tested, Verification,â¨
Documented, deployed.
65. The ball-point game
⢠Ball must have air-time
⢠No ball to your direct neighbor
⢠First person= Last person
⢠Iteration = 1 min
⢠In between = 1 min
65
66. ⢠Periodically take a look at what is â¨
and is not working
⢠Typically takes ~60 minutes
⢠Done after every sprint
⢠Whole team participates
⢠Scrum Master
⢠Product owner
⢠Team
⢠Possibly customers and others
67. Whole team gathers and discusses what theyâd like to:
Start doing
Stop doing
Continue doing
72. Velocity
â˘How many points can the team complete
in one iteration.
â˘Easy to measure.
â˘Fixes estimation errors.
â˘Easily reďŹects the project status.
â˘Primary parameter in planning.
72
74. ⢠How many points still to complete ? (pts)
⢠What is the velocity ? (vel)
⢠How many sprints to go ? (num = pts/vel)
⢠What is the sprintâs length ? len
⢠How much time left ? num*len
⢠This is as simple as it gets !!!
74
So, how much time left ?
75.
76.
77. ⢠Mindset:
â My work is to do my work and to improve my
work.
⢠Practice:
â Choose and practice techniques the team has
agreed to try, until they are well understoodâ
that is, master standardized work
â Experiment until you ďŹnd a better way
â Repeat forever
78. ⢠Value: The moments of action â¨
or thought creating the â¨
product that the customer is â¨
willing to pay for.
⢠Waste: All other moments or â¨
actions that do not add value â¨
but consume resources.
⢠value ratio =â¨
total-value-time / total-cycle-time
79. ⢠Overproduction
â features or services the customer doesnât want
â large engineering documents, more detailed
designs than can be quickly implemented
â duplication of data
⢠Waiting / delay
â for clariďŹcation
â Documents
â Approval
â Components
â other groups to ďŹnish something
80. ⢠Handoff, conveyance, moving
â Giving a speciďŹcation from an analyst to an
engineer
â Giving a component to another group for testing
⢠Extra processing
â Relearning, lose of information.
â Forced conformance to centralized process
checklists of
â Recreating something made
81. ⢠Partially done work â WIP DIP
â Designs documented but not built
â Things built but not integrated or tested
â Things tested but not delivered.
⢠Task switching
â Interruption
â Multitasking on 3 projects
â Partial allocation of a person to many projects
82. ⢠Under-realizing people
â People only working to single speciality job
â Do people have the chance to change what they
see is waste.
⢠Information scatter or loss
â Information spread across many separate
documents
â Communication barriers such as walls between
people, or people in multiple locations.
83. ⢠Wishful thinking
â âWe MUST follow the planâ
â âThe estimate cannot increase; the effort
estimate is what we want it to be, not what it is
now proposed.â
â âWeâre behind schedule, but weâll make it up
later.â
84. Find one example of waste
from your work and design
an experiment to try
eliminate it.
â¨
10 minutes