Story Points Explained
•
3 likes•906 views
The document discusses estimating story points for tasks in software development. It explains that story points indicate the amount of work, complexity, and uncertainty of a task, with values assigned on a scale of 0 to 100. It provides examples of common tasks and their typical story point values, as well as tips for calculating story points by considering the amount of work, complexity, and uncertainty of the task.
Report
Share
Report
Share
Download to read offline
Recommended
Introduction to story points
A brief introduction to Story Points and how to use Planning Poker to determine story points collaboratively for the task at hand
Estimating with story points
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
[HCM Scrum Breakfast] Agile estimation - Story points
This document provides information about agile estimation techniques, including story points and planning poker. It discusses how story points are used to provide relative estimates of complexity rather than time estimates. Planning poker is described as a consensus-based technique where a team privately selects story point cards before discussing to reach agreement. The document also covers insights around how additional details don't necessarily lead to better estimates and how past sprint performance can inform long-term planning estimates. Common questions about estimation techniques are addressed.
story points v2
User story points are used for estimation because software projects are complex with many factors that make hour-based estimation inaccurate. Story points use a relative scale where user stories are assigned points based on their size compared to baseline reference stories. This allows for more accurate planning across sprints and continuous improvement of estimates as a team's velocity is tracked over time. The key aspects are regularly practicing estimation as a skill, having a shared understanding of baseline stories, and focusing comparisons only on effort required to complete stories.
Agile estimation
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!
How to estimate in scrum
- Story points are an arbitrary measure used by Scrum teams to estimate the effort required to implement a user story. Teams typically use a Fibonacci sequence like 1, 2, 3, 5, 8, 13, 20, 40, 100.
- Estimating user stories allows teams to plan how many highest priority stories can be completed in a sprint and helps forecast release schedules. The whole team estimates during backlog refinement.
- Stories are estimated once they are small enough to fit in a sprint and acceptance criteria are agreed upon. Teams commonly use planning poker where each member privately assigns a story point value and the team discusses until consensus is reached.
Agile Estimation & Capacity Planning
This presentation includes an overview of the various estimation techniques used in Agile projects. I've also put in a slide for explaining the importance of business value for Agile requirements. A simple mechanism on capacity planning before weaving it all together to come up with a reasonably foolproof plan.
Agile stories, estimating and planning
This document provides an overview of agile stories, estimating, and planning. It discusses what user stories are, how to write them, and techniques for estimating story sizes such as story points. It also covers different levels of planning including release planning, iteration planning, and daily planning. The document is intended to provide background information on using agile methods for requirements management and project planning.
Recommended
Introduction to story points
A brief introduction to Story Points and how to use Planning Poker to determine story points collaboratively for the task at hand
Estimating with story points
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
[HCM Scrum Breakfast] Agile estimation - Story points
This document provides information about agile estimation techniques, including story points and planning poker. It discusses how story points are used to provide relative estimates of complexity rather than time estimates. Planning poker is described as a consensus-based technique where a team privately selects story point cards before discussing to reach agreement. The document also covers insights around how additional details don't necessarily lead to better estimates and how past sprint performance can inform long-term planning estimates. Common questions about estimation techniques are addressed.
story points v2
User story points are used for estimation because software projects are complex with many factors that make hour-based estimation inaccurate. Story points use a relative scale where user stories are assigned points based on their size compared to baseline reference stories. This allows for more accurate planning across sprints and continuous improvement of estimates as a team's velocity is tracked over time. The key aspects are regularly practicing estimation as a skill, having a shared understanding of baseline stories, and focusing comparisons only on effort required to complete stories.
Agile estimation
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!
How to estimate in scrum
- Story points are an arbitrary measure used by Scrum teams to estimate the effort required to implement a user story. Teams typically use a Fibonacci sequence like 1, 2, 3, 5, 8, 13, 20, 40, 100.
- Estimating user stories allows teams to plan how many highest priority stories can be completed in a sprint and helps forecast release schedules. The whole team estimates during backlog refinement.
- Stories are estimated once they are small enough to fit in a sprint and acceptance criteria are agreed upon. Teams commonly use planning poker where each member privately assigns a story point value and the team discusses until consensus is reached.
Agile Estimation & Capacity Planning
This presentation includes an overview of the various estimation techniques used in Agile projects. I've also put in a slide for explaining the importance of business value for Agile requirements. A simple mechanism on capacity planning before weaving it all together to come up with a reasonably foolproof plan.
Agile stories, estimating and planning
This document provides an overview of agile stories, estimating, and planning. It discusses what user stories are, how to write them, and techniques for estimating story sizes such as story points. It also covers different levels of planning including release planning, iteration planning, and daily planning. The document is intended to provide background information on using agile methods for requirements management and project planning.
Agile effort estimation
This document discusses effort estimation in agile projects. It recommends estimating tasks by relative size using story points rather than absolute time values. Planning poker, where a team privately selects effort estimate cards and then discusses them, is advocated as it emphasizes relative estimation and reduces anchoring bias. Velocity, the number of points a team can complete per iteration, is key for planning and adjusting for estimation errors over time. Burn down charts also increase visibility of progress.
Story Points Estimation And Planning Poker
An introduction into basic concepts about agile scrum story point estimation and planning poker. And a simple set of do's and don'ts.
Agile Planning and Estimation
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
User Story Sizing using Agile Relative 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.
Estimation techniques for Scrum Teams
My main goal is to share and make you experiment some of the techniques that I use when transforming teams into high-perfoming agile teams, by providing you with four (4) different ways to estimate projects in Agile.
Estimation and Release Planning in Scrum
Scrum uses relative estimation and velocity to aid in planning and making trade-off decisions. Relative estimation involves comparing the effort of new requirements to previously estimated ones, which humans are better at than absolute estimates. Velocity is the amount of work completed in an iteration, measured in story points or hours, and varies over time so is useful for longer-term planning. There are two types of Scrum planning: fixed-date planning estimates how much can be completed by a date based on velocity, while fixed-scope planning estimates the timeframe to complete all backlog items based on velocity. Both use velocity as a range rather than a precise prediction.
Agile Scrum Estimation
The document discusses different approaches to estimation in waterfall and Scrum methodologies. In Scrum, teams estimate their own work in story points, which are relative units based on size and complexity. Story points help drive cross-functional behavior and do not decay over time. Ideal days estimates involve determining how long a task would take with ideal conditions and no interruptions. Planning poker uses story point cards to facilitate discussion and reach consensus on estimates. Release planning in Scrum involves estimating velocity over sprints to determine how many product backlog items can be completed.
Agile Estimating & Planning by Amaad 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
Estimating Story Points in Agile - MAGIC Approach
This document discusses techniques for estimating story points in Agile projects. It describes current estimation practices like fixed story pointing based on person hours or days, expert influence, and guestimating. These can lead to inaccurate estimates and not reflect improved productivity over time. The document proposes an approach called MAGIC which uses a story point matrix based on functional and technical analysis to measure and analyze stories, and an empirical data model using historical project data to improve and control estimates. Templates are provided for the story point matrix and empirical data model.
Practical estimation techniques
Introduction:
Struggling to estimate your user stories?
Agenda:
What is agile estimation
Relative versus absolute estimation
Various techniques of estimation
Short introduction to Planning poker technique
Estimate in Story points or ideal days?
When not to re estimate?
Common challenges while estimating
Agile estimating 12112013 - Agile KC Dec 2013
Story point estimating using the Fibonacci sequence is the most common agile estimating technique. It provides better and more accurate estimates than hourly estimates with less variation. Story points also cut estimation time by 80% allowing teams to estimate and track work more. Regularly measuring a team's velocity enables accurate forecasting of schedules and costs for a release. Agile estimating with story points is more efficient than traditional techniques.
Agile Estimation Techniques.pptx
Agile estimation is the process of estimating the effort required to complete tasks in the product backlog. This helps with accurate sprint planning. There are several techniques for agile estimation, including planning poker where team members assign numeric values to tasks, T-shirt sizing where tasks are categorized based on size, and analogy where tasks are estimated based on comparisons to other similar tasks. Other techniques include dot voting, affinity mapping, and various systems using buckets or distributions. Planning poker and T-shirt sizing involve collaboration between team members to determine estimates. Accurate estimation allows for improved sprint management and release prediction.
Agile estimation techniques workshop
Workshop on Agile estimation techniques including Planning poker, Affinity estimation and relative estimation. First prez at Trasys during a lunch seminar
Story Points
Story points are used to estimate the relative complexity of user stories in an agile framework like Scrum. They provide an easier comparison between stories than estimating time. A team agrees on a reference story and then estimates new stories in points relative to the reference. This allows the team to track their average velocity of completed points over sprints to forecast how many sprints future work will take. There is no explicit Scrum event for estimating points but it commonly occurs during backlog refinement.
Agile metrics
An overview about various agile metrics - why to use them, what to consider when using metrics and various examples of suggested metrics
Agile estimation and planning peter saddington
The document discusses several techniques for estimating the size and complexity of features in agile development projects, including planning poker, decomposition, and using ideal time vs elapsed time. It emphasizes that estimation in agile focuses on relative sizing rather than durations, and that estimates are intentionally vague at first and improve over time based on measuring team velocity. Key goals of iteration planning meetings are to set commitments and arrive at a prioritized backlog for the upcoming sprint.
SCRUM Estimation
This document discusses key concepts in agile planning including story points, velocity, and release planning using velocity. It defines story points as relative sizes used to estimate user stories, and explains how they remain constant over time unlike ideal days estimates. Velocity is defined as the average story points a team can complete per sprint. The document outlines how to establish story points and use them along with velocity for release planning and tracking progress with a burn down chart.
Agile Estimation Techniques
Presentation from Agile Base Camp conference (Kiev, April 2011) about estimation techniques in Agile teams.
WIP: A Couple Exercises and Some Simple Math
This presentation begins with a simple exercise, follows with some simple math, and ends with another simple exercise. The intent of the exercises and the math is to illustrate the impacts of work in progress and multi-tasking.
Limiting WIP is perhaps the single most impactful practice at our disposal to dramatically improve productivity.
Originally presented at Agile New England on 5 May 2022.
Agile estimation and planning
This document discusses agile estimation and planning techniques. It recommends estimating tasks relatively using story points rather than absolute time estimates. Planning poker, where teams privately estimate tasks and then discuss estimates, is presented as an effective technique. Prioritizing a backlog by value, risk, and estimate allows teams to focus on the most important work. Iterative planning within sprints and tracking progress via burn down charts increases transparency.
User Story Point estimation method at ConFoo 2015
We'll initially examine how and why estimation in Agile goes so wrong, so often. A new, structured and empirical method for estimating story points will then be introduced. The method involves taking into account human and environment-related factors, as well as technical ones, assigns weighted points to them and uses a numeric formula to derive a user-story's point estimate.
The Year of Living Dangerously: Extraordinary Results for an Enterprise Agile...
Keynote address at the Scrum Gathering 2008 in Chicago. Steve Greene and Chris Fry expand the salesforce.com agile transformation story with a year of continuous improvement and metrics / measurements of extraordinary success.
More Related Content
What's hot
Agile effort estimation
This document discusses effort estimation in agile projects. It recommends estimating tasks by relative size using story points rather than absolute time values. Planning poker, where a team privately selects effort estimate cards and then discusses them, is advocated as it emphasizes relative estimation and reduces anchoring bias. Velocity, the number of points a team can complete per iteration, is key for planning and adjusting for estimation errors over time. Burn down charts also increase visibility of progress.
Story Points Estimation And Planning Poker
An introduction into basic concepts about agile scrum story point estimation and planning poker. And a simple set of do's and don'ts.
Agile Planning and Estimation
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
User Story Sizing using Agile Relative 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.
Estimation techniques for Scrum Teams
My main goal is to share and make you experiment some of the techniques that I use when transforming teams into high-perfoming agile teams, by providing you with four (4) different ways to estimate projects in Agile.
Estimation and Release Planning in Scrum
Scrum uses relative estimation and velocity to aid in planning and making trade-off decisions. Relative estimation involves comparing the effort of new requirements to previously estimated ones, which humans are better at than absolute estimates. Velocity is the amount of work completed in an iteration, measured in story points or hours, and varies over time so is useful for longer-term planning. There are two types of Scrum planning: fixed-date planning estimates how much can be completed by a date based on velocity, while fixed-scope planning estimates the timeframe to complete all backlog items based on velocity. Both use velocity as a range rather than a precise prediction.
Agile Scrum Estimation
The document discusses different approaches to estimation in waterfall and Scrum methodologies. In Scrum, teams estimate their own work in story points, which are relative units based on size and complexity. Story points help drive cross-functional behavior and do not decay over time. Ideal days estimates involve determining how long a task would take with ideal conditions and no interruptions. Planning poker uses story point cards to facilitate discussion and reach consensus on estimates. Release planning in Scrum involves estimating velocity over sprints to determine how many product backlog items can be completed.
Agile Estimating & Planning by Amaad 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
Estimating Story Points in Agile - MAGIC Approach
This document discusses techniques for estimating story points in Agile projects. It describes current estimation practices like fixed story pointing based on person hours or days, expert influence, and guestimating. These can lead to inaccurate estimates and not reflect improved productivity over time. The document proposes an approach called MAGIC which uses a story point matrix based on functional and technical analysis to measure and analyze stories, and an empirical data model using historical project data to improve and control estimates. Templates are provided for the story point matrix and empirical data model.
Practical estimation techniques
Introduction:
Struggling to estimate your user stories?
Agenda:
What is agile estimation
Relative versus absolute estimation
Various techniques of estimation
Short introduction to Planning poker technique
Estimate in Story points or ideal days?
When not to re estimate?
Common challenges while estimating
Agile estimating 12112013 - Agile KC Dec 2013
Story point estimating using the Fibonacci sequence is the most common agile estimating technique. It provides better and more accurate estimates than hourly estimates with less variation. Story points also cut estimation time by 80% allowing teams to estimate and track work more. Regularly measuring a team's velocity enables accurate forecasting of schedules and costs for a release. Agile estimating with story points is more efficient than traditional techniques.
Agile Estimation Techniques.pptx
Agile estimation is the process of estimating the effort required to complete tasks in the product backlog. This helps with accurate sprint planning. There are several techniques for agile estimation, including planning poker where team members assign numeric values to tasks, T-shirt sizing where tasks are categorized based on size, and analogy where tasks are estimated based on comparisons to other similar tasks. Other techniques include dot voting, affinity mapping, and various systems using buckets or distributions. Planning poker and T-shirt sizing involve collaboration between team members to determine estimates. Accurate estimation allows for improved sprint management and release prediction.
Agile estimation techniques workshop
Workshop on Agile estimation techniques including Planning poker, Affinity estimation and relative estimation. First prez at Trasys during a lunch seminar
Story Points
Story points are used to estimate the relative complexity of user stories in an agile framework like Scrum. They provide an easier comparison between stories than estimating time. A team agrees on a reference story and then estimates new stories in points relative to the reference. This allows the team to track their average velocity of completed points over sprints to forecast how many sprints future work will take. There is no explicit Scrum event for estimating points but it commonly occurs during backlog refinement.
Agile metrics
An overview about various agile metrics - why to use them, what to consider when using metrics and various examples of suggested metrics
Agile estimation and planning peter saddington
The document discusses several techniques for estimating the size and complexity of features in agile development projects, including planning poker, decomposition, and using ideal time vs elapsed time. It emphasizes that estimation in agile focuses on relative sizing rather than durations, and that estimates are intentionally vague at first and improve over time based on measuring team velocity. Key goals of iteration planning meetings are to set commitments and arrive at a prioritized backlog for the upcoming sprint.
SCRUM Estimation
This document discusses key concepts in agile planning including story points, velocity, and release planning using velocity. It defines story points as relative sizes used to estimate user stories, and explains how they remain constant over time unlike ideal days estimates. Velocity is defined as the average story points a team can complete per sprint. The document outlines how to establish story points and use them along with velocity for release planning and tracking progress with a burn down chart.
Agile Estimation Techniques
Presentation from Agile Base Camp conference (Kiev, April 2011) about estimation techniques in Agile teams.
WIP: A Couple Exercises and Some Simple Math
This presentation begins with a simple exercise, follows with some simple math, and ends with another simple exercise. The intent of the exercises and the math is to illustrate the impacts of work in progress and multi-tasking.
Limiting WIP is perhaps the single most impactful practice at our disposal to dramatically improve productivity.
Originally presented at Agile New England on 5 May 2022.
Agile estimation and planning
This document discusses agile estimation and planning techniques. It recommends estimating tasks relatively using story points rather than absolute time estimates. Planning poker, where teams privately estimate tasks and then discuss estimates, is presented as an effective technique. Prioritizing a backlog by value, risk, and estimate allows teams to focus on the most important work. Iterative planning within sprints and tracking progress via burn down charts increases transparency.
What's hot (20)
Viewers also liked
User Story Point estimation method at ConFoo 2015
We'll initially examine how and why estimation in Agile goes so wrong, so often. A new, structured and empirical method for estimating story points will then be introduced. The method involves taking into account human and environment-related factors, as well as technical ones, assigns weighted points to them and uses a numeric formula to derive a user-story's point estimate.
The Year of Living Dangerously: Extraordinary Results for an Enterprise Agile...
Keynote address at the Scrum Gathering 2008 in Chicago. Steve Greene and Chris Fry expand the salesforce.com agile transformation story with a year of continuous improvement and metrics / measurements of extraordinary success.
AgileChina 2015: Agile Estimation Workshop
These are the slides from the Agile Estimation Workshop I gave at AgileChina 2015. The morning session covered opinion-based techniques. The afternoon covered empirical techniques based on cycle time, Little's Law, and Monte Carlo simulation.
Agile requirements: User Stories, Story Points, Hours
A presentation for the people who would like to improve their skills in writing good user stories, and understanding approach for estimation and planning in Scrum.
2 hour presentation + 1 hour of practical game.
I Don't Do Agile. I Am Agile
The document discusses adopting agile practices in organizations. It describes common problems organizations face, such as following practices rigidly without understanding why. It advocates taking a lean approach, focusing on value and eliminating waste. Practices from Scrum, XP and Kanban should be selected based on what specifically helps for the product and team, rather than following a single methodology strictly. Continuous improvement is emphasized through learning from failures and questioning current practices.
Responsive Color
Color is one of the first things we learn how to do in CSS — and yet many of us don't ever go further than typing hex numbers handed to us by a designer. But getting colors to appear on a screen is just the beginning. Find out why colors look different on different devices, and what you can do about it. Learn how to adjust colors with media queries to make sure your colors look their best on any screen size. Find out how user context may affect the appropriate colors for a website. And finally, learn how you can make this whole color thing a lot less complicated by using a CSS preprocessor like Sass to manage your color choices and create color variations automatically.
Presented in 2015 & 2016 at Amazon's WebDevCon, ConFoo, Breaking Development, Mobile+Web Dev Conference, Code Fellows Seattle, CascadiaFest, CSS Summit, CSS Brigade Vancouver, CSS Day Amsterdam, Future Insights Live, WebVisions NYC, and Albany UX.
Agile webinar بالعربي Planning ,estimation and story points
الwebinar ده من ضمن سلسلة webinars هدفها نشر فكر الagile بطريقة interactive و بالعربي عشان توصل اكتر للناس
webinar ده بيتعمل كل اسبوعين مع جروب agile بالعربي
https://www.facebook.com/groups/Agile.bel3araby/
الhost انا Mona Shokrof , بشتغل Agile coach and trainer في Agile Arena ده الaccount بتاعي علي linked in
https://www.linkedin.com/in/monashokrof
اللي حابب يسال اي حاجة
اللي بدات فكرة شرح الAgile بالعربي علي الblog بتاعها www.shokrof.com
Agile organization design workshop
这个工作坊的目标是帮助变革者理解组织设计的各个方面以推动敏捷组织转型。敏捷转型是为了提⾼组织的敏捷度。我们会基于星型模型来设计敏捷组织。首先，我们会理解什么是组织敏捷度以及它如何支持组织战略。接着，我们会来看组织架构－基于Scrum团队的架构和扩展，以及相关⾓色和职责。然后，我们会来看如何设计流程和横向能⼒以使组织架构中跨部门能有效合作。最后，我们会来看奖励和⼈员方面的实践，尤其是绩效考评。
Agile Estimation And Planning
This document provides an introduction to agile estimation and release planning. It discusses estimating the effort for each product backlog item, prioritizing items, using iterations to determine average team velocity, creating a candidate schedule based on velocity, and continuously monitoring and adapting the plan based on real progress. The key messages are that plans will change and embracing change is important, estimating includes uncertainty, and the goal is to deliver working software frequently.
Better Estimation Through Estimation Process Improvement - Dan Galorath
How can an organisation begin to develop a standardised estimation approach and what benefits can be achieved.
Successful agile teams at scale
This document discusses successful Agile teams at scale. It begins by explaining why organizations want to adopt Agile practices like shorter time-to-market and improved quality. However, true Agile adoption requires changes to business, culture and ways of working. The document then discusses scaling Agile through frameworks like SAFe and DAD which provide structure for large, distributed teams. Supporting practices for Agile at scale include risk management, delivery assurance and governance. Finally, the document states that successful Agile teams at scale provide benefits like reduced time-to-value and improved business relationships, but require investments in people, processes and tools to support collaboration.
How to build rubust org structure for Agile at scale
Are you going to implement Agile/Lean methodologies in your organization, but you don’t have a clue where to start? Does it make sense to begin with Agile training? Or, it would be better to start with implementation of application lifecycle management tools (ALM), or, it would be enough just to hire right people with agile expertise?
Based on our experience, with more than 100 clients, we clearly see that in most of the cases real agile transformation is kicking off from organizational structure change. This is exactly what we would like to share with you.
We will talk about typical issues in organization structure that we have seen when helping our clients to transform. We will also outline what potential problems might cause those issues. Furthermore, we will share successful patterns of building robust organizational structures for different types of the companies: starting from small and scaling it up to enterprise (100+ employees).
As an outcome, participants will get an overview on how to build robust organizational structure as a foundation for successful Agile/Lean implementation.
The 5 Levels Planning in Agile
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".
Viewers also liked (13)
The Year of Living Dangerously: Extraordinary Results for an Enterprise Agile...
The Year of Living Dangerously: Extraordinary Results for an Enterprise Agile...
Agile requirements: User Stories, Story Points, Hours
Agile requirements: User Stories, Story Points, Hours
Agile webinar بالعربي Planning ,estimation and story points
Agile webinar بالعربي Planning ,estimation and story points
Better Estimation Through Estimation Process Improvement - Dan Galorath
Better Estimation Through Estimation Process Improvement - Dan Galorath
How to build rubust org structure for Agile at scale
How to build rubust org structure for Agile at scale
Recently uploaded
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Fueling AI with Great Data with Airbyte Webinar
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Building Production Ready Search Pipelines with Spark and Milvus
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
System Design Case Study: Building a Scalable E-Commerce Platform - Hiike
This case study explores designing a scalable e-commerce platform, covering key requirements, system components, and best practices.
Trusted Execution Environment for Decentralized Process Mining
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
Predictive maintenance is a proactive approach that anticipates equipment failures before they happen. At the forefront of this innovative strategy is Artificial Intelligence (AI), which brings unprecedented precision and efficiency. AI in predictive maintenance is transforming industries by reducing downtime, minimizing costs, and enhancing productivity.
Finale of the Year: Apply for Next One!
Presentation for the event called "Finale of the Year: Apply for Next One!" organized by GDSC PJATK
TrustArc Webinar - 2024 Global Privacy Survey
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Best 20 SEO Techniques To Improve Website Visibility In SERP
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Skybuffer SAM4U tool for SAP license adoption
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
5th LF Energy Power Grid Model Meet-up Slides
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Recently uploaded (20)
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Deep Dive: Getting Funded with Jason Jason Lemkin Founder & CEO @ SaaStr
Deep Dive: Getting Funded with Jason Jason Lemkin Founder & CEO @ SaaStr
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
System Design Case Study: Building a Scalable E-Commerce Platform - Hiike
System Design Case Study: Building a Scalable E-Commerce Platform - Hiike
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Trusted Execution Environment for Decentralized Process Mining
Trusted Execution Environment for Decentralized Process Mining
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
Story Points Explained
- 1. Estimating Stories What the heck is the Story Point?
- 2. Change 1 output message Change 10 output messages 0 1 2 3 4 5 6 7 8 9 10 Trivial and concrete Amount Storysize Amount of work
- 3. Change 1 output message Change 10 output messages Write one line recursion Write a big recursions 0 5 10 15 20 25 30 Concrete but not trivial Complexity Amount Storysize Complexity
- 4. Change 1 output message Change 10 output messages Write one line recursion Write a big recursions Find a data integrity flaw Find a netw orking bottleneck 0 10 20 30 40 50 60 70 80 At whole Uncertainty Complexity Amount Storysize Uncertainty
- 5. Calculation tip Amount of work: Done +0 One-liner +1 Larger task +2 Huge task +3 Enormous +100 Complexity: Trivial +0 Not so trivial +1 Quite complex +2 Very complex +3 Incomprehensible +100 Uncertainty: Certain +0 A bit uncertain +1 Quite uncertain +2 Need to read a book +3 Undertrained +100 Round up: 1, 2, 3, 5, 8 (sprint ok) 13, 21, 34, 55 (need to be split)