The document discusses various techniques for agile planning including estimating story sizes using planning poker, estimating velocity based on prior iterations, prioritizing stories based on value, cost, risk and new knowledge, and creating a release plan by selecting stories and estimating a release date based on estimated velocity. It cautions that estimates are not commitments and provides tips for splitting large stories and combining planning at both the release and sprint levels.
Business valueiIs a conversation_kent-mcdonald_#bddxnyWendy Devolder
Kent McDonald explains how Business Value is a conversation, not a number, at the Agile Testing & BDD eXchange in New York (Oct 1sr 2012). Find this and other presentations at this conference her:
http://skillsmatter.com/event/agile-testing/agile-testing-and-bdd-exchange-nyc/wd-23
A talk by David Lowe and James Wyllie delivered at Agile on the Beach, Falmouth, on 3 September 2015. The talk covered a variety of approaches to estimate and forecast, including planning poker, Kanban metrics, calibration, Student's t-statistic and Monte Carlo simulations.
Business valueiIs a conversation_kent-mcdonald_#bddxnyWendy Devolder
Kent McDonald explains how Business Value is a conversation, not a number, at the Agile Testing & BDD eXchange in New York (Oct 1sr 2012). Find this and other presentations at this conference her:
http://skillsmatter.com/event/agile-testing/agile-testing-and-bdd-exchange-nyc/wd-23
A talk by David Lowe and James Wyllie delivered at Agile on the Beach, Falmouth, on 3 September 2015. The talk covered a variety of approaches to estimate and forecast, including planning poker, Kanban metrics, calibration, Student's t-statistic and Monte Carlo simulations.
A part of my Product Owner Training Program covering to different approaches on Financial Prioritization:
1- Agile Estimating and Planning by Mike Conh (Ch. 10)
2.- AgileEVM
Take that presentation as just a information material.
In real life, this has to be adapted to customer's/business needs.
Cheers
Pierre
Scrum is one of the leading agile software development processes. Over 12,000 project managers have become certified to run Scrum projects . Since its origin on Japanese new product development projects in the 1980s, Scrum has become recognized as one of the best project management frameworks for handling rapidly changing or evolving projects. Especially useful on projects with lots of technology or requirements uncertainty, Scrum is a proven, scalable agile process for managing software projects.
Through lecture, discussion and exercises, this fast-paced tutorial covers the basics of what you need to know to get started with Scrum. You will learn about all key aspects of Scrum including product and sprint backlog, the sprint planning meeting, the sprint review, conducting a sprint retrospective, activities that occur during sprints, measuring and monitoring progress, and scaling Scrum to work with large and distributed teams. Also covered are the roles and responsibilities of the ScrumMaster, the product owner, and the Scrum team.
This session will be equally suited for managers, programmers, testers, product managers and anyone else interested in improving product delivery.
Presentatie van Hans Korbee van Agentschap NL tijdens
Netwerkbijeenkomst 23 mei 2012
Platform binnenluchtkwaliteit basisscholen in Gelderland
Provinciehuis, Noordgalerij, Arnhem 9:00-14:00 uur
Presentation to Libraries, MOOCs and online learning ALIA,CAUL, OCLC and State Library of Queensland Symposium. https://www.alia.org.au/events/2348/libraries-moocs-and-online-learning
Laura Leichum: "Lessons from Inside the Digital Silo," for the "E-book Nuts a...Krista Coulson
"Lessons from Inside the Digital Silo"
Laura Leichum's (Intellectual Property Manager, Georgetown University Press) presentation for the 2012 AAUP panel "E-book Nuts and Bolts"
A part of my Product Owner Training Program covering to different approaches on Financial Prioritization:
1- Agile Estimating and Planning by Mike Conh (Ch. 10)
2.- AgileEVM
Take that presentation as just a information material.
In real life, this has to be adapted to customer's/business needs.
Cheers
Pierre
Scrum is one of the leading agile software development processes. Over 12,000 project managers have become certified to run Scrum projects . Since its origin on Japanese new product development projects in the 1980s, Scrum has become recognized as one of the best project management frameworks for handling rapidly changing or evolving projects. Especially useful on projects with lots of technology or requirements uncertainty, Scrum is a proven, scalable agile process for managing software projects.
Through lecture, discussion and exercises, this fast-paced tutorial covers the basics of what you need to know to get started with Scrum. You will learn about all key aspects of Scrum including product and sprint backlog, the sprint planning meeting, the sprint review, conducting a sprint retrospective, activities that occur during sprints, measuring and monitoring progress, and scaling Scrum to work with large and distributed teams. Also covered are the roles and responsibilities of the ScrumMaster, the product owner, and the Scrum team.
This session will be equally suited for managers, programmers, testers, product managers and anyone else interested in improving product delivery.
Presentatie van Hans Korbee van Agentschap NL tijdens
Netwerkbijeenkomst 23 mei 2012
Platform binnenluchtkwaliteit basisscholen in Gelderland
Provinciehuis, Noordgalerij, Arnhem 9:00-14:00 uur
Presentation to Libraries, MOOCs and online learning ALIA,CAUL, OCLC and State Library of Queensland Symposium. https://www.alia.org.au/events/2348/libraries-moocs-and-online-learning
Laura Leichum: "Lessons from Inside the Digital Silo," for the "E-book Nuts a...Krista Coulson
"Lessons from Inside the Digital Silo"
Laura Leichum's (Intellectual Property Manager, Georgetown University Press) presentation for the 2012 AAUP panel "E-book Nuts and Bolts"
This ppt.is presented by J. V. Ravichandran (Group Manager in JK Technosoft Ltd.) at Agile NCR 2009 Conference held on 18th July at Park Premier Hotel.
Room to Breathe: The BA's role in project estimationufunctional
What's the Business Analyst's role in project estimation?
According to this presentation, it's "Getting the project through the Hot Zone, with Room to Breathe."
Room to Breathe means enough time for the team and project manager to deal with the remaining uncertainty as it comes up.
The Hot Zone starts when up-front requirements and planning are yielding diminishing returns, the pressure to commit to a plan is mounting, and there's still more than about 25% uncertainty in the estimate.
The difference between a requirements gatherer and a Business Analyst is that a BA provides great decision support, and the estimation problem is at the heart of that.
Every year, software companies spend a huge amount of time and effort estimating large projects, and still end up regularly missing the mark - often by huge amounts. What the heck is going on? With all of the planning poker, and PI planning, and #noestimates, why isn't this figured out yet?
In this talk, we'll dive into probability theory and psychology to discover some of the common underlying causes for a lack of predictability. Once we understand why the world is so uncertain, we'll talk about how we can live with our estimation failures, while still thrilling our customers and maintaining enough predictability to succeed as an organization.
I've spent the last years modelling complex businesses and Software Architectures with EventStorming. The original recipe evolved a lot from the initial one. This is EventStorming state of the art.
Agile metrics can be used to the advantage or the detriment of teams and an organisation’s Agile success. This session looks at several of the core Agile metrics used to measure success to help you understand what success looks like, why the metric is desirable and what the metrics can tell us.
Understanding why we want these metrics is critical to capturing something of value, rather than just doing 'because'. What will leaders and decision makers do with these metrics? What value do they add?
Steve will also dive into the negative impacts of some of the Agile metrics we are sometimes forced to capture, how chasing velocity leads to gaming the system etc. He’ll look at bad metrics such as the seven deadly sins of Agile measurement and how to avoid them in your enterprise.
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
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
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.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
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.
4. why plan?
Reduce Risk
Reduce Uncertainty
Support Better Decision Making
Establish Trust
Convey Information
5. what Makes a good plan?
Sufficiently reliable for making decisions.
6. what makes planning agile?
Focused more on planning than the plan
Encourages changes
Results in plans that are easily changed
Is spread throughout the project
7. Planning statistics
60% of projects significantly over run their
cost estimates
64% of features features included in
products are rarely or never used
The average project exceeds it’s estimate
by 100%
8. planning by activity instead of feature
Activities don’t finish early
Parkinson’s Law states “Work expands so as to fill the
time available for its completion”
Lateness is passed down the schedule
Activities are not independent
9. additional traps we fall into
Multitasking causes further delays
Features are not developed by priority
We ignore uncertainty
Integrum Tip:
Don’t split people among multiple
projects.
Small iterations combat
uncertainty.
10. the manifesto says...
Individuals and Interactions over Process and Tools
Working Software over Comprehensive Documentation
Customer Collaboration over Contract Negotiation
Responding to Change over Following a Plan
11. an agile approach
Work as one team
Work in short iterations
Deliver something each iteration
Focus on business priorities
Inspect and adapt
13. release planning
Define
Conditions
of Select
Satisfaction Iteration
Length
Generate Select
Estimate
User Stories
User Stories
Stories Estimate Release Date
Velocity
Prioritize
User
Stories
16. estimate stories
Estimate gets to cost and time
Not necessary to estimate everything always
17. estimates are Not commitments
An estimate is a probability
Commitment can’t be made on probability
Commitments are made to dates
Estimates are not implicit commitments
18. estimates are shared
Not done by “expert” individual
We don’t know WHO will do the work
Those not doing the work still have the
ability to call bullshit
19. estimation scales
1, 2, 3, 5, 8 and 13
Fibonacci reflects the proportional uncertainty to
estimate the further from the smallest you are.
1, 2, 4, 8 and 16
Still reflects non-linear pattern that highlights great
uncertainty the further you get from the smallest.
25. planning poker
Combines all three methods
Quick but reliable
Right amount of discussion (< 2 min)
Smaller sessions
Before project starts and within project
26. Workshop #1
In teams of 3 to 4 estimate (size) the following water
vessels: row boat, canoe, speed boat, freight liner, cruise
ship, yacht, sail boat using planning poker.
20m
Activity Time
28. epics & Themes
Blocks of Epics/Themes
Bigger numbers with same non-linear seq
More uncertainty
More likely estimates inaccurate
29. Why ideal days?
Easier to explain outside team
Easier to estimate at first (?)
30. Why story points?
Help drive cross-functional behavior
Do not decay
Pure measure of size
Typically faster to obtain estimate
My ideal day is not your ideal day
32. when not to re-estimate
Relativity is right, velocity wrong.
Adjust velocity. Recalculate release.
33. when to re-estimate
Relativity is wrong
ex: API difficult to work with
Adjust stories with API work
34. re-estimate partially completed stories
No such thing as partially completed!
Should only happen if so bad can’t be
completed in next 2 iterations
Probably better to decompose and
estimate decomposed stories
35. select iteration length
Shorter times tightens feedback loops
Shorter times can feel like more overhead
Longer times can be more comforting
39. prioritize stories
Too little time, too many features
Helps with decision making
Helps reduce churn
40. factors in prioritization
The financial VALUE of having
The COST of developing/supporting
The amount/significance of NEW
KNOWLEDGE
The amount of RISK removed
42. Cost
Cost can change depending on when
Can convert points to money
43. new knowledge
High Low High Low
High High
End Uncertainty
End Uncertainty
(What)
(What)
Low Low
Means Uncertainty Means Uncertainty
(How) (How)
44. Risk
High High
High risk High risk
Avoid Do first
Low value High value
Risk
Risk
Low risk Low risk
Do Last Do Second
Low value High value
Low Low
Low Value High Low Value High
45. financial value
Net Present Value
Internal Rate of Return
Payback Period
Discounted Payback Period
59. prioritizing desirability
Hotel Features
Must Haves: Exciting:
a bed built-in TV’s on treadmills
a bathroom free bottled water in room
a desk free hi-speed internet
clean
The More, the Better:
comfort of the bed
size of room
variety of equip in fitness room
60. kano model
Threshold, or must-have, features
Linear features
Exciters and delighters
61. kano customer
High
Customer Satisfaction
Exciters and
delighters
r
ea
lin
c e/ Must-have,
an Mandatory
rm
fo
Implemented
r
Pe
Low
Fully
Absent
Feature Presence
66. Workshop #2
In teams of 3 to 4 prioritize the provided backlog using
by value, cost, new knowledge, risk removed and
desirability utilizing the methods show today.
45m
Activity Time
67. select stories and date
Feature driven.. Stories determines date
Date driven.. Date determines features
Can be detailed by iteration
Can be vague by iteration
68. release planning
Helps product owner and whole team
decide how long until release of product
Conveys expectations about what will be
developed
Serves as a guidepost towards progress
70. when to split a story
Too large to fit in an iteration
Won’t fit in an iteration
Story is Epic (needs better estimate)
71. splitting across data
Split stories along the boundaries of the
data supported by the story
Split exceptions or error conditions
72. split on operational
Split large stories based on operations that
are performed within the story ex: search
Split large stories into separate operations
(ex: CRUD)
74. don’t meet performance constraints
Consider splitting a large story by
separating the functional and non functional
aspects into separate stories.
“Make it work. Then make it work faster.”
75. mixed priorities
Separate a large story into smaller stories if
the smaller stories hae different priorities.
76. don’t split into tasks
Don’t split a large story into tasks.
ex: Not UI, Model, Controller, View Story
Use tracer bullets
77. avoid temptation of related changes
Don’t add related changes
Unless related changes equivalent priority
“While I’m in that code...”
Only makes it worse
78. combining stories
It’s okay to combine smaller stories
Use caution and keep things managable
79. Workshop #2
In teams of 3 to 4 create a release plan using velocity.
20m
Activity Time