1. The document provides an overview of practical scrum concepts including lean thinking, agile principles, scrum roles and ceremonies.
2. It discusses the roles of the product owner, scrum master and team in scrum and describes the four main scrum ceremonies: sprint planning, daily scrum, sprint review, and retrospective.
3. Key aspects of each ceremony are outlined such as their purpose, participants, and goals to continuously deliver working software and improve the process.
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.
Description of different methodologies for software project management. Overview of the classic Waterfall and the most popular methodologies for Agile development as Scrum, Kanban, XP..
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.
Introduction to the scrum framework: roles, activities and artifacts.
Scrum is an agile methodology for project management, to create a high quality product.
www.nieldeckx.be
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.
Description of different methodologies for software project management. Overview of the classic Waterfall and the most popular methodologies for Agile development as Scrum, Kanban, XP..
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.
Introduction to the scrum framework: roles, activities and artifacts.
Scrum is an agile methodology for project management, to create a high quality product.
www.nieldeckx.be
Why transform to Agile? What are the impediments to Agile Transformation? How to plan the Agile transformation? How to accelerate and sustain the Agile Transformation.
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
Scrumban Demystified. Talk from Agile New England.
A few of the Scrumban Evolutions from Mamamoth bank from the upcoming book on Scrumban.
More excerpts can be found at facebook.com/scrumban
Learn more at scrumban.io
Do you have a case study of applying the Kanban Method in a Scrum context. We want to learn more from your experiments and results. Contact us at info@codegenesys.com
Brief overview of Scrum
Overview of Kanban principles and practices
Comparison of Scrum and Kanban
Overview of Scrum with Kanban
Basic Metrics of Flow
Visualizing Metrics of Flow
Experience Report
Leading a large-scale agile transformation isn’t about adopting a new set of attitudes, processes, and behaviors at the team level… it’s about helping your company deliver faster to market, and developing the ability to respond to a rapidly-changing competitive landscape. First and foremost, it’s about achieving business agility. Business agility comes from people having clarity of purpose, a willingness to be held accountable, and the ability to achieve measurable outcomes. Unfortunately, almost everything in modern organizations gets in the way of teams acting with any sort of autonomy. In most companies, achieving business agility requires significant organizational change.
Agile transformation necessitates a fundamental rethinking of how your company organizes for delivery, how it delivers value to its customers, and how it plans and measures outcomes. Agile transformation is about building enabling structures, aligning the flow of work, and measuring for outcomes based progress. It's about breaking dependencies. The reality is that this kind of change can only be led from the top. This talk will explore how executives can define an idealized end-state for the transformation, build a fiscally responsible iterative and incremental plan to realize that end-state, as well as techniques for tracking progress and managing change.
This simple and crisp quick reference card is for Agile and Scrum basics. It is a simple way to glance through all the concepts and use it as a tool for revision, even before an interview.
In this presentation I will explain how companies can become learning organisations. I will give concrete step by step ideas that can be implemented in your own organisation. Hope you enjoy.
Why transform to Agile? What are the impediments to Agile Transformation? How to plan the Agile transformation? How to accelerate and sustain the Agile Transformation.
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
Scrumban Demystified. Talk from Agile New England.
A few of the Scrumban Evolutions from Mamamoth bank from the upcoming book on Scrumban.
More excerpts can be found at facebook.com/scrumban
Learn more at scrumban.io
Do you have a case study of applying the Kanban Method in a Scrum context. We want to learn more from your experiments and results. Contact us at info@codegenesys.com
Brief overview of Scrum
Overview of Kanban principles and practices
Comparison of Scrum and Kanban
Overview of Scrum with Kanban
Basic Metrics of Flow
Visualizing Metrics of Flow
Experience Report
Leading a large-scale agile transformation isn’t about adopting a new set of attitudes, processes, and behaviors at the team level… it’s about helping your company deliver faster to market, and developing the ability to respond to a rapidly-changing competitive landscape. First and foremost, it’s about achieving business agility. Business agility comes from people having clarity of purpose, a willingness to be held accountable, and the ability to achieve measurable outcomes. Unfortunately, almost everything in modern organizations gets in the way of teams acting with any sort of autonomy. In most companies, achieving business agility requires significant organizational change.
Agile transformation necessitates a fundamental rethinking of how your company organizes for delivery, how it delivers value to its customers, and how it plans and measures outcomes. Agile transformation is about building enabling structures, aligning the flow of work, and measuring for outcomes based progress. It's about breaking dependencies. The reality is that this kind of change can only be led from the top. This talk will explore how executives can define an idealized end-state for the transformation, build a fiscally responsible iterative and incremental plan to realize that end-state, as well as techniques for tracking progress and managing change.
This simple and crisp quick reference card is for Agile and Scrum basics. It is a simple way to glance through all the concepts and use it as a tool for revision, even before an interview.
In this presentation I will explain how companies can become learning organisations. I will give concrete step by step ideas that can be implemented in your own organisation. Hope you enjoy.
Great individuals are important but not enough (having bunch of great individuals in a group does not make a team). Cross Functional teams are important but not enough. Great company vision is important but not enough. Great technical best practices like a good CI environment is good, but not enough either.
In my presentation I will show you when having cross-functional teams is not enough anymore. There are several aspects that need to be considered in order to create High Performing Teams. I will explain the right way to assemble teams, and how to create the team vision that fosters growth and keeps them on track. I will also explain the different phases of a team and how they relate to scrum practices, i.e. when you teach what and when, and last but not least…how to help teams to spread knowledge amongst themselves.
Do you want to know how all of these and other small pieces come together in order to create High Performing Teams? Come and see my talk "How to Create High Performing teams".
The sole purpose of this presentation was to introduce Agile Scrum Methodology into our company. We were following sprints and agile methodology, but never planned it properly before this.
A few months back, I recalled my days of working with Limewire and having few scrum masters in DigiMantra Labs. So we gave a little introduction and after that most of our teams are following this method. We now have 2 qualified Scrum Masters and counting.
Slidedeck for 1 hour basic workshop about Agile in general and Intro to Scrum framework for newbies without tight linking to the software development. Prepared by Artem Bykovets, Agile Coach & Process consultant - www.abykovets.com
This presentation introduces agile methodology, talks about scrum and the pros and cons of agile from a various perspectives. It also talks about cost of an agile project
User stories are too often thought of as just another way to gather requirements. That misses the point and can lead us down the path of aimless projects just trying to complete a set of predefined work.
Done right, users stores provide clear business purpose by answering the who, what, and why of specific business problems that should be addressed. In doing so, user stories help flesh out vision and value stream details that improve decision making across the organization and make delivery teams more effective.
Agile is a software development methodology in which the development is carried out iteratively and the requirements evolve through continuous inspection and adaptation. Some of the most commonly used agile software development methods/frameworks are: Adaptive Software Development (ASD), Extreme Programming (XP), Scrum and Kanban.
Introduction to Agile Software Developmentaboulkheir
What is Agile Software Development?
The Agile Manifesto
The Twelve Principles of Agile Software
Agile Methodologies
Scrum
Extreme Programming (XP)
Lean Software Development
Kanban Software Development
User Story
Definition of Done
Relative Sizing & Story Points
Planning Poker Estimation Technique
Velocity
3 question that will help you strategies your release planning Anat (Alon) Salhov
This talk was presented as part of Agile Testing Days 2018.
In this session I am focusing on the 3 questions that will help you prioritize the user stories, and by that enable you to control the release.
Please contact me for questions
In this Meetup we discussed on the following topics:
What is the difference between a facilitator and coach?
We discussed on different situation from life, and which tool (facilitator or coaching) should be used?
Why does it matter?
The simulation displays the scrum board over 7 working days iteration. It emphasizes the difference between the information that can be derived from the Scrum board based mainly on intuition (and can be misleading) vs. The information that can be derived from the burn down chart based on empirical data, that show us visual trend immediately
You will learn how to set the stage and provide clear boundaries within each ceremony. Heck, this practical knowledge will help you in any meeting, not just Scrum. With this knowledge you will get the team to collaborate with each other and with you.
Target audience: Fresh and experience scrum masters wishing to acquire additional tools and skills and agile coaches leading organizational change.
Hybrid optimization of pumped hydro system and solar- Engr. Abdul-Azeez.pdffxintegritypublishin
Advancements in technology unveil a myriad of electrical and electronic breakthroughs geared towards efficiently harnessing limited resources to meet human energy demands. The optimization of hybrid solar PV panels and pumped hydro energy supply systems plays a pivotal role in utilizing natural resources effectively. This initiative not only benefits humanity but also fosters environmental sustainability. The study investigated the design optimization of these hybrid systems, focusing on understanding solar radiation patterns, identifying geographical influences on solar radiation, formulating a mathematical model for system optimization, and determining the optimal configuration of PV panels and pumped hydro storage. Through a comparative analysis approach and eight weeks of data collection, the study addressed key research questions related to solar radiation patterns and optimal system design. The findings highlighted regions with heightened solar radiation levels, showcasing substantial potential for power generation and emphasizing the system's efficiency. Optimizing system design significantly boosted power generation, promoted renewable energy utilization, and enhanced energy storage capacity. The study underscored the benefits of optimizing hybrid solar PV panels and pumped hydro energy supply systems for sustainable energy usage. Optimizing the design of solar PV panels and pumped hydro energy supply systems as examined across diverse climatic conditions in a developing country, not only enhances power generation but also improves the integration of renewable energy sources and boosts energy storage capacities, particularly beneficial for less economically prosperous regions. Additionally, the study provides valuable insights for advancing energy research in economically viable areas. Recommendations included conducting site-specific assessments, utilizing advanced modeling tools, implementing regular maintenance protocols, and enhancing communication among system components.
Event Management System Vb Net Project Report.pdfKamal Acharya
In present era, the scopes of information technology growing with a very fast .We do not see any are untouched from this industry. The scope of information technology has become wider includes: Business and industry. Household Business, Communication, Education, Entertainment, Science, Medicine, Engineering, Distance Learning, Weather Forecasting. Carrier Searching and so on.
My project named “Event Management System” is software that store and maintained all events coordinated in college. It also helpful to print related reports. My project will help to record the events coordinated by faculties with their Name, Event subject, date & details in an efficient & effective ways.
In my system we have to make a system by which a user can record all events coordinated by a particular faculty. In our proposed system some more featured are added which differs it from the existing system such as security.
Automobile Management System Project Report.pdfKamal Acharya
The proposed project is developed to manage the automobile in the automobile dealer company. The main module in this project is login, automobile management, customer management, sales, complaints and reports. The first module is the login. The automobile showroom owner should login to the project for usage. The username and password are verified and if it is correct, next form opens. If the username and password are not correct, it shows the error message.
When a customer search for a automobile, if the automobile is available, they will be taken to a page that shows the details of the automobile including automobile name, automobile ID, quantity, price etc. “Automobile Management System” is useful for maintaining automobiles, customers effectively and hence helps for establishing good relation between customer and automobile organization. It contains various customized modules for effectively maintaining automobiles and stock information accurately and safely.
When the automobile is sold to the customer, stock will be reduced automatically. When a new purchase is made, stock will be increased automatically. While selecting automobiles for sale, the proposed software will automatically check for total number of available stock of that particular item, if the total stock of that particular item is less than 5, software will notify the user to purchase the particular item.
Also when the user tries to sale items which are not in stock, the system will prompt the user that the stock is not enough. Customers of this system can search for a automobile; can purchase a automobile easily by selecting fast. On the other hand the stock of automobiles can be maintained perfectly by the automobile shop manager overcoming the drawbacks of existing system.
Welcome to WIPAC Monthly the magazine brought to you by the LinkedIn Group Water Industry Process Automation & Control.
In this month's edition, along with this month's industry news to celebrate the 13 years since the group was created we have articles including
A case study of the used of Advanced Process Control at the Wastewater Treatment works at Lleida in Spain
A look back on an article on smart wastewater networks in order to see how the industry has measured up in the interim around the adoption of Digital Transformation in the Water Industry.
Water scarcity is the lack of fresh water resources to meet the standard water demand. There are two type of water scarcity. One is physical. The other is economic water scarcity.
Quality defects in TMT Bars, Possible causes and Potential Solutions.PrashantGoswami42
Maintaining high-quality standards in the production of TMT bars is crucial for ensuring structural integrity in construction. Addressing common defects through careful monitoring, standardized processes, and advanced technology can significantly improve the quality of TMT bars. Continuous training and adherence to quality control measures will also play a pivotal role in minimizing these defects.
Final project report on grocery store management system..pdfKamal Acharya
In today’s fast-changing business environment, it’s extremely important to be able to respond to client needs in the most effective and timely manner. If your customers wish to see your business online and have instant access to your products or services.
Online Grocery Store is an e-commerce website, which retails various grocery products. This project allows viewing various products available enables registered users to purchase desired products instantly using Paytm, UPI payment processor (Instant Pay) and also can place order by using Cash on Delivery (Pay Later) option. This project provides an easy access to Administrators and Managers to view orders placed using Pay Later and Instant Pay options.
In order to develop an e-commerce website, a number of Technologies must be studied and understood. These include multi-tiered architecture, server and client-side scripting techniques, implementation technologies, programming language (such as PHP, HTML, CSS, JavaScript) and MySQL relational databases. This is a project with the objective to develop a basic website where a consumer is provided with a shopping cart website and also to know about the technologies used to develop such a website.
This document will discuss each of the underlying technologies to create and implement an e- commerce website.
COLLEGE BUS MANAGEMENT SYSTEM PROJECT REPORT.pdfKamal Acharya
The College Bus Management system is completely developed by Visual Basic .NET Version. The application is connect with most secured database language MS SQL Server. The application is develop by using best combination of front-end and back-end languages. The application is totally design like flat user interface. This flat user interface is more attractive user interface in 2017. The application is gives more important to the system functionality. The application is to manage the student’s details, driver’s details, bus details, bus route details, bus fees details and more. The application has only one unit for admin. The admin can manage the entire application. The admin can login into the application by using username and password of the admin. The application is develop for big and small colleges. It is more user friendly for non-computer person. Even they can easily learn how to manage the application within hours. The application is more secure by the admin. The system will give an effective output for the VB.Net and SQL Server given as input to the system. The compiled java program given as input to the system, after scanning the program will generate different reports. The application generates the report for users. The admin can view and download the report of the data. The application deliver the excel format reports. Because, excel formatted reports is very easy to understand the income and expense of the college bus. This application is mainly develop for windows operating system users. In 2017, 73% of people enterprises are using windows operating system. So the application will easily install for all the windows operating system users. The application-developed size is very low. The application consumes very low space in disk. Therefore, the user can allocate very minimum local disk space for this application.
Democratizing Fuzzing at Scale by Abhishek Aryaabh.arya
Presented at NUS: Fuzzing and Software Security Summer School 2024
This keynote talks about the democratization of fuzzing at scale, highlighting the collaboration between open source communities, academia, and industry to advance the field of fuzzing. It delves into the history of fuzzing, the development of scalable fuzzing platforms, and the empowerment of community-driven research. The talk will further discuss recent advancements leveraging AI/ML and offer insights into the future evolution of the fuzzing landscape.
Forklift Classes Overview by Intella PartsIntella Parts
Discover the different forklift classes and their specific applications. Learn how to choose the right forklift for your needs to ensure safety, efficiency, and compliance in your operations.
For more technical information, visit our website https://intellaparts.com
Saudi Arabia stands as a titan in the global energy landscape, renowned for its abundant oil and gas resources. It's the largest exporter of petroleum and holds some of the world's most significant reserves. Let's delve into the top 10 oil and gas projects shaping Saudi Arabia's energy future in 2024.
Courier management system project report.pdfKamal Acharya
It is now-a-days very important for the people to send or receive articles like imported furniture, electronic items, gifts, business goods and the like. People depend vastly on different transport systems which mostly use the manual way of receiving and delivering the articles. There is no way to track the articles till they are received and there is no way to let the customer know what happened in transit, once he booked some articles. In such a situation, we need a system which completely computerizes the cargo activities including time to time tracking of the articles sent. This need is fulfilled by Courier Management System software which is online software for the cargo management people that enables them to receive the goods from a source and send them to a required destination and track their status from time to time.
7. What are we going to cover today?
TABLE OF CONTENTS
What is Lean Thinking?
What is Agile?
What is scrum?
What are the roles in scrum?
What is the manager role within
agile environment?
What is the meaning of each
ceremony in scrum?
8. “It ain’t what you don’t know
that gets you into troubles.
It’s what you know for sure
that just ain’t so”
Mark Twain
WHAT WE THOUGHT VS. WHAT WE KNOW
11. WINSTON W. ROYCE 1970
"I believe in this
concept, but the
implementation
described above is
risky and invites
failure"
12. 01
WHAT WE
KNOW
The harder we plan and
analyze in the beginning,
the less there’s change in
the project and the more
successful the project
WHAT WE
THOUGHT
13. WHAT WE
THOUGHT
01
WHAT WE
KNOW
There is change always
and responding to it is vital.
Uncertainty is best reduced
by learning from actual
implementation
14. 02
WHAT WE
KNOW It is possible to “collect” or
even “know” all the
requirements up-front
It’s possible to transfer
information effectively on
written documents without
much of human contact
WHAT WE
THOUGHT
15. 02
WHAT WE
KNOW
Requirements evolve as
customers and our
knowledge increases –
based on experience
Essential knowledge is
lost in every handover
and human interaction is
needed to overcome it.WHAT WE
THOUGHT
16. 03
WHAT WE
KNOW
Division of work to
specialized teams
(specification, design and
testing) is efficient
WHAT WE
THOUGHT
26. Agile Principle 1-4
1. Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software
27. Agile Principle 1-4
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
28. Agile Principle 1-4
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
29. Agile Principle 1-4
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
30. Agile Principle 5-8
5. Build project around motivated individuals. Give them the
environment and support they need, and trust them to get the
job done
31. Agile Principle 5-8
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
32. Agile Principle 5-8
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
7. Working software is the primary measure for progress
33. Agile Principle 5-8
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
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
34. Agile Principle 9-12
9. Continuous attention to technical excellence and good
design enhances agility
35. Agile Principle 9-12
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
36. Agile Principle 9-12
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
37. Agile Principle 9-12
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
40. WHAT IS SCRUM?
"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."
41. THE ORIGIN OF
SCRUM
• Toyota lean concept
• The new, new software
development game
[Takeuchi & Nonaka, 1986]
• Iterative & incremental
development
• Jeff Sutherland
• Ken Schwaber
42. • Understanding that we
cannot predict the future
• One size does not fit all
• Constant improvement
• Transparency & Visibility
• Team work
SCRUM PRINCIPLES
43. • Deliver business value fast
(max. 30 days)
• Prioritizing
• Empirical approach
• Fun !!!
SCRUM PRINCIPLES
46. SCRUM MASTER (SM)
• Scrum - A framework for
managing the development
lifecycle of software products
• Master - A skilled practitioner of
a particular art or activity
• A Scrum master - the leader of
the Scrum process (& team)
47. What does it means
“The leader of the scrum process”?
• Coach the team with Scrum
• Coach the PO with Scrum
• Help Facilitate effective ceremonies
• Helps removing impediments
• Help the team grow
• 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
49. SCRUM TEAM
• Self organizing
• Typically 5-9 people
• Cross functional (Preferably a
feature team)
• Provide estimate for the tasks
• Decides how much it can do
• Decides how to reach the sprint
goal (within the project’s boundaries)
• The team is responsible for the
outcomeALL OF US
ARE SMARTER THAN
ANY OF US
50. PRODUCT OWNER (PO)
• Defines the features of the product
• Defines release dates and content
• Responsible for ROI
• Prioritizes feature according to value
• Can change features and priority
once every predefined interval
• Decides what will be worked on in
each iteration
• Accepts or rejects results
51. The PO takes an active role throughout the
development lifespan
Traditionally throws content “over the fence”
NO MORE!
CONCEPT CHANGE
52. Product Backlog Refinement = Grooming
The team and the PO together review the backlog in order to
make it ready for the next 2-3 sprints
How?
Grooming = Clarifying, Estimating, and Splitting
Recommended to allocate ~5% of the sprint time
58. Sprint Planning
The first meeting of the sprint
Length: 2-8 hours
Participants: PO, Team, Scrum Master
Preconditions: Product backlog should be in good shape
Divided into two parts
61. To do In progress Done
PBI # 1
PBI # 2
Task Board
62. To do In progress Done
PBI # 1
PBI # 2
Task Board
63. To do In progress Done
PBI # 1
PBI # 2
Task Board
64. To do In progress Done
PBI # 1
PBI # 2
Task Board
65. To do In progress Done
PBI # 1
PBI # 2
Task Board
66. Burndown Chart
A simple visual way of tracking
progress
Used in different levels:
Sprint
Release
Product
Shows the amount of work left to
reach target
69. Every day, Same time, Same place
No longer than 15 minutes
Stand up
All the team must attend
Only team members are allowed to speak
Daily
70. Daily
3 Questions:
1. What have we accomplished since the
last daily
2. What will we accomplish until the next
daily
3. What are my/our impediments
73. Close the sprint
Participants: The team, PO, everyone (managers, customers..)
Inspect & adapt, focus on feedback - this is NOT a Demo
Focus on shard learning - not reporting
Only Done Working Software allowed
Avoid power point presentation
Sprint Review
76. Goal: Inspect and create plan for improvements
Team time tune & adjust
After sprint review - Before sprint planning
Length: 1-2 hours
Participates: Scrum Master and the team (others are optional)
Generate AI (experiments) to execute the following sprint
Sprint Retrospective
Things to Stop doing
Things to start doing
Things to Keep doing
77. Retrospective Model Example
Opening (2-5 minutes)
Data collection (15-25 minutes)
Generate insights (15-25 minutes)
Decide what do do (15-25 minutes)
Closing (2-5 minutes)
