Batting Averages and Slugging %s
•
0 likes•500 views
This document discusses alternatives to using team velocity as a metric for software development teams. It proposes measuring the frequency of delivering value to users through high value releases, prioritizing work that provides the best value for effort, and recognizing individuals who consistently deliver high value features. Specific metrics proposed include an L value batting average measuring weeks with high value releases, slugging percentage measuring value delivered, and a silver slugger award for top performers.
Report
Share
Report
Share
Download to read offline
Recommended
Predictability at Axial
Given at Axial HQ for the New York chapter of Venwise, this talk details how Axial approaches building products predictably through a combination of focus, objectives, prioritization and forecasting. We call it stack.
Check out more of what we're building over at: axialcorps.com
Uncertainty in agile projects
This document discusses the importance of accounting for uncertainty in agile projects. It provides examples of sources of uncertainty like changing requirements, over or under estimation of tasks, and lack of technical knowledge. It recommends involving customers throughout the project, estimating uncertainty without being precise, and allocating time and resources to address defects and non-iteration work as a way to mitigate uncertainty. Estimating uncertainty helps deliver promised functionality on time and builds customer trust.
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.
Kaizen presentation to management meeting
The document discusses the Kaizen philosophy of continuous improvement. Kaizen focuses on making small, incremental changes over time to optimize processes and quality. It is a collaborative approach that involves all stakeholders. The 10 step Kaizen process identifies problems, plans and implements solutions, then measures results to identify areas for further improvement. The goal is to empower teams to continuously enhance their work through data-driven experiments and adjustments.
[CXL Live 16] How to Utilize Your Test Capacity? by Ton Wesseling
Ton Wesseling gave a presentation at ConversionXL Live in Austin on March 31st 2016 about utilizing test capacity. He discussed optimizing conversions through the ROAR model of risk, optimization, automation and re-thinking. Wesseling emphasized fully using a company's test capacity for impactful A/B tests and separating that capacity for IT releases, campaigns and behavioral learning. He advised celebrating failures to encourage risk-taking and continuous learning.
EuroSTAR 2013 Albert Witteveen Final
The document discusses the importance of performance testing systems and identifying queuing centers to understand bottlenecks. Some key points:
1. Performance tests often fail to accurately simulate real-world loads, leading to underestimating needed hardware on production.
2. Queuing theory can be used to model systems and identify queuing centers where waiting occurs. These centers determine performance and scalability.
3. Identifying queuing centers through testing and monitoring helps assess if systems can meet requirements, where risks lie, and how to scale effectively to improve response times.
Software Economies of Scale
Software development does not benefit from economies of scale and instead experiences diseconomies of scale. Developing in small batches provides several advantages: it accelerates feedback, makes debugging easier, allows for better visualization of progress, de-risks projects, improves estimation, enables more pivoting, gives more opportunities to inspect and adapt work, and delivers value to customers more efficiently.
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.
Recommended
Predictability at Axial
Given at Axial HQ for the New York chapter of Venwise, this talk details how Axial approaches building products predictably through a combination of focus, objectives, prioritization and forecasting. We call it stack.
Check out more of what we're building over at: axialcorps.com
Uncertainty in agile projects
This document discusses the importance of accounting for uncertainty in agile projects. It provides examples of sources of uncertainty like changing requirements, over or under estimation of tasks, and lack of technical knowledge. It recommends involving customers throughout the project, estimating uncertainty without being precise, and allocating time and resources to address defects and non-iteration work as a way to mitigate uncertainty. Estimating uncertainty helps deliver promised functionality on time and builds customer trust.
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.
Kaizen presentation to management meeting
The document discusses the Kaizen philosophy of continuous improvement. Kaizen focuses on making small, incremental changes over time to optimize processes and quality. It is a collaborative approach that involves all stakeholders. The 10 step Kaizen process identifies problems, plans and implements solutions, then measures results to identify areas for further improvement. The goal is to empower teams to continuously enhance their work through data-driven experiments and adjustments.
[CXL Live 16] How to Utilize Your Test Capacity? by Ton Wesseling
Ton Wesseling gave a presentation at ConversionXL Live in Austin on March 31st 2016 about utilizing test capacity. He discussed optimizing conversions through the ROAR model of risk, optimization, automation and re-thinking. Wesseling emphasized fully using a company's test capacity for impactful A/B tests and separating that capacity for IT releases, campaigns and behavioral learning. He advised celebrating failures to encourage risk-taking and continuous learning.
EuroSTAR 2013 Albert Witteveen Final
The document discusses the importance of performance testing systems and identifying queuing centers to understand bottlenecks. Some key points:
1. Performance tests often fail to accurately simulate real-world loads, leading to underestimating needed hardware on production.
2. Queuing theory can be used to model systems and identify queuing centers where waiting occurs. These centers determine performance and scalability.
3. Identifying queuing centers through testing and monitoring helps assess if systems can meet requirements, where risks lie, and how to scale effectively to improve response times.
Software Economies of Scale
Software development does not benefit from economies of scale and instead experiences diseconomies of scale. Developing in small batches provides several advantages: it accelerates feedback, makes debugging easier, allows for better visualization of progress, de-risks projects, improves estimation, enables more pivoting, gives more opportunities to inspect and adapt work, and delivers value to customers more efficiently.
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.
With Cloud Computing, Who Needs Performance Testing?
With cloud computing we can add more hardware resources on the fly. Considering how expensive load and stress testing can be, why don't we just add more power when needed?
This presentation will explain why, especially for situations where cloud computing is available, load and stress testing often falls short but is still required. It will also show how the queuing theory can provide a different approach which allows load and stress testers to add real value. Stakeholders and test managers can use the same theory to get a handle on the coverage and depth of the tests.
Key Takeaways:
- Why performance testing so often fails to accomplish what we want
- Why relying on cloud computing alone is not enough
- How the queuing theory can provide a different approach to performance testing
- How the queuing theory can help you understand if the performance tests
www.eurostarconferences.com
www.testhuddle.com
Toyota Kata at MYOB - Cycle Time
This document discusses continuous improvement at MYOB. It defines what an "awesome" way of working entails, including delivering high quality outcomes quickly, having self-organizing teams that are happy and engaged. It also discusses assessing the current processes, which include practices like refactoring, pair programming and metrics like cycle time, lead time, and customer happiness. It recommends collecting cycle time metrics to identify improvement opportunities like inconsistent story sizes, work in progress limits, and forecasting. Reducing high cycle times could involve clearer story definition and acceptance criteria.
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.
E-Roster Project
This document provides a guide for implementing benefits realization from a rostering improvement project. It outlines a process that begins with gathering baseline data on current spending, fill rates, and non-effective rostering. Training is then provided on rostering theory and creating a roster template. The first roster is implemented after one month, and reviews are conducted at 2, 3, and 4 months to evaluate impacts on costs, fill rates, overtime usage, and other metrics. The goal is to identify actions to improve rostering performance and efficiency over time. Regular monitoring will help ensure agreed-upon actions are implemented and wards are properly administered. While all issues may not be solved, this provides an initial framework to start identifying areas for rostering improvements
Agile Estimation
We’re agile, so we don’t have to estimate and have no deadlines, right? Wrong! This session will review the problem with estimations in projects today and then give an overview of the concept of agile estimation and the notion of re-estimation. We’ll learn about user stories, story points, team velocity, and 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 TFS and much more.
Getting To Product Market Fit Quickly
This 1-hour workshop marries the best practices from product strategy with those of fast and efficient technology teamwork and delivery. You’ll learn how to get your product organization working as a single cohesive, well-oiled machine to deliver the right product to market as quickly as possible. We will cover how to use both qualitative and quantitative measures to ensure that your product is solving the right problem; how to optimize and streamline the way your team designs, builds, and deploys software to your customers; and, how to beat the competition in strategy and execution.
BA World Boston: Evening the Odds with Monte Carlo Project Forecasting
This document discusses using Monte Carlo forecasting to predict project completion dates. It explains that Monte Carlo forecasting acknowledges variability and uncertainty by running multiple simulations of random task durations to predict a range of possible completion dates. The document provides instructions for creating a Monte Carlo forecast, discusses how the technique was used on a project, and notes some limitations and variations of the approach.
Lean Practices For Software Development
Lean practices for software development focus on maximizing customer value while minimizing waste. This includes reducing partially completed work, extra processes, extra features, task switching, waiting, motion, and defects. Developers should take an economic view by quantifying the cost of delay. They should also manage queues to reduce wait times, exploit variability while maintaining economic impact, reduce batch sizes to improve cycle times, apply work-in-progress constraints, and accelerate feedback through small batches.
Finance Presentation
The document discusses accounting and finance processes and systems at WGUK. It identifies several key issues: data accuracy problems across systems from meter points to invoices; a lack of validation processes between integrated systems; and a need for proper testing before new systems go live. It recommends: understanding problems fully before taking action; introducing validation and testing rigorously; focusing initially on fixing meter point and data accuracy issues; training staff; and establishing accurate budgets and processes for long-term improvement.
Stop using spreadsheets to monitor quality in your call centre!
The document describes a quality assessment solution called Scorebuddy that delivers real results, makes the job easier, and helps impress bosses. It provides rapid return on investment, improves agent and team performance, and allows managers and supervisors to make decisions using reports and analytics. Scorebuddy is easy to use, gives all information in one place, and saves time.
Implementing infinity hr (katie cuthriell)
This document outlines the key steps for successfully implementing the InfinityHR system. It discusses (1) planning and preparing by understanding needs, setting goals, and building a timeline, (2) designing an optimal solution by focusing on priorities and recommendations, (3) building by providing clean data and consistent communication, and (4) testing and training through engaging sessions and practicing tasks to ensure expertise before (5) deploying the system and scheduling follow up meetings for ongoing success.
agile_flow
The document outlines the Scrum process for managing product development, including estimating story points, prioritizing stories, committing to a sprint backlog, tracking progress daily, and meeting at the end of each sprint to review outcomes and plan improvements. Key steps involve breaking down features into user stories with acceptance criteria, estimating story effort, committing to complete specific stories each sprint, tracking task progress, addressing any issues that arise, demoing completed work, and retrospecting on lessons learned.
Invoice reading made simple
This EasySeparate Presentation shows how to make invoice reading simple and affordable for any SMB company.
Agile brazil2013poised
The document discusses business agility and how to achieve it through continuous experimentation, rapid feedback, and keeping systems poised for change. It outlines factors like agile software development principles, internal software quality measures, evolutionary architecture principles, and continuous delivery practices. These help lower the cost and risk of experimentation while maximizing visibility and feedback. The goal is for the business to be agile through experimenting often, being prepared to change quickly yet safely, and relying on evidence over guesses to balance predictability and opportunities.
Humans by the hundred (DevOps Days Ohio)
1) The document discusses how human fallibility and increased development teams can lead to an exponential decay in the probability of successful deployments over time as the number of changes increases.
2) It recommends approaches like implementing a service-oriented architecture, focusing on mean time to recovery rather than just preventing failures, and establishing "DevOps deputies" to help mitigate this problem.
3) The key message is that organizations should embrace DevOps culture, tailor their approaches to their specific teams, plan for inevitable changes over time, and view components as distributed from the beginning.
Flow Efficiency, the most powerful improvement driver - Scrum Australia 2018
The document discusses flow efficiency, which is a measure of how much time is spent on valuable work versus waiting. It defines flow efficiency and explains why organizations should focus on improving it. Flow efficiency is calculated by dividing touch time by lead time. The document provides tips for how to measure, analyze sources of delay, and improve an organization's flow efficiency through principles like limiting work-in-progress and reducing dependencies. The biggest leverage for improving productivity is reducing delays rather than improving individual performance.
Introduction of Kanban metrics
One of the powerful aspects of Kanban is the statistical analysis of its metrics. This presentation talks about common Kanban metrics and how to interpret them.
Implementing InfinityHR
The document outlines the key steps for implementing a new HR system called InfinityHR, including plan and prepare, design, build, testing and training, and deployment. Plan and prepare involves setting goals, organizing teams, documenting requirements, and preparing clients. Design focuses on optimizing business processes. Build requires clean data and consistent communication. Testing and training dedicates time to thoroughly test the system and make training engaging. Deployment ensures clients control the system and receive check-ins for ongoing success.
Measurement magic in world of DevOps
This document discusses the importance of measurement in software development and operations. It notes that measurement is needed as a basis for decisions, to gain situational awareness, and for improvement. However, what is measured needs to be useful, as measuring the wrong things can lead to pitfalls. The document outlines different aspects that can be measured in development, operations, and finance. It advocates relating measures to key performance indicators and using tools and machine learning to help deal with large volumes of data from measures. Automation is also emphasized.
Better Payroll Days Ahead with Automated, Cloud-Based Time and Attendance
Processing payroll may not be a day at the beach, but it doesn’t have to be a chore. According to the IRS, 33% of employers make costly payroll errors each year that result in billions of dollars in penalties. Why does this happen? We all know that payroll isn’t just about adding up the hours an employee works over a period of time, multiplying those hours by a rate, and then cutting the employee a check. There is a seemingly endless list of variables to factor in, such as local, state and federal labor law compliance (such as the ACA); PTO accruals; job costing; expense tracking for items such as tips or uniform deductions; and the list goes on and on. Multiply all of that by different pay policies for different groups of employees, and take into account union versus non-union workers, and the payroll process becomes even more complicated. In this free webinar, nettime solutions will show you how using automated, cloud-based time and attendance with web service integrations will convert your payroll processing chores into big wins for your company by eliminating errors, improving productivity, and maintaining data integrity so that payday is a great day for everyone involved.
Steve Lawrence - Agile Metrics
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.
UX Australia - voice of customer in the product lifecycle
Responding to the introduction of the Net Promoter score in a large organisation through the establishment of an operationalised testing program that covers, usability, product features, and importantly, service experience. Large companies need to have a particular emphasis on service experiences as these tend to be very polarising and emotive. This case study shows how Telstra, with help from consultancy U1 Group, created a program to ensure that product and service development processes create user experiences that result in advocacy.
More Related Content
What's hot
With Cloud Computing, Who Needs Performance Testing?
With cloud computing we can add more hardware resources on the fly. Considering how expensive load and stress testing can be, why don't we just add more power when needed?
This presentation will explain why, especially for situations where cloud computing is available, load and stress testing often falls short but is still required. It will also show how the queuing theory can provide a different approach which allows load and stress testers to add real value. Stakeholders and test managers can use the same theory to get a handle on the coverage and depth of the tests.
Key Takeaways:
- Why performance testing so often fails to accomplish what we want
- Why relying on cloud computing alone is not enough
- How the queuing theory can provide a different approach to performance testing
- How the queuing theory can help you understand if the performance tests
www.eurostarconferences.com
www.testhuddle.com
Toyota Kata at MYOB - Cycle Time
This document discusses continuous improvement at MYOB. It defines what an "awesome" way of working entails, including delivering high quality outcomes quickly, having self-organizing teams that are happy and engaged. It also discusses assessing the current processes, which include practices like refactoring, pair programming and metrics like cycle time, lead time, and customer happiness. It recommends collecting cycle time metrics to identify improvement opportunities like inconsistent story sizes, work in progress limits, and forecasting. Reducing high cycle times could involve clearer story definition and acceptance criteria.
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.
E-Roster Project
This document provides a guide for implementing benefits realization from a rostering improvement project. It outlines a process that begins with gathering baseline data on current spending, fill rates, and non-effective rostering. Training is then provided on rostering theory and creating a roster template. The first roster is implemented after one month, and reviews are conducted at 2, 3, and 4 months to evaluate impacts on costs, fill rates, overtime usage, and other metrics. The goal is to identify actions to improve rostering performance and efficiency over time. Regular monitoring will help ensure agreed-upon actions are implemented and wards are properly administered. While all issues may not be solved, this provides an initial framework to start identifying areas for rostering improvements
Agile Estimation
We’re agile, so we don’t have to estimate and have no deadlines, right? Wrong! This session will review the problem with estimations in projects today and then give an overview of the concept of agile estimation and the notion of re-estimation. We’ll learn about user stories, story points, team velocity, and 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 TFS and much more.
Getting To Product Market Fit Quickly
This 1-hour workshop marries the best practices from product strategy with those of fast and efficient technology teamwork and delivery. You’ll learn how to get your product organization working as a single cohesive, well-oiled machine to deliver the right product to market as quickly as possible. We will cover how to use both qualitative and quantitative measures to ensure that your product is solving the right problem; how to optimize and streamline the way your team designs, builds, and deploys software to your customers; and, how to beat the competition in strategy and execution.
BA World Boston: Evening the Odds with Monte Carlo Project Forecasting
This document discusses using Monte Carlo forecasting to predict project completion dates. It explains that Monte Carlo forecasting acknowledges variability and uncertainty by running multiple simulations of random task durations to predict a range of possible completion dates. The document provides instructions for creating a Monte Carlo forecast, discusses how the technique was used on a project, and notes some limitations and variations of the approach.
Lean Practices For Software Development
Lean practices for software development focus on maximizing customer value while minimizing waste. This includes reducing partially completed work, extra processes, extra features, task switching, waiting, motion, and defects. Developers should take an economic view by quantifying the cost of delay. They should also manage queues to reduce wait times, exploit variability while maintaining economic impact, reduce batch sizes to improve cycle times, apply work-in-progress constraints, and accelerate feedback through small batches.
Finance Presentation
The document discusses accounting and finance processes and systems at WGUK. It identifies several key issues: data accuracy problems across systems from meter points to invoices; a lack of validation processes between integrated systems; and a need for proper testing before new systems go live. It recommends: understanding problems fully before taking action; introducing validation and testing rigorously; focusing initially on fixing meter point and data accuracy issues; training staff; and establishing accurate budgets and processes for long-term improvement.
Stop using spreadsheets to monitor quality in your call centre!
The document describes a quality assessment solution called Scorebuddy that delivers real results, makes the job easier, and helps impress bosses. It provides rapid return on investment, improves agent and team performance, and allows managers and supervisors to make decisions using reports and analytics. Scorebuddy is easy to use, gives all information in one place, and saves time.
Implementing infinity hr (katie cuthriell)
This document outlines the key steps for successfully implementing the InfinityHR system. It discusses (1) planning and preparing by understanding needs, setting goals, and building a timeline, (2) designing an optimal solution by focusing on priorities and recommendations, (3) building by providing clean data and consistent communication, and (4) testing and training through engaging sessions and practicing tasks to ensure expertise before (5) deploying the system and scheduling follow up meetings for ongoing success.
agile_flow
The document outlines the Scrum process for managing product development, including estimating story points, prioritizing stories, committing to a sprint backlog, tracking progress daily, and meeting at the end of each sprint to review outcomes and plan improvements. Key steps involve breaking down features into user stories with acceptance criteria, estimating story effort, committing to complete specific stories each sprint, tracking task progress, addressing any issues that arise, demoing completed work, and retrospecting on lessons learned.
Invoice reading made simple
This EasySeparate Presentation shows how to make invoice reading simple and affordable for any SMB company.
Agile brazil2013poised
The document discusses business agility and how to achieve it through continuous experimentation, rapid feedback, and keeping systems poised for change. It outlines factors like agile software development principles, internal software quality measures, evolutionary architecture principles, and continuous delivery practices. These help lower the cost and risk of experimentation while maximizing visibility and feedback. The goal is for the business to be agile through experimenting often, being prepared to change quickly yet safely, and relying on evidence over guesses to balance predictability and opportunities.
Humans by the hundred (DevOps Days Ohio)
1) The document discusses how human fallibility and increased development teams can lead to an exponential decay in the probability of successful deployments over time as the number of changes increases.
2) It recommends approaches like implementing a service-oriented architecture, focusing on mean time to recovery rather than just preventing failures, and establishing "DevOps deputies" to help mitigate this problem.
3) The key message is that organizations should embrace DevOps culture, tailor their approaches to their specific teams, plan for inevitable changes over time, and view components as distributed from the beginning.
Flow Efficiency, the most powerful improvement driver - Scrum Australia 2018
The document discusses flow efficiency, which is a measure of how much time is spent on valuable work versus waiting. It defines flow efficiency and explains why organizations should focus on improving it. Flow efficiency is calculated by dividing touch time by lead time. The document provides tips for how to measure, analyze sources of delay, and improve an organization's flow efficiency through principles like limiting work-in-progress and reducing dependencies. The biggest leverage for improving productivity is reducing delays rather than improving individual performance.
Introduction of Kanban metrics
One of the powerful aspects of Kanban is the statistical analysis of its metrics. This presentation talks about common Kanban metrics and how to interpret them.
Implementing InfinityHR
The document outlines the key steps for implementing a new HR system called InfinityHR, including plan and prepare, design, build, testing and training, and deployment. Plan and prepare involves setting goals, organizing teams, documenting requirements, and preparing clients. Design focuses on optimizing business processes. Build requires clean data and consistent communication. Testing and training dedicates time to thoroughly test the system and make training engaging. Deployment ensures clients control the system and receive check-ins for ongoing success.
Measurement magic in world of DevOps
This document discusses the importance of measurement in software development and operations. It notes that measurement is needed as a basis for decisions, to gain situational awareness, and for improvement. However, what is measured needs to be useful, as measuring the wrong things can lead to pitfalls. The document outlines different aspects that can be measured in development, operations, and finance. It advocates relating measures to key performance indicators and using tools and machine learning to help deal with large volumes of data from measures. Automation is also emphasized.
Better Payroll Days Ahead with Automated, Cloud-Based Time and Attendance
Processing payroll may not be a day at the beach, but it doesn’t have to be a chore. According to the IRS, 33% of employers make costly payroll errors each year that result in billions of dollars in penalties. Why does this happen? We all know that payroll isn’t just about adding up the hours an employee works over a period of time, multiplying those hours by a rate, and then cutting the employee a check. There is a seemingly endless list of variables to factor in, such as local, state and federal labor law compliance (such as the ACA); PTO accruals; job costing; expense tracking for items such as tips or uniform deductions; and the list goes on and on. Multiply all of that by different pay policies for different groups of employees, and take into account union versus non-union workers, and the payroll process becomes even more complicated. In this free webinar, nettime solutions will show you how using automated, cloud-based time and attendance with web service integrations will convert your payroll processing chores into big wins for your company by eliminating errors, improving productivity, and maintaining data integrity so that payday is a great day for everyone involved.
What's hot (20)
With Cloud Computing, Who Needs Performance Testing?
With Cloud Computing, Who Needs Performance Testing?
BA World Boston: Evening the Odds with Monte Carlo Project Forecasting
BA World Boston: Evening the Odds with Monte Carlo Project Forecasting
Stop using spreadsheets to monitor quality in your call centre!
Stop using spreadsheets to monitor quality in your call centre!
Flow Efficiency, the most powerful improvement driver - Scrum Australia 2018
Flow Efficiency, the most powerful improvement driver - Scrum Australia 2018
Better Payroll Days Ahead with Automated, Cloud-Based Time and Attendance
Better Payroll Days Ahead with Automated, Cloud-Based Time and Attendance
Similar to Batting Averages and Slugging %s
Steve Lawrence - Agile Metrics
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.
UX Australia - voice of customer in the product lifecycle
Responding to the introduction of the Net Promoter score in a large organisation through the establishment of an operationalised testing program that covers, usability, product features, and importantly, service experience. Large companies need to have a particular emphasis on service experiences as these tend to be very polarising and emotive. This case study shows how Telstra, with help from consultancy U1 Group, created a program to ensure that product and service development processes create user experiences that result in advocacy.
Toc Education
The document discusses using Critical Chain Project Management (CCPM) to better manage project risk and variation. It explains that CCPM uses buffers and the theory of constraints to protect project due dates from the effects of variation. Projects are scheduled using a critical chain approach which identifies the critical chain of tasks and calculates buffers based on statistical analysis of variation. This allows the project schedule to function as a predictive model and maintain protection ratios to keep customers insulated from impacts of variation.
TC23 - Wiiisdom Presentation
We’ve all been there. You rushed, published a dashboard, & missed a few errors. Good news! Catastrophe is preventable—without extra work! Join ex-Tableau leaders to discover what's next: AnalyticsOps!
Why You Don't Want to be a Tester; an agile discussion
"Why You Don't Want to be a Tester" focuses on a common discussion we are having among Quality Assurance and Software Testing professionals, especially as it relates to operating as part of an agile team.
In a recent discussion at the Software QA User Group in Portland Oregon, Brett used these slides to foster conversation and to promote the idea that each person should be proactive in their approach to not allow their role to simply become a tester. Solid QA practices are needed more today than ever as we move fast and raise the bar on quality and continually add to our tool belt!
Csp
This document proposes a group award system to evaluate Performance Improvement and Accountability Groups (PAGs) for a Local Health Integration Network (LHIN). It includes:
1) A radial assessment tool to measure PAG performance on factors like goals, strengths, weaknesses, and impact.
2) Awards would be given after key reviews to recognize high-achieving, self-motivated teams and fuel competition.
3) Benefits include enhancing teamwork, improving performance, and recognizing achievement. Rewards could include plaques, certificates, or training courses.
4) The tool is demonstrated through a sample calculation for a cardiology team's performance assessment.
Humans by the hundred
This document discusses how scaling teams to support big data growth at Yelp can negatively impact deployment speed due to an exponential increase in the probability of failures as the number of developers increases. It proposes service-oriented architecture and focusing on mean time to recovery rather than just preventing failures as ways to mitigate these risks and maintain rapid iteration. Continuous delivery, reliable but not exhaustive testing, and treating all processes as distributed are also recommended to support scaling teams while preserving deployment speed.
ImpactAgile_Quantified
This document analyzes data from over 9,000 software teams using an Agile project management platform to identify practices that improve team performance. It finds that fully dedicating team members to a single stable team can double productivity and halve time to market. Following a "full Scrum" process of estimating stories and tasks provides the best overall results, especially for quality, though a "lightweight Scrum" approach without task estimates performs nearly as well. Maintaining low work-in-process levels can cut time spent on work items in half compared to teams with high work-in-process. The document recommends dedicating team members, keeping teams stable, using a full or lightweight Scrum process, and controlling work-in-
Impact_Agile_Quantified
This document summarizes key findings from analyzing data from over 9,000 software teams using an Agile project management platform. It finds that dedicating team members to a single team and maintaining stable team membership significantly improves productivity, quality, predictability, and time to market. Specifically, it shows nearly doubling productivity and halving time to market when team dedication is over 95%, and improvements of up to 60% in these areas when team stability exceeds 90%. However, the data shows team stability is generally low, with about a quarter of members changing every 3 months on average. It recommends dedicating people to one team and keeping teams stable to realize substantial performance gains.
[CXL Live 16] Beyond Test-by-Test Results: CRO Metrics for Performance & Insi...
Individual tests drive insights & ROI, but the most sophisticated optimizers look beyond what an individual test is telling them and use data to optimize their overall testing performance.
In this talk, Claire will dive into the specifics of how to track, improve, and drive insight from performance metrics for your conversion program, so you can not only run better tests, but get more out of your investment in CRO.
LITE 2018 – A Deep Dive Into Communication Triggers [Terry Woods]
1. The document discusses using communication triggers in an event management system to automate emails. Triggers allow setting criteria to send standardized communications like registration confirmations and reminders.
2. Triggers save significant time over manual communications. An example shows sending 600 pre-event emails could take 2.5-5 hours manually but triggers automate it.
3. Tips are provided for setting up different trigger scenarios for events, including registration, pre-event, during event, post-event, and scheduled communications. Consistency, staggered timing, and multi-channel messages are recommended.
Bringing Continuous Delivery to Dell.com: A Retrospective
Multibillion dollar sales portal Dell.com has more than 1,000 developers working in tandem to contribute content and code. This presents unique strategic challenges when it comes to selecting, planning, and deploying DevOps tools. James Watt presents a retrospective on transitioning one of the world’s largest grossing websites from a quarterly waterfall delivery cadence to weekly agile releases. Learn how “continuous” principles changed the way Dell.com improves its user experience and the tools that made it possible. Starting with a legacy waterfall delivery chain, the Buyer DevOps team had to design, develop, and roll out a staged plan to transition from monolithic integration environments linked by bespoke engineering to dynamically provisioned and continuously-tested cloud infrastructure based on industry-leading toolsets. James describes TeamCity and Octopus integration with Team Foundation Server and other Microsoft products, large scale C# Selenium test automation, and dynamic virtual environment provisioning along with continuous integration, continuous testing, and other rapid release concepts.
Advance ALM and DevOps Practices with Continuous Improvement
Do you want to improve your application lifecycle and incorporate DevOps practices quickly with limited resources? If so, you’re experiencing a common scenario – not enough budget and unrealistic time constraints. Your big multi-year application lifecycle management (ALM) project seems less achievable than ever, and you are left wondering how to move forward. Jason St-Cyr shares how to establish a continuous improvement approach using “build, measure, learn” techniques and a DevOps maturity model to kickstart your DevOps/ALM project. Jason reviews some of the tools—Visual Studio Online, Atlassian OnDemand, and TeamCity—available to support iterative DevOps changes. Find out how to tackle smaller achievable chunks of process improvement, even when time does not seem to be on your side. Learn how to plan for incremental organizational change and examine metrics for monitoring improvements, reporting on success, and supporting your business case for further investment. Join Jason to see why you don’t have to put your organization’s DevOps initiatives on hold.
Estimate and Measure. Minimize work, maximize value. Part 2
Discover in this deck different output and outcome metrics, have an overview of popular impact metrics and get a link to an estimation exercise.
Want to attend our next webinar? Become a Shiftup Explorer: https://shiftup.work/product/explorer-agility-innovation-qualification-program/
Error-Proofing in Office & Service Environments
Recorded webinar: http://bit.ly/LfQXrJ
Subscribe: http://www.ksmartin.com/subscribe
Karen’s Books: http://ksmartin.com/books
Want better estimation ?
The document discusses estimation techniques. It presents five estimation laws: 1) Don't estimate if you can measure, 2) compare instead of estimating units, 3) measure things that are measurable, 4) reduce precision of estimates based on knowledge, and 5) use different metrics for different estimates. Good practices discussed include using story sizing for requirements, measuring in hours for small tasks, using velocity, splitting large stories, and measuring fixed cycle times. The document provides resources for further learning about agile estimation techniques.
Embracing service-level-objectives of your microservices in your Cl/CD
Embracing service-level-objectives of your microservices in your Cl/CD
This presentation discusses defining service level objectives (SLOs) for microservices and using them to automate quality gates in continuous integration/continuous delivery (CI/CD) pipelines. It presents the open-source Keptn framework, which can provide quality gates for microservices running on Kubernetes clusters based on defined SLOs. The presentation covers how SLOs and service level indicators (SLIs) can help prevent bad code from reaching production and configure alerts, and demonstrates Keptn's automated SLO evaluation and a use case for performance as a self-service tool.
Agile DC Lead Time
This document discusses lead time and how measuring and understanding it can help forecast projects. It defines lead time as the time between one event preceding another. Lead time data can be more useful than just average times since it accounts for variability. The document also discusses using distributions to model different types of work instead of single numbers, as processes are probabilistic rather than deterministic. Measuring lead time and understanding its distribution is important for planning delivery rates and work in process.
Global qa conference updated
This document summarizes the key points from a seminar on quality and productivity. It discusses the customer mission of delivering excellent quality products on time and on budget. It outlines Next's expectations for suppliers to meet customer expectations. It also discusses challenges like price pressures and how improvements can be made through techniques like lean manufacturing, reducing waste, and improving internal processes and training.
CRMUG UK November 2015 - Testing testing! Panel Discussion with Scott Durow, ...
This document provides information about a panel session on testing Dynamics CRM. The panel will include Scott Durow, Sarah Critchley, and Priscilla Tse and will discuss challenges and best practices for unit testing, integration and system testing, and user acceptance testing. Brief biographies are provided for each panelist along with an agenda laying out the session structure and topics.
Similar to Batting Averages and Slugging %s (20)
UX Australia - voice of customer in the product lifecycle
UX Australia - voice of customer in the product lifecycle
Why You Don't Want to be a Tester; an agile discussion
Why You Don't Want to be a Tester; an agile discussion
[CXL Live 16] Beyond Test-by-Test Results: CRO Metrics for Performance & Insi...
[CXL Live 16] Beyond Test-by-Test Results: CRO Metrics for Performance & Insi...
LITE 2018 – A Deep Dive Into Communication Triggers [Terry Woods]
LITE 2018 – A Deep Dive Into Communication Triggers [Terry Woods]
Bringing Continuous Delivery to Dell.com: A Retrospective
Bringing Continuous Delivery to Dell.com: A Retrospective
Advance ALM and DevOps Practices with Continuous Improvement
Advance ALM and DevOps Practices with Continuous Improvement
Estimate and Measure. Minimize work, maximize value. Part 2
Estimate and Measure. Minimize work, maximize value. Part 2
Embracing service-level-objectives of your microservices in your Cl/CD
Embracing service-level-objectives of your microservices in your Cl/CD
CRMUG UK November 2015 - Testing testing! Panel Discussion with Scott Durow, ...
CRMUG UK November 2015 - Testing testing! Panel Discussion with Scott Durow, ...
Recently uploaded
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.
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
AWS Cloud Cost Optimization Presentation.pptx
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
A Comprehensive Guide to DeFi Development Services in 2024
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
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.
Taking AI to the Next Level in Manufacturing.pdf
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Azure API Management to expose backend services securely
How to use Azure API Management to expose backend service securely
Introduction of Cybersecurity with OSS at Code Europe 2024
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
dbms calicut university B. sc Cs 4th sem.pdf
Its a seminar ppt on database management system using sql
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
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.
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.
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
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!
Recently uploaded (20)
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
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...
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Deep Dive: Getting Funded with Jason Jason Lemkin Founder & CEO @ SaaStr
Deep Dive: Getting Funded with Jason Jason Lemkin Founder & CEO @ SaaStr
A Comprehensive Guide to DeFi Development Services in 2024
A Comprehensive Guide to DeFi Development Services in 2024
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
Azure API Management to expose backend services securely
Azure API Management to expose backend services securely
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
System Design Case Study: Building a Scalable E-Commerce Platform - Hiike
System Design Case Study: Building a Scalable E-Commerce Platform - Hiike
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Batting Averages and Slugging %s
- 1. Batting Averages and Slugging %s Matt Story // VP Engineering Handshake
- 2. Why I Don’t Care About Team Velocity And neither should you.
- 3. Why Process Infrastructure? We’re usually optimizing for up to 3 things
- 5. Predictability Consistency of time to value
- 6. Sustainability Value over the long haul
- 8. 0 25 50 75 100 Velocity Effort Actual Team Effort Sprint-over-Sprint
- 9. It Rewards Padding Which isn’t really predictability
- 10. And it’s a bad predictor When you have historical data 50% 75% 98%
- 11. Effort <> Value Unfortunately effort is not that important
- 12. ‘L’ Value Batting Average Weeks with a ‘L’ Value Delivery / Weeks
- 13. It Rewards Iteration More ‘L’ Value Releases the Better …
- 14. It Rewards Value/Effort Arbitrage ‘L’ Value / ‘S’ Effort is best
- 15. Informing Prioritization Decisions “Stack” ranking for Value / Effort
- 16. And Producing Results In first quarter using stack, against .357 the prior quarter .769 10 weeks with launches / 14 weeks
- 17. But it Over-values Home Runs ... wrong town for this slide*
- 18. But Over-values Home Runs Much better.
- 19. ‘XL’ Value Eq Batting Average Weeks with the equivalent of an ‘XL’ Value Delivery / Weeks
- 20. Slugging % ‘L’ Value Equivalents / Weeks
- 21. Slugging % In first quarter using stack, compared to .446 quarter prior. 1.654
- 22. Silver Slugger Award Given every month to engineer with highest Slugging %
- 23. Not Counting Weeks on Support Which are like sacrifice plays