The document provides a template for conducting a Sprint Review, Retrospective, and Planning meeting. It includes sections for demoing completed work, reviewing work accepted in the previous Sprint, discussing key performance metrics and action items from the prior Retrospective, setting the Sprint goal, and estimating work for the upcoming Sprint.
Getting Started - Introduction to Sprint ReviewsEasy Agile
Overview
- What is a sprint review?
- Benefits of sprint reviews
- Anatomy of a sprint review
- Guidelines for effective sprint review meetings
- conducting sprint reviews using Easy Agile User Story Maps
Getting Started - Introduction to Sprint ReviewsEasy Agile
Overview
- What is a sprint review?
- Benefits of sprint reviews
- Anatomy of a sprint review
- Guidelines for effective sprint review meetings
- conducting sprint reviews using Easy Agile User Story Maps
Ever wonder why Agile teams swear by relative estimation? My teams improved sprint planning efforts by a factor or 3, once we started using relative estimation.
Without understanding Agile relative estimation, teams tend to fall back to using time-based methods. This often leads them to spend way too much time on obsolete estimates that will be made even more complex with all the unknowns and constant emergent requirements of an Agile world!
“It's better to be roughly right, than precisely wrong!”
~ John Maynard Keyenes
The Solution is simple: understand that relative estimation is only a rough order of magnitude estimate to quickly organize the product backlog. This empowers your product owners (PO) to quickly make value based trade-offs on backlog items and decide on what stories the team should work next. This gives the business the highest bang for their buck!
PROBLEMS WITH TIME-BASED ESTIMATES
-Teams spend too much time trying to get it right
-Lack of confidence/experience can lead to people being either optimistic or pessimistic
-Timeline you are estimating may be too far in the future
-Due to long timeline, there are too many risks, unknowns, changes or dependencies!
WHY USE RELATIVE ESTIMATION?
-Allows a quick comparison of stories in the backlog
-Allows you to select a predictable volume of work to do in a sprint
-Uses a simple arbitrary scale
-Allows PO to make trade-offs and take on the most valuable stories next
ESTIMATION TIPS
-Relative points or equivalent Tshirt sizes are used to estimate stories, leveraging the Fibonacci sequence modified for Agile.
-The team estimates the story, not management nor the customer.
-Story estimates account for three things: effort, complexity, and unknowns. Don’t short sell yourself by estimating effort alone, that’s where waterfall projects face issues.
-Remember to estimate all Stories, user stories or technical stories. Even estimate research or discovery spikes.
-Refine your backlog as a team on a continuous basis, to get your stories to meet the Definition of Ready.
-Only pull into your sprint, stories that are refined and estimated.
-Break down stories that are large, into smaller slivers of value to optimize your flow.
-Don’t sweat it if you get it wrong, teams often do early on but improve over time.
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
UPDATE VERSION : https://www.slideshare.net/pmengal/scrum-in-ten-slides-v20-2018
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.
Join BostonPHP and Michael Bourque as he presents the concept of Scrum and shows why so many people are now deploying scrum to their development projects. Michael will take us through the process and talk about how his company, Parametric Technology Inc. (PTC) , is successfully applying Scrum.
Agile metrics: Measure and Improve:
Mattia Battiston (SKY) and David Leach (Reed Online) share their expert views on velocity, agile ROI, reporting and measuring impact.
Sponsored by Wemanity - www.wemanity.com - the agile driving force
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
This slide gives an excellent overview of Agile Planning and Estimation.
Will be really helpful, if presented to a Scrum/Agile Team to understand activities related to Release Planning, Sprint Planning and Estimation
Ever wonder why Agile teams swear by relative estimation? My teams improved sprint planning efforts by a factor or 3, once we started using relative estimation.
Without understanding Agile relative estimation, teams tend to fall back to using time-based methods. This often leads them to spend way too much time on obsolete estimates that will be made even more complex with all the unknowns and constant emergent requirements of an Agile world!
“It's better to be roughly right, than precisely wrong!”
~ John Maynard Keyenes
The Solution is simple: understand that relative estimation is only a rough order of magnitude estimate to quickly organize the product backlog. This empowers your product owners (PO) to quickly make value based trade-offs on backlog items and decide on what stories the team should work next. This gives the business the highest bang for their buck!
PROBLEMS WITH TIME-BASED ESTIMATES
-Teams spend too much time trying to get it right
-Lack of confidence/experience can lead to people being either optimistic or pessimistic
-Timeline you are estimating may be too far in the future
-Due to long timeline, there are too many risks, unknowns, changes or dependencies!
WHY USE RELATIVE ESTIMATION?
-Allows a quick comparison of stories in the backlog
-Allows you to select a predictable volume of work to do in a sprint
-Uses a simple arbitrary scale
-Allows PO to make trade-offs and take on the most valuable stories next
ESTIMATION TIPS
-Relative points or equivalent Tshirt sizes are used to estimate stories, leveraging the Fibonacci sequence modified for Agile.
-The team estimates the story, not management nor the customer.
-Story estimates account for three things: effort, complexity, and unknowns. Don’t short sell yourself by estimating effort alone, that’s where waterfall projects face issues.
-Remember to estimate all Stories, user stories or technical stories. Even estimate research or discovery spikes.
-Refine your backlog as a team on a continuous basis, to get your stories to meet the Definition of Ready.
-Only pull into your sprint, stories that are refined and estimated.
-Break down stories that are large, into smaller slivers of value to optimize your flow.
-Don’t sweat it if you get it wrong, teams often do early on but improve over time.
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
UPDATE VERSION : https://www.slideshare.net/pmengal/scrum-in-ten-slides-v20-2018
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.
Join BostonPHP and Michael Bourque as he presents the concept of Scrum and shows why so many people are now deploying scrum to their development projects. Michael will take us through the process and talk about how his company, Parametric Technology Inc. (PTC) , is successfully applying Scrum.
Agile metrics: Measure and Improve:
Mattia Battiston (SKY) and David Leach (Reed Online) share their expert views on velocity, agile ROI, reporting and measuring impact.
Sponsored by Wemanity - www.wemanity.com - the agile driving force
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
This slide gives an excellent overview of Agile Planning and Estimation.
Will be really helpful, if presented to a Scrum/Agile Team to understand activities related to Release Planning, Sprint Planning and Estimation
This is a short introduction to the practice of Sprint Planning in Scrum. It would be useful for people new to Scrum or Agile. For more, comment or write to read my blog : http://agilediary.wordpress.com/
Creating a backlog of user stories is pretty straight forward but it doesn't help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and plan the project, and how to visualize progress. The traditional backlog is simply too flat and often too long to help you see the bigger picture and make good decisions. User Story Mapping helps simplify all of these common project issues. By adding a third dimension to your backlog, your team will make better decisions about priorities, scope, and planning while improving your ability to visualize progress.
In this practical session I’ll cover the basics of user story mapping before walking you through case studies of how our teams are using this approach and the results we are achieving. I'll show you the before, during, and after pictures from several projects so that you can understand how our maps progress during the projects and how we use them to influence iterative development, promote good decision making, and visualize priorities, plans, scope and progress.
"Agile development consists of a series of interdependent planning and delivery rhythms. These agile rhythms, while quite simple conceptually, have proven to be less simple to implement. Yet this reccurring series of meetings and events delivers the reliable beat which allows teams to find their own agile rhythm. Use the resources below to help you get started with or scale your agile efforts.
While no single publication or presentation delivers all of the ammunition agile teams need to get the rhythm, this set of agile meeting and facilitation checklists offers an easy framework to help guide software development teams through the various agile cycles. We hope you find this step-by-step guide valuable."
Author, VersionOne, Inc
http://www.versionone.com/Resources/
Talk about Drupal 8 as headless solution for challenging web applications. Exploring options using Backbone.js front-end application (with Underscore.js templates, or possibly Mustache/Patternlab), via REST API.
Experiments that have worked for me in the last 7 years playing with Scrum in Agile teams.
The presentation covers 4 key pilars of Scrum:
- Roles: Product Owner, Scrum Master and Development Team.
- Scrum Events: Planning Meeting, Daily Stand-up, Grooming/Refinement, Demo and Retrospective.
- Scrum Artifacts: Product Backlog, User Stories, Definition of Done, Sprint Backlog, Sprint Dashboad.
- Reports: End of Sprint Report, New Sprint Report, Burn-up/Burn-down, Product Report.
The primary metric in an Agile project is whether working software actually exists, and is demonstrably suitable for its intended purpose. This is determined empirically, by demonstration, at the end of every single iteration and product increment
All teams and projects are encouraged to pivot most of their measuring-attention to this fact. All other metrics are subordinate to that objective and the overriding goal of keeping the focus on rapid delivery of quality, working software.
This presentation gives you a detailed look at what is in the out of the box templates available in TFS 2013, how they differ, and how that affects some of the ALM tooling.
Software Development Guide To Accelerate PerformanceZaid Shabbir
Scrum is the most widely used framework across all software and business industries. By following complete scrum framework you can improve the quality product deliver in more adaptive way.
Slides contents content guidelines related to scrum framework and how some one become a certified scrum master. Slides elaborate scrum framework by using user friendly diagrams and bulleted points. After grasping the slides any one can easily pass certified scrum examination.
I am sure you will enjoy the contents and its really helpful to become a certified scrum practitioner.
the presentation gives brief description about a methodology of software engineering which is most using software engineering process in today's IT world and helps student to know how a software company runs and build software product using various software engineering methodologies.
This talk is a 101-level introduction to Scrum, the agile methodology, especially in terms of how it works for web development. We'll cover the scrum values, rituals, and team. We'll also discuss some common pitfalls and how to work around them.
A small presentation by Ashley-Christian Hardy on the basics of Scrum methodology, covering the basics of roles & responsibilities, events & ceremonies and scrum artefacts.
Similar to Sprint Review and Planning Template (20)
Farmers, Shields and Money: An Iterative Approach to the Rise of the Greek PolisMike Lally
Slides for a presentation I did at SUNY Empire State College's 2014 Student Academic Conference. I review the "Hoplite Debate" by looking at the work of Victor Davis Hanson, Hans Van Wees, and John R. Hale. Each debates the significance the role Greek Hoplites played in the beginnings of democracy in Ancient Greece. I try to synthesize the points of contention in an iterative approach.
Further Examination of the Hoplite DebateMike Lally
This is a paper I wrote for a class in Ancient Greek History. This is a continuation of the theme I explored in "A Proposed Alternative to the Hoplite Debate." I examine the thesis of John R. Hall in Donald Kagan's "Men of Bronze." I filter the thesis through Kagan's definition of the debate points and conclude by incorporating Hall's thesis (that hoplites emerged from Greek mercenaries) into my own iterative model.
A Proposed Alternative to the Hoplite DebateMike Lally
This is a paper I wrote for a class in Ancient Mediterranean History. I examine the "hoplite debate" as described by Donald Kagan in "Men of Bronze" and recommend an alternative approach that combines the points of the orthodox and revisionists.
Using social media_in_your_job_search_v4_2_sepMike Lally
Latest version of a presentation that walks through both using social media in your job search and using social media to manage your career and online reputation.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
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!
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
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.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
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.
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.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
Sprint Review and Planning Template
1. Sprint Review and Planning Meeting
Template
• I am a Scrum Master for multiple Scrum Teams
• I use the following template to guide the teams through
• Sprint Review/Demo/Retrospective
• Sprint Planning
• I show a couple of reporting views to encourage reflection
and conversation
• I share the completed deck with the teams once we have
completed Sprint Planning
3. Project Review/Demo
• Demos
• Nothing is too small to demo!
• Doesn’t have to be a software demonstration
• New functionality demo 1
• New functionality demo 2
• Updated UI demo 1
• Monitoring demo 1
4. Work Accepted
• I will export a list of work accepted from Rally and include
it here
• I do this just to document the Development Team’s work
effort
5. Sprint Retrospective
• How Are We Doing KPIs
• Performance: Velocity over Time
• Performance: Release Burnup
• Performance: Work Accepted
• Planning: Planned Velocity vs. Actual Velocity
• Quality: Rolling 30-day Defect Trend
6. Velocity Over Time
100% Accepted - 95 out of 95 points.
Last 3 Average: 96 points
Best 3 Average: 117 points
0
20
40
60
80
100
120
140
52
92
104.5
65
115
130.5
102
122
Q1 Velocity
7. Q1 Release Burnup
35
87
179
283.5
348.5
463.5
632
734
856
400
500
600
700
800
850 856 856 856
0
100
200
300
400
500
600
700
800
900
December
1st Half
2012
January 1st
Half 2013
January 2nd
Half 2013
February 1st
Half 2013
February
2nd Half
2013
March 1st
Half 2013
Q1 Pre-
Release
Cycle
April 2nd
Half 2013
May 1st Half
2013
Q1 Release Burnup
14. Sprint Goal
• On this slide I will call out the goal of the sprint.
• Or the top goals of the sprint. Many times we will have 2-3 main
user stories or defect fixes that we are working.
• I find it provides a little bit of help with team focus.
15. Sprint Planning
• We will assign points to ALL user stories and defects
• EVERY we pull into a sprint defect will get a minimum of 3
points