Introduction to Agile Estimation & PlanningAmaad Qureshi
Presented by Natasha Hill & Amaad Qureshi
In this session, we will be covering the techniques of estimating Epics, Features and User Stories on an Agile project and then of creating iteration and release plans from these artefacts.
Agenda
1. Why traditional estimation approaches fail
2. What makes a good Agile Estimating and Planning approach.
3. Story points vs. Ideal Days
4. Estimating product backlog items with Planning Poker
5. Iteration planning - looking ahead and estimating no more than a few week ahead.
6. Release planning - creating a longer term plan, typically looking ahead, 3-6 months
7. Q&A
This presentation discusses the following:
What is an estimate?
What are the factors influencing estimating?
How are agile projects estimated?
How Agile estimation solves common estimation problems?
Agile Estimating & Planning by Amaad QureshiAmaad Qureshi
An introduction to Agile Estimating and how it can be used to measure the size and length of work.
Agile estimating & planning is a way of measuring the size and time it takes to complete a task. This technique is used by Agile teams in Enterprise and can be utilised in the same way by Start-ups not just for software but for all areas of the business. In this talk I will show you how estimating & planning works by:
- Writing effective user stories
- Writing tests to validate stories (acceptance criteria)
- Using story points to work out the size of a task
- Estimating using Planning Poker
- Using Story Points to calculate a team’s velocity (speed of work)
- Using a team’s velocity to calculate project length
Introduction to Agile Estimation & PlanningAmaad Qureshi
Presented by Natasha Hill & Amaad Qureshi
In this session, we will be covering the techniques of estimating Epics, Features and User Stories on an Agile project and then of creating iteration and release plans from these artefacts.
Agenda
1. Why traditional estimation approaches fail
2. What makes a good Agile Estimating and Planning approach.
3. Story points vs. Ideal Days
4. Estimating product backlog items with Planning Poker
5. Iteration planning - looking ahead and estimating no more than a few week ahead.
6. Release planning - creating a longer term plan, typically looking ahead, 3-6 months
7. Q&A
This presentation discusses the following:
What is an estimate?
What are the factors influencing estimating?
How are agile projects estimated?
How Agile estimation solves common estimation problems?
Agile Estimating & Planning by Amaad QureshiAmaad Qureshi
An introduction to Agile Estimating and how it can be used to measure the size and length of work.
Agile estimating & planning is a way of measuring the size and time it takes to complete a task. This technique is used by Agile teams in Enterprise and can be utilised in the same way by Start-ups not just for software but for all areas of the business. In this talk I will show you how estimating & planning works by:
- Writing effective user stories
- Writing tests to validate stories (acceptance criteria)
- Using story points to work out the size of a task
- Estimating using Planning Poker
- Using Story Points to calculate a team’s velocity (speed of work)
- Using a team’s velocity to calculate project length
Agile Patterns: Agile Estimation
We’re agile, so we don’t have to estimate and have no deadlines, right? Wrong! This session will consist of review of the problem with estimation in projects today and then an overview of the concept of agile estimation and the notion of re-estimation. We’ll learn about user stories, story points, team velocity, how to apply them all to estimation and iterative re-estimation. We will take a look at the cone of uncertainty and how to use it to your advantage. We’ll then take a look at the tools we will use for Agile Estimation, including planning poker, Visual Studio Team System, and much more. This is a very interactive session, so bring a lot of questions!
A couple years ago, a company I was working with, asked me to share with them the use cases and benefits of Scrum. It must have really sparked the management’s interest as they asked me to come up with an Agile implementation strategy for the company. This is the presentation I would like to share with you as I believe many curious, mid size, web development shops out there might be seriously thinking about adopting Agile or some hybrid form to supplement their Waterfall process.
Updated with latest version as presented at the Canberra Agile & Scrum meetup on July 20, 2017. Previously titled "Using Agile techniques to manage risk more effectively".
Given that the "Waterfall" process model has been dominant in the IT industry for many decades, how many IT and project management professionals are aware that it's inventor warned the world in 1970 that Waterfall is "risky and invites failure"?
From a risk management perspective, is waterfall ever an appropriate choice for complex IT initiatives given what we know now?
In this session we will outline how, as a risk management strategy, using the waterfall model for non-trivial systems development initiatives is systemically high risk as compared with the Iterative Incremental Development (IID) model that has been used in pockets of the IT industry since the late 1950's. Today, many organisations use the IID strategy under the umbrella term of 'Agile'. The majority of these employ Lean Product Development patterns that were first described in the Harvard Business Review in 1986 using a metaphor borrowed from the game of rugby i.e. 'Scrum'.
If you are not using a disciplined agile approach, are you facing more risk as you approach a high-stakes deadline than you need to?
The varied contexts that we work in come with varied types of risk. For a green fields date-driven release, the primary risk may be cost and schedule related. For teams designing a new product for an emerging market, the primary risks may be business risk. For teams doing innovative R&D, the primary risk may technical risk. For a young team in a new technical or business domain, the primary risk may be social risk. In this session, we will use real world examples of such varied challenges to illustrate how risk-tuned Agile helped us to manage risk effectively.
Whilst we will always have to deal with risk to create value, the good news is that there are now many powerful risk management techniques that can be overlaid on top of IID to tune your development process to the type of risk you face. The question is: which ones are most appropriate for the type of risk you are facing? In this workshop we outline a series of powerful risk management tools that tune an agile development process to effectively manage the type of risk that you face.
Introduction to Scrum presentation which outlines common issues in software development, what is Scrum, and an introduction to the Scrum framework. This presentation has been used for training and presentations to both technology and business audiences.
This August Scrum Breakfast, we have a new speaker - Mr. Pedro Gonzalez - Scrum Master at TINYpulse.
He will bring us an interesting topic about Agile estimation using story points, giving some tips on why relative estimations are far better than absolutes, why we shouldn't spend too long in details, and other issues he has experienced himself with his team.
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.
Why estimate user stories using poker planning? What’s the advantage of relative estimation? Why leverage Fibonacci series?
These slides explore the reasons for relative estimation using Fibonacci through a collection of exercises and illustrations.
Slides assume a basic understanding of user stories and poker planning.
Originally presented as an Agile 101 at Agile New England in May 2023.
Agile Patterns: Agile Estimation
We’re agile, so we don’t have to estimate and have no deadlines, right? Wrong! This session will consist of review of the problem with estimation in projects today and then an overview of the concept of agile estimation and the notion of re-estimation. We’ll learn about user stories, story points, team velocity, how to apply them all to estimation and iterative re-estimation. We will take a look at the cone of uncertainty and how to use it to your advantage. We’ll then take a look at the tools we will use for Agile Estimation, including planning poker, Visual Studio Team System, and much more. This is a very interactive session, so bring a lot of questions!
A couple years ago, a company I was working with, asked me to share with them the use cases and benefits of Scrum. It must have really sparked the management’s interest as they asked me to come up with an Agile implementation strategy for the company. This is the presentation I would like to share with you as I believe many curious, mid size, web development shops out there might be seriously thinking about adopting Agile or some hybrid form to supplement their Waterfall process.
Updated with latest version as presented at the Canberra Agile & Scrum meetup on July 20, 2017. Previously titled "Using Agile techniques to manage risk more effectively".
Given that the "Waterfall" process model has been dominant in the IT industry for many decades, how many IT and project management professionals are aware that it's inventor warned the world in 1970 that Waterfall is "risky and invites failure"?
From a risk management perspective, is waterfall ever an appropriate choice for complex IT initiatives given what we know now?
In this session we will outline how, as a risk management strategy, using the waterfall model for non-trivial systems development initiatives is systemically high risk as compared with the Iterative Incremental Development (IID) model that has been used in pockets of the IT industry since the late 1950's. Today, many organisations use the IID strategy under the umbrella term of 'Agile'. The majority of these employ Lean Product Development patterns that were first described in the Harvard Business Review in 1986 using a metaphor borrowed from the game of rugby i.e. 'Scrum'.
If you are not using a disciplined agile approach, are you facing more risk as you approach a high-stakes deadline than you need to?
The varied contexts that we work in come with varied types of risk. For a green fields date-driven release, the primary risk may be cost and schedule related. For teams designing a new product for an emerging market, the primary risks may be business risk. For teams doing innovative R&D, the primary risk may technical risk. For a young team in a new technical or business domain, the primary risk may be social risk. In this session, we will use real world examples of such varied challenges to illustrate how risk-tuned Agile helped us to manage risk effectively.
Whilst we will always have to deal with risk to create value, the good news is that there are now many powerful risk management techniques that can be overlaid on top of IID to tune your development process to the type of risk you face. The question is: which ones are most appropriate for the type of risk you are facing? In this workshop we outline a series of powerful risk management tools that tune an agile development process to effectively manage the type of risk that you face.
Introduction to Scrum presentation which outlines common issues in software development, what is Scrum, and an introduction to the Scrum framework. This presentation has been used for training and presentations to both technology and business audiences.
This August Scrum Breakfast, we have a new speaker - Mr. Pedro Gonzalez - Scrum Master at TINYpulse.
He will bring us an interesting topic about Agile estimation using story points, giving some tips on why relative estimations are far better than absolutes, why we shouldn't spend too long in details, and other issues he has experienced himself with his team.
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.
Why estimate user stories using poker planning? What’s the advantage of relative estimation? Why leverage Fibonacci series?
These slides explore the reasons for relative estimation using Fibonacci through a collection of exercises and illustrations.
Slides assume a basic understanding of user stories and poker planning.
Originally presented as an Agile 101 at Agile New England in May 2023.
IFERGAN COLLECTION ABRIRÁ ESTE VERANO EN EL CENTRO DE MÁLAGA UN PROYECTO CULT...Ayuntamiento de Málaga
Este nuevo espacio reunirá una selección de 300 piezas de la colección privada de Vicente Jiménez Ifergan, que van del año 3000 a. C. al siglo XIII
Este proyecto cultural único ofrecerá a partir del próximo verano una experiencia inmersiva alrededor de una de las colecciones arqueológicas más importantes de Europa.
Agile inschatten van werk - planning pokerLuk Schoofs
Voor het Agile inschatten van de inspanning van een taak kan planning poker gebruikt worden. De infographic geeft schematisch weer welke stappen ondernomen moeten worden.
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.
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
Agile is a philosophy for delivering solutions that embraces and promotes evolutionary change throughout the life-cycle of a product. Many teams and organizations have been using Agile to, deliver software more timely, increase quality, and ultimately increase customer satisfaction.
These planning levels were originally described by Hubert Smits in the whitepaper "5 Levels of Agile Planning: From Enterprise Product Vision to Team Stand-up".
Presentatie bij workshop die gegeven door OVSoftware tijdens TOP event 2014. Het scrum traject wordt inzichtelijk in Jira. Presentatie laat zien hoe je gemakkelijk kan scrummen met behulp van de juiste tooling, Alle partijen hebben inzicht in de voortgang van het project.
Speak To The Business! Agile Metrics That Inform Rather Confuse the Businesstroytuttle
Given to PMI KC Professional Development Days 2014 Conference.
In this session, we will investigate the challenges with the popular Agile planning and reporting concepts like story points, planning poker, and average velocity. We will explore some practical alternative planning and reporting practices that the business can understand. And we will look at metrics that are less of an abstraction from reality and more actionable by teams and management.
Learning is driven by core skill set of kids. We have focused on identifying and improving core skill set by casual gaming. The process of skill set enhancement is very important at very young age.
For more information
info@twistmobile.in
The NoEstimates Game by Matthew Philip (ThoughtWorks) - Agile en SeineAgile En Seine
Wondering what NoEstimates means in practice, or why you would want to use NoEstimates? Perhaps you’ve heard the buzz, read Vasco Duarte’s book or simply want to understand how to spend less time estimating and more time delivering working software, while providing your customers with some understanding of predictability. If so, you can play a board game that helps you find out through simulation what — and how much — different factors influence delivery time. You also learn how to move from upfront intuition-based estimates to create a data-based probabilistic forecast that provides a more reliable way to talk about when stuff will be done, while taking less effort to do so. Through simulating real-life occurrences, such as rework, blockers and delays, the game helps you understand how to reduce variation that creates risk in software delivery. It may just be the most fun you have learning something that you can start using as soon as you return to the office!
AnnMaria De Mars - Making Educational Games That Add UpSeriousGamesAssoc
Educational games share certain challenges with all serious games. A successful educational game needs to be both a good game and educational. Obvious, but many teams focus on one aspect and include either the game developer or educator as an after-thought. The result is either games that don’t teach or games that children won’t play. How do you determine at what level of mathematics (or any subject) a student should begin? How do you know if students learned something and how do you prove that your game was the cause? The educational component must target, teach, test and track. Is a game where the novelty effect never wears off an oxymoron? These questions will be answered, based on both the research literature, as well as our own data, from the first two years of research on using games to raise mathematics scores of students attending schools on American Indian reservations.
Estimating or sizing the agile backlog might seem like a lot of work with low ROI because things change quickly. But it helps bring much-needed order to the chaos of an ungroomed backlog. When technical teams provide high-level estimates on backlog items (epics, features, stories, tasks, and bugs) using their extensive experience and expertise, it helps both the business and the team doing the estimates build a better product at the end of the day.
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.
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.
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.
Exploring Innovations in Data Repository Solutions - Insights from the U.S. G...Globus
The U.S. Geological Survey (USGS) has made substantial investments in meeting evolving scientific, technical, and policy driven demands on storing, managing, and delivering data. As these demands continue to grow in complexity and scale, the USGS must continue to explore innovative solutions to improve its management, curation, sharing, delivering, and preservation approaches for large-scale research data. Supporting these needs, the USGS has partnered with the University of Chicago-Globus to research and develop advanced repository components and workflows leveraging its current investment in Globus. The primary outcome of this partnership includes the development of a prototype enterprise repository, driven by USGS Data Release requirements, through exploration and implementation of the entire suite of the Globus platform offerings, including Globus Flow, Globus Auth, Globus Transfer, and Globus Search. This presentation will provide insights into this research partnership, introduce the unique requirements and challenges being addressed and provide relevant project progress.
top nidhi software solution freedownloadvrstrong314
This presentation emphasizes the importance of data security and legal compliance for Nidhi companies in India. It highlights how online Nidhi software solutions, like Vector Nidhi Software, offer advanced features tailored to these needs. Key aspects include encryption, access controls, and audit trails to ensure data security. The software complies with regulatory guidelines from the MCA and RBI and adheres to Nidhi Rules, 2014. With customizable, user-friendly interfaces and real-time features, these Nidhi software solutions enhance efficiency, support growth, and provide exceptional member services. The presentation concludes with contact information for further inquiries.
We describe the deployment and use of Globus Compute for remote computation. This content is aimed at researchers who wish to compute on remote resources using a unified programming interface, as well as system administrators who will deploy and operate Globus Compute services on their research computing infrastructure.
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.
How to Position Your Globus Data Portal for Success Ten Good PracticesGlobus
Science gateways allow science and engineering communities to access shared data, software, computing services, and instruments. Science gateways have gained a lot of traction in the last twenty years, as evidenced by projects such as the Science Gateways Community Institute (SGCI) and the Center of Excellence on Science Gateways (SGX3) in the US, The Australian Research Data Commons (ARDC) and its platforms in Australia, and the projects around Virtual Research Environments in Europe. A few mature frameworks have evolved with their different strengths and foci and have been taken up by a larger community such as the Globus Data Portal, Hubzero, Tapis, and Galaxy. However, even when gateways are built on successful frameworks, they continue to face the challenges of ongoing maintenance costs and how to meet the ever-expanding needs of the community they serve with enhanced features. It is not uncommon that gateways with compelling use cases are nonetheless unable to get past the prototype phase and become a full production service, or if they do, they don't survive more than a couple of years. While there is no guaranteed pathway to success, it seems likely that for any gateway there is a need for a strong community and/or solid funding streams to create and sustain its success. With over twenty years of examples to draw from, this presentation goes into detail for ten factors common to successful and enduring gateways that effectively serve as best practices for any new or developing gateway.
Paketo Buildpacks : la meilleure façon de construire des images OCI? DevopsDa...Anthony Dahanne
Les Buildpacks existent depuis plus de 10 ans ! D’abord, ils étaient utilisés pour détecter et construire une application avant de la déployer sur certains PaaS. Ensuite, nous avons pu créer des images Docker (OCI) avec leur dernière génération, les Cloud Native Buildpacks (CNCF en incubation). Sont-ils une bonne alternative au Dockerfile ? Que sont les buildpacks Paketo ? Quelles communautés les soutiennent et comment ?
Venez le découvrir lors de cette session ignite
Unleash Unlimited Potential with One-Time Purchase
BoxLang is more than just a language; it's a community. By choosing a Visionary License, you're not just investing in your success, you're actively contributing to the ongoing development and support of BoxLang.
Advanced Flow Concepts Every Developer Should KnowPeter Caitens
Tim Combridge from Sensible Giraffe and Salesforce Ben presents some important tips that all developers should know when dealing with Flows in Salesforce.
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.
How Does XfilesPro Ensure Security While Sharing Documents in Salesforce?XfilesPro
Worried about document security while sharing them in Salesforce? Fret no more! Here are the top-notch security standards XfilesPro upholds to ensure strong security for your Salesforce documents while sharing with internal or external people.
To learn more, read the blog: https://www.xfilespro.com/how-does-xfilespro-make-document-sharing-secure-and-seamless-in-salesforce/
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.
First Steps with Globus Compute Multi-User EndpointsGlobus
In this presentation we will share our experiences around getting started with the Globus Compute multi-user endpoint. Working with the Pharmacology group at the University of Auckland, we have previously written an application using Globus Compute that can offload computationally expensive steps in the researcher's workflows, which they wish to manage from their familiar Windows environments, onto the NeSI (New Zealand eScience Infrastructure) cluster. Some of the challenges we have encountered were that each researcher had to set up and manage their own single-user globus compute endpoint and that the workloads had varying resource requirements (CPUs, memory and wall time) between different runs. We hope that the multi-user endpoint will help to address these challenges and share an update on our progress here.
Globus Compute wth IRI Workflows - GlobusWorld 2024Globus
As part of the DOE Integrated Research Infrastructure (IRI) program, NERSC at Lawrence Berkeley National Lab and ALCF at Argonne National Lab are working closely with General Atomics on accelerating the computing requirements of the DIII-D experiment. As part of the work the team is investigating ways to speedup the time to solution for many different parts of the DIII-D workflow including how they run jobs on HPC systems. One of these routes is looking at Globus Compute as a way to replace the current method for managing tasks and we describe a brief proof of concept showing how Globus Compute could help to schedule jobs and be a tool to connect compute at different facilities.
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.
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!
2. First developed by James Grenning
“How to avoid analysis paralysis while release
planning”
The aim of Planning Poker is to create
estimates in a short time and involve the
whole team
David Parsons - Massey University
3. Like the Planning Game, Planning Poker is not
really a game
◦ Simply a way of using game-like activities to
perform some of the tasks of agile planning
One significant difference is that in Planning
Poker there are additional „pieces‟ – the
„cards‟ used to estimate stories
David Parsons - Massey University
4. The customer reads a story
◦ There is a discussion clarifying the story as
necessary
Each programmer selects their chosen
estimate card
◦ (Or writes their estimate on a note card, if no pre-
printed pack is available)
No discussion of estimates takes place at this
stage
Once all programmers have written their
estimate, all the cards are turned over
David Parsons - Massey University
5. If there is agreement, no discussion is
necessary
◦ The estimate is recorded and we move on to the
next story.
If there is disagreement in the estimates, the
team can try to get a consensus
If there is no consensus, it doesn‟t matter
◦ It is only one story out of many
It can be deferred, split, or the lowest
estimate can be taken
David Parsons - Massey University
6. Everyone in the team participates
◦ They have to make an estimate
◦ Everyone gains experience
Discussions are automatically triggered by
the more problematic estimates
Where estimates are straightforward, the
game enables consensus without unnecessary
discussion
David Parsons - Massey University
7. Save time of manually writing estimates
Cards also only have a subset of possible
estimated days
James Grenning‟s set:
◦ 1, 2, 3, 5, 7, 10 days and infinity
As the estimates get longer, the precision
goes down
David Parsons - Massey University
8. Maximum story size is under 2 weeks
if you estimate that a story is longer than 2
weeks, play the infinity card and make the
customer split the story
David Parsons - Massey University
9. Mountain Goat Software
◦ 0, 1, 2, 3, 5, 8, 13, 20, 40, and 100
◦ online version also includes a .5 card
◦ The „zero‟ value might look odd but it does not
mean it takes no time at all, rather that is closer to
0 than 1
Mike Cohn
◦ 1, 2, 3, 5, and 8 (Fibonacci sequence)
◦ or 1, 2, 4, and 8
StudioAlt
◦ ?, 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100
David Parsons - Massey University
10. If the number represents days, why do some
card sets go up to 100?
Because not everyone sticks to „days‟ as their
unit of estimation
“Planning Poker can be used with story
points, ideal days, or any other estimating
unit”
– Mountain Goat Software
David Parsons - Massey University
11. As well as the estimation number cards, some
packs have additional cards
◦ „don‟t know‟
◦ „discuss‟
◦ „coffee time‟
◦ etc.
You can make up cards that you find useful in
your own processes
David Parsons - Massey University
12. 0, 1, 2, 3, 5, 8, 13, 20, 40 (in 5 „suits‟)
+ „fast forward/rewind‟ and „talk‟
David Parsons - Massey University
13. One suggestion for maintaining the speed of
the process is to use a 2-minute egg timer
for each discussion
This may be turned over once more for more
problematic estimates but then the next story
should be estimated
David Parsons - Massey University
14. With large teams, where there are many
stories to estimate, Planning Poker can be
played separately by smaller teams
However they will need to have done some
estimating as a whole team first, covering 10
to 20 stories
◦ This ensures that everyone is familiar with the
technique
◦ Also ensures that subsequent estimates are
consistent between groups
David Parsons - Massey University
15. A minor variation on Planning Poker is to use
poker chips instead of estimation cards, 1
chip for each story point
Possible to use different coloured chips to
indicate different estimation contexts
◦ “we had three team sizes we were considering for
the release and we used white, blue and red chips
to indicate the base story points and two levels of
increment”
Yip, J. (2007)
David Parsons - Massey University
16. Another variation is to use an on-line version
for distributed teams
You can also download versions for mobile
phones
planningpoker.com
David Parsons - Massey University
17. Moløkken-Østvold and Haugen (2007)
identified some measurable and potential
benefits
Haugen (2006) claimed that it improved
estimation in most cases, but that it
increased estimation error in the extreme
cases
David Parsons - Massey University
18. Cohn, M. (2005). Agile Estimating and Planning, Addison-Wesley
Grenning, J. (2002). Planning Poker or How to avoid analysis
paralysis while release planning https://sewiki.iai.uni-
bonn.de/_media/teaching/labs/xp/2005a/doc.planningpoker-
v1.pdf
Haugen, N. (2006). An Empirical Study of Using Planning Poker
for User Story Estimation, AGILE 2006, 23-34
Moløkken-Østvold, K. & Haugen, N. (2007). Combining Estimates
with Planning Poker – An Empirical Study, 18th Australian
Software Engineering Conference (ASWEC 2007), 349–358
Yip, J. (2007). Hands-on release planning with poker chips. 14th
Conference on Pattern Languages of Programs (PLOP 2007)
David Parsons - Massey University