This document provides an introduction to SCRUM, an agile framework for developing software. It discusses the core concepts of SCRUM including roles, events, artifacts, and values. The three main roles are the Product Owner, Development Team, and Scrum Master. Key events in the SCRUM process are the Sprint Planning Meeting, Daily Scrum, Sprint Review, and Sprint Retrospective. Main artifacts include the Product Backlog and Sprint Backlog. The document also covers user stories, estimation techniques, and how a typical SCRUM sprint cycle works.
User Story Writing & Estimation For Testers By Mahesh VaradharajanAgile Testing Alliance
This session aims to introduce the critical aspects of user story formulation like INVEST principle, requirements hierarchy in Agile - with focus on aspects related to Agile Testing, such that it fits into the overall theme of the event. Through an exercise, with Lego blocks, the session will address the following aspects: Testability of user stories and importance of acceptance criteria. Handling NFRs - either as part of acceptance criteria or a new user stories. DoD and accommodating testing efforts as part of user story estimation; Defects as user stories. Dependency management between user stories via story maps.
Talk including Demo for the learning objectives outlined above
User Story Writing & Estimation For Testers By Mahesh VaradharajanAgile Testing Alliance
This session aims to introduce the critical aspects of user story formulation like INVEST principle, requirements hierarchy in Agile - with focus on aspects related to Agile Testing, such that it fits into the overall theme of the event. Through an exercise, with Lego blocks, the session will address the following aspects: Testability of user stories and importance of acceptance criteria. Handling NFRs - either as part of acceptance criteria or a new user stories. DoD and accommodating testing efforts as part of user story estimation; Defects as user stories. Dependency management between user stories via story maps.
Talk including Demo for the learning objectives outlined above
this is the document in PDF format used as documentation for technical seminar on Scrum called as Proffesional Scrum Master which is a certificate on Agile Software development process.
Summarizes how I began to apply the CMMI for Services (CMMI-SVC) to my small company in 2009.
First delivered at the NDIA CMMI Technology Conference in Denver, November 2009. WINNER: Outstanding Presentation, CMMI for Services / Lean / Small Settings Track [CmmiTraining.com]
Explores the underlying reasons why project managers often fear the CMMI, explains that their negative reaction is sometimes justified, and offers practical guidance on how to avoid this undesirable (and unsustainable) state.
First delivered at the NDIA CMMI Technology Conference in Denver, November 2011. [CmmiTraining.com]
Scrum is an efficient framework within which you can develop software with teamwork. It is based on agile principles.
This presentation will help you understand agile development in general and Scrum in specific. You will get familiar with its associated terminology along with appropriate examples.
A compilation of the absolute basics for those who want to know about Agile Methodology with some insights on Scrum. The idea is to give enough to fuel the curiosity to learn more. It might not interest one of he / she is an Agile guru but may I ask for your review / comments / suggestions. I'd love to hear from you all...
this is the document in PDF format used as documentation for technical seminar on Scrum called as Proffesional Scrum Master which is a certificate on Agile Software development process.
Summarizes how I began to apply the CMMI for Services (CMMI-SVC) to my small company in 2009.
First delivered at the NDIA CMMI Technology Conference in Denver, November 2009. WINNER: Outstanding Presentation, CMMI for Services / Lean / Small Settings Track [CmmiTraining.com]
Explores the underlying reasons why project managers often fear the CMMI, explains that their negative reaction is sometimes justified, and offers practical guidance on how to avoid this undesirable (and unsustainable) state.
First delivered at the NDIA CMMI Technology Conference in Denver, November 2011. [CmmiTraining.com]
Scrum is an efficient framework within which you can develop software with teamwork. It is based on agile principles.
This presentation will help you understand agile development in general and Scrum in specific. You will get familiar with its associated terminology along with appropriate examples.
A compilation of the absolute basics for those who want to know about Agile Methodology with some insights on Scrum. The idea is to give enough to fuel the curiosity to learn more. It might not interest one of he / she is an Agile guru but may I ask for your review / comments / suggestions. I'd love to hear from you all...
The Role of a BA on a Scrum Team IIBA Presentation 2010scrummasternz
What is your role as a BA on a Scrum team? How do you fit in? This presentation was given to the IIBA conference in NZ in 2010 by Stephen Reed. Stephen had worked extensively as a BA and moved into using Scrum with multiple teams at a large Insurance company. This experience led to a lot of questions around what the BA should be doing on a Scrum team. This presentation goes some way to listing what worked in the teams Stephen was involved in. The BA role does not change and all the skills of a great BA are necessary still on a great Software Development team, just more focused on being a team member and utilising those skills for the Scrum process of getting working software to the customer with more focus and clarity for the user.
I got a copy of this from the internet, and it was not written by me. yet I found this PPT quite helpful for you to understand the Scrum, so just enjoy it.
This is one of the very best presentations about scrum that I know of and thought it worthwhile to have it up for people to be able to check it out. It's great that the authors went for a Creative Commons license.
Large Language Models and the End of ProgrammingMatt Welsh
Talk by Matt Welsh at Craft Conference 2024 on the impact that Large Language Models will have on the future of software development. In this talk, I discuss the ways in which LLMs will impact the software industry, from replacing human software developers with AI, to replacing conventional software with models that perform reasoning, computation, and problem-solving.
SOCRadar Research Team: Latest Activities of IntelBrokerSOCRadar
The European Union Agency for Law Enforcement Cooperation (Europol) has suffered an alleged data breach after a notorious threat actor claimed to have exfiltrated data from its systems. Infamous data leaker IntelBroker posted on the even more infamous BreachForums hacking forum, saying that Europol suffered a data breach this month.
The alleged breach affected Europol agencies CCSE, EC3, Europol Platform for Experts, Law Enforcement Forum, and SIRIUS. Infiltration of these entities can disrupt ongoing investigations and compromise sensitive intelligence shared among international law enforcement agencies.
However, this is neither the first nor the last activity of IntekBroker. We have compiled for you what happened in the last few days. To track such hacker activities on dark web sources like hacker forums, private Telegram channels, and other hidden platforms where cyber threats often originate, you can check SOCRadar’s Dark Web News.
Stay Informed on Threat Actors’ Activity on the Dark Web with SOCRadar!
Into the Box Keynote Day 2: Unveiling amazing updates and announcements for modern CFML developers! Get ready for exciting releases and updates on Ortus tools and products. Stay tuned for cutting-edge innovations designed to boost your productivity.
TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERRORTier1 app
Even though at surface level ‘java.lang.OutOfMemoryError’ appears as one single error; underlyingly there are 9 types of OutOfMemoryError. Each type of OutOfMemoryError has different causes, diagnosis approaches and solutions. This session equips you with the knowledge, tools, and techniques needed to troubleshoot and conquer OutOfMemoryError in all its forms, ensuring smoother, more efficient Java applications.
Accelerate Enterprise Software Engineering with PlatformlessWSO2
Key takeaways:
Challenges of building platforms and the benefits of platformless.
Key principles of platformless, including API-first, cloud-native middleware, platform engineering, and developer experience.
How Choreo enables the platformless experience.
How key concepts like application architecture, domain-driven design, zero trust, and cell-based architecture are inherently a part of Choreo.
Demo of an end-to-end app built and deployed on Choreo.
How Recreation Management Software Can Streamline Your Operations.pptxwottaspaceseo
Recreation management software streamlines operations by automating key tasks such as scheduling, registration, and payment processing, reducing manual workload and errors. It provides centralized management of facilities, classes, and events, ensuring efficient resource allocation and facility usage. The software offers user-friendly online portals for easy access to bookings and program information, enhancing customer experience. Real-time reporting and data analytics deliver insights into attendance and preferences, aiding in strategic decision-making. Additionally, effective communication tools keep participants and staff informed with timely updates. Overall, recreation management software enhances efficiency, improves service delivery, and boosts customer satisfaction.
OpenFOAM solver for Helmholtz equation, helmholtzFoam / helmholtzBubbleFoamtakuyayamamoto1800
In this slide, we show the simulation example and the way to compile this solver.
In this solver, the Helmholtz equation can be solved by helmholtzFoam. Also, the Helmholtz equation with uniformly dispersed bubbles can be simulated by helmholtzBubbleFoam.
Globus Connect Server Deep Dive - GlobusWorld 2024Globus
We explore the Globus Connect Server (GCS) architecture and experiment with advanced configuration options and use cases. This content is targeted at system administrators who are familiar with GCS and currently operate—or are planning to operate—broader deployments at their institution.
Gamify Your Mind; The Secret Sauce to Delivering Success, Continuously Improv...Shahin Sheidaei
Games are powerful teaching tools, fostering hands-on engagement and fun. But they require careful consideration to succeed. Join me to explore factors in running and selecting games, ensuring they serve as effective teaching tools. Learn to maintain focus on learning objectives while playing, and how to measure the ROI of gaming in education. Discover strategies for pitching gaming to leadership. This session offers insights, tips, and examples for coaches, team leads, and enterprise leaders seeking to teach from simple to complex concepts.
Cyaniclab : Software Development Agency Portfolio.pdfCyanic lab
CyanicLab, an offshore custom software development company based in Sweden,India, Finland, is your go-to partner for startup development and innovative web design solutions. Our expert team specializes in crafting cutting-edge software tailored to meet the unique needs of startups and established enterprises alike. From conceptualization to execution, we offer comprehensive services including web and mobile app development, UI/UX design, and ongoing software maintenance. Ready to elevate your business? Contact CyanicLab today and let us propel your vision to success with our top-notch IT solutions.
Climate Science Flows: Enabling Petabyte-Scale Climate Analysis with the Eart...Globus
The Earth System Grid Federation (ESGF) is a global network of data servers that archives and distributes the planet’s largest collection of Earth system model output for thousands of climate and environmental scientists worldwide. Many of these petabyte-scale data archives are located in proximity to large high-performance computing (HPC) or cloud computing resources, but the primary workflow for data users consists of transferring data, and applying computations on a different system. As a part of the ESGF 2.0 US project (funded by the United States Department of Energy Office of Science), we developed pre-defined data workflows, which can be run on-demand, capable of applying many data reduction and data analysis to the large ESGF data archives, transferring only the resultant analysis (ex. visualizations, smaller data files). In this talk, we will showcase a few of these workflows, highlighting how Globus Flows can be used for petabyte-scale climate analysis.
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
Strategies for Successful Data Migration Tools.pptxvarshanayak241
Data migration is a complex but essential task for organizations aiming to modernize their IT infrastructure and leverage new technologies. By understanding common challenges and implementing these strategies, businesses can achieve a successful migration with minimal disruption. Data Migration Tool like Ask On Data play a pivotal role in this journey, offering features that streamline the process, ensure data integrity, and maintain security. With the right approach and tools, organizations can turn the challenge of data migration into an opportunity for growth and innovation.
Modern design is crucial in today's digital environment, and this is especially true for SharePoint intranets. The design of these digital hubs is critical to user engagement and productivity enhancement. They are the cornerstone of internal collaboration and interaction within enterprises.
Listen to the keynote address and hear about the latest developments from Rachana Ananthakrishnan and Ian Foster who review the updates to the Globus Platform and Service, and the relevance of Globus to the scientific community as an automation platform to accelerate scientific discovery.
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
6. Kent Beck
Mike Beedle
Arie van Bennekum
Alistair Cockburn
Ward Cunningham
Martin Fowler
James Grenning
Jim Highsmith
Andrew Hunt
Ron Jeffries
Jon Kern
Brian Marick
Robert C. Martin
Steve Mellor
Ken Schwaber
Jeff Sutherland
Dave Thomas
21. What is SCRUM?
Scrum is an Agile framework for developing,
delivering and sustaining complex products.
Scrum is Iterative & Incremental method
Scrum is
Lightweight
Simple to understand
Difficult to master
22. What SCRUM Follows
Empirical Process Control theory i.e. knowledge
comes from experience & makes decision based on
what is known.
23. Values of SCRUM
Commitment
Courage
Focus
Openness
Respect
When they are embodied and lived by the Scrum Team,
the Scrum pillars of transparency, inspection, and
adaptation come to life and build trust for everyone.
The Scrum Team members learn and explore those values
as they work with the Scrum roles, events, and artifacts.
25. What is Scrum being used for?
Commercial software
In-house development
Fixed-price projects
Financial applications
ISO 9001-certified applications
24x7 systems with 99.999% uptime requirements
Video game development
US FDA-approved software for X-Rays, MRIs
Satellite-control software
Websites, Mobile phones
Network switching applications
Large database applications
CMMi organizations
Multi-location development
Non-software projects
26. Scrum has been used by-
Microsoft
Yahoo
Google
Electronic Arts
High Moon Studios
Lockheed Martin
Philips
Siemens
Nokia
Capital One
BBC
Intuit
First American Real Estate
BMC Software
Ipswitch
John Deere
Lexis Nexis
Sabre
Salesforce.com
Time Warner
Turner Broadcasting
Oce
Intuit
Nielsen Media
27. Disadvantages of SCRUM
SCRUM is hard!
Makes all dysfunction visible
Scrum doesn’t fix anything: the team has to do it
Feels like things are worse at the beginning
Bad product will be delivered sooner and doomed projects will
fail faster
Some teams and organizations are not right or ready for it
Team willingness, capabilities
Management
Risk of turnover during adoption
Some people will refuse to stay on a Scrum team
Some people will refuse to stay if Scrum is abandoned
Partial adoption may be worse than none at all
28. Foundations of SCRUM
The heart of SCRUM is “Sprint”- a time boxed which are not
extended
There are 02 artifacts, 03 roles, 04 events are closely related with
the Sprint.
30. SCRUM Roles- The Product Owner
Responsible for the overall project vision and goals
Responsible for managing project ROI vs. risk
Responsible for managing Product Backlog
Clearly express the product backlog items
Ordering the items based on their priorities
Ensures backlog items visible, transparent and clear to
all
Ensures development team understands the items of
backlog to the level as needed.
Participates actively in Sprint Planning and Sprint Review
meetings, and is available to team throughout the Sprint
Determines release plan and communicates it to upper
management and the customer
32. SCRUM Roles- The Development Team
Responsible for delivering a potentially releasable
increments of “Done” product at the end of the sprint
Self Organizing
Team manages itself to achieve the Sprint commitment
Cross Functional
All the skills as a team necessary to create a product
Increment
Team takes on tasks based on skills, not just official “role”
Size should be of 6 persons, + or -3
Can be shared with other teams (but better when not)
Can change between Sprints (but better when they don’t)
Can be distributed (but better when co-located)
34. SCRUM Roles- The Scrum Master
Servant-leader for the team.
Does everything to help the team achieve success
including-
Serving the Team
Protecting the Team
Guiding the team’s use of SCRUM
35. Scrum Master- Serving the team
Takes action to help remove impediments to the team’s
effectiveness.
Facilitates the team’s group interactions, to help the team
achieve its full potential
Coaches the team, to help them improve their practices
and effectiveness
36. Scrum Master- Protects the Team
Protects the team from
anything that threatens its
effectiveness, such as
outside interference or
disruption
Deal with uncomfortable
issues, both inside and
outside the team
37. Guiding the team’s use of Scrum
Teaches Scrum to the team and organization
Ensures that all standard Scrum rules and practices are
followed
Organizes all Scrum-related practices
41. Transforming “Project Manager” to …..
There is no such role is scrum where we can have a project
manager.
We need to transform our traditional project managers to
Scrum Master (Highly risk involved as the intention of
managing the team will be there)
Product Owner
Team Member (Hard to adjust as a member of the
team)
44. Product Backlog
Product Owner lists items
in descending order of
priority (highest priority
item is listed first, next-
highest is second, etc.)
Size estimates are rough
estimates (can either be
arbitrary “points”, or
“ideal days”)
45. Product Backlog
List of everything that could ever be of value to the business for the
team to produce
Ranked in order of priority
Priority is a function of business value versus risk
Product Owner can make any changes they want before the start of
a Sprint Planning Meeting
Items added, changed, removed, reordered
How much documentation is up to the team and Product Owner to
decide
The farther down the list, the bigger and less defined the items
become
~2 Sprints worth are defined in detail
46. User Stories
User Stories are a good approach for writing
Product Backlog Items
User Stories are a short, plain-language
description of the functionality, in terms of the
customer benefit and need
47. Good Format of User Stories
As a …..
I want …..
So that …..
48. Examples of well formatted user stories
“As a customer, I can place an item on my wish-
list, so that I can decide later whether or not I
want to buy it”
“As a frequent flyer member, I can see the
number of miles I have earned in my frequent
flyer account, so that I can decide whether to
redeem them for a ticket”
“As a new user, I can set up a profile so that
potential employers can find out more about
my skills and qualifications”
49. Epics
Larger user stories are referred as Epic.
Epics generally take more than one or two
sprints to develop and test. They are usually
broad in scope, short on details, and will
commonly need to be split into multiple,
smaller stories before the team can work on
them.
50. Themes
A theme is a collection of related user stories
A user Story can belong to one or more themes.
An Epic can be sliced into several stories. One way
to remember that all of these sliced stories is
related is to say that they belong to a particular
theme
51. Tasks
An user story can be further sliced further tasks
like-
UI Design
Database Design
Server side Business logic implement
Client side Business logic implement etc.
Tasks are generally contains by “Sprint
Backlog”
52. INVEST in Good Stories and SMART Tasks
Stories should be-
I – Independent
N – Negotiable
V – Valuable
E – Estimable
S – Small
T – Testable
Tasks should be-
S – Specific
M – Measurable
A – Achievable
R – Relevant
T – Time-boxed
53. How to Set the Story point (Est. Size of Story)
Planning Poker
First of all team should agree a story (from backlog
item) as “baseline” or “benchmark” and give it a
size e.g.- 5
Size = Effort x Complexity x Uncertainty
54. How to Set the Story point (Est. Size of Story)
Planning Poker
Team will given / create cards with following
values-
55. How to Set the Story point (Est. Size of Story)
Planning Poker
1. Product owner will pick a story from backlog and ask
the team to estimate it’s size in respect of already
estimated story
2. Each person will decide their cards at the same time. In
this case no one will share his/her number with other.
This is very secret.
3. Everyone will show their card at once when Scrum
Master will says “1-2-3-show”
4. If estimates vary significantly then high and low
estimators will explain briefly why
5. Repeat step 2-4 until estimates stop converging
6. Decided estimates are the size of Backlog item
7. Move to next backlog item
56. How to Set the Story point (Est. Size of Story)
Planning Poker
59. Sprint Planning Meeting
Takes place before the start of every Sprint
Team decides how much Product Backlog it will commit to
complete by the end of the Sprint, and comes up with a plan
and list of tasks for how to achieve it
What’s a good commitment?
Clearly understood by all
Shared among the team
Achievable without sacrificing quality
Achievable without sacrificing sustainable pace
Attended by Team, Product Owner, Scrum Master,
Stakeholders
May require
2 hours for each week of Sprint duration
2 week Sprint = 4 hours,
4 week Sprint = 8 hours
60. Sprint Planning Meeting (Cont.)
Sprint Planning Meeting further divided into two parts-
Sprint Pre-Planning Meeting
Sprint Planning Meeting
Sprint Pre-Planning Meeting
Team understands the details of what the Product
Owner has prioritized on the Product Backlog
Team Set the Size of each Story
Sprint Planning Meeting
Team decides how much productive time it has available
during the Sprint
Team decides how many Product Backlog items it can
commit to complete during the Sprint
61. Sprint Pre-Planning Meeting
Should take place 2-3 days before the actual sprint
planning meeting
Team must understand the prioritized items by product
owner and ask for clarification if required
Provide rough estimation for new items
Calculate team’s available days, hours etc.
The Dev Team, Product Owner, and ScrumMaster look
ahead to upcoming Product Backlog Items (or User Stories)
coming in the next 2-3 Sprints
They split larger items into smaller slices – ideally, small
enough that 1-2 people could completely finish them in 3-4
days (“1-2-3-4”)
They start to get a more detailed understanding of the
requirements for these upcoming Product Backlog Items
No fixed format, timing, or timebox: try a 2-3 hour session
for Dev Team, Product Owner and ScrumMaster
65. Available Hours Per day
Different members can have different responsibilities. Based on those differences
approximate available hour per day calculation-
70. Definition of Done (DoD)
Definition of Done (DoD) has been described as a tool for bringing
transparency to the work a Scrum Team is performing.
It is related more to the quality of a product, rather than its functionality.
The DoD is usually a clear and concise list of requirements that a software
Increment must adhere to for the team to call it complete. Until this list is
satisfied, a product Increment is not done.
During the Sprint Planning meeting, the Scrum Team develops or reconfirms
its DoD, which enables the Development Team to know how much work to
select for a given Sprint.
The Definition of Done is not changed during a Sprint, but should change
periodically between Sprints to reflect improvements the Development Team
has made in its processes and capabilities to deliver software.
74. Creating Sprint Backlog
Team will break an Story into Multiple Tasks
Estimate the effort/time of each task
Here Volunteer means the member who will complete the task.
75. Sprint Planning Ends when…
Team’s available time is mostly committed
Good idea to go through and make sure there’s full
agreement on the commitment
After the meeting, Scrum Master turns the task list into
the Sprint Backlog
78. Daily SCRUM
Purpose of Daily Scrum Meeting
Keep team coordinated and up-to-date with each other
Surface impediments daily
How it works
Every weekday
Whole team attends
Team chooses a time that works for everyone
Product Owner can attend, but doesn’t speak
Everyone stands in a circle, facing each other (not facing the SM)
Lasts 15 minutes or less
Everyone reports 3 things only to each other
What was I able to accomplish since last meeting
What will I try to accomplish by next meeting
What are my blocks / problems / difficulties
No discussion or conversation until meeting ends
81. Update Sprint Backlog
After the Daily Scrum, team members update the
hours remaining on the Sprint Backlog
Also moves cards on the visual task board
82. Update Sprint Backlog
After the Daily Scrum, team members update the
hours remaining on the Sprint Backlog
Also moves cards on the visual task board
83. Update Sprint Backlog
*. Column 1,2,3,4,5,6 indicates days of the sprint.
*. Value of those columns i.e. 4,3,0 etc. indicates how much time remaining to complete
the task.
93. Some important note (About Task Board)
Use sticky paper on a board or use pin and paper on a
soft board so that items are easy to move
Can assign different color for team members, task type or
themes
Should be visible from a sitting position (for everyone)
Item can move forward or backward
Can be customized to have more than 2 columns
95. No Changes During Sprint
No Changes to the Deliverable
Once team has committed, no changes to the
deliverable
If something major comes up, Product Owner can
terminate the Sprint and start new one
Details and clarifications will emerge during Sprint, but
no new work or substantially changed work
Difference between “change” and “clarification”
“If there’s any doubt, then it’s a change
96. What if a change is required?
Do not allow any changes in current sprint
Move the item for next sprint
Break the sprint and start a new sprint with modified
backlog
Product owner should be responsible for breaking the
sprint or removing items from the sprint
99. Sprint Review
Purpose of the Sprint Review
Demo what the team has built
Make visible whether the team completed what they set
out to
Generate feedback, which the Product Owner can
incorporate in the Product Backlog
Attended by Team, Product Owner, ScrumMaster,
functional managers, and any other stakeholders
A demo of what’s been built, not a presentation about
what’s been built
No Power-points allowed!
Usually 4 hours for 4 weeks sprint, 2 hours for 2 weeks, 1
hour for 1 week sprint
101. Sprint Retrospective
Occurs after Sprint Review and prior to next sprint
planning
03 hours meeting for one hour sprint, 1.5 hours for two
weeks sprint, 45 minutes for 1 week sprint
Product Owner, Team and Scrum Master will attended
Generally Scrum Master Facilitate the Meeting but if
possible call Neutral Person to Facilitate the Meeting
Discuss about
What’s working
What’s could better
Things try to next sprint
103. Good approach of Retrospective
Create 03 large list on a whiteboard
What’s working
What’s could work better
Things to try in the next Sprint
Allow each person to add one or more items to the 3 lists
If people agree with something already on the lists then put a
tick mark next to that
Select a subset from “Things to Try” list and try in the next
sprint. (Scrum Master responsible for tracking this)