The document discusses the limitations of using velocity as a key metric in agile development. It argues that velocity is a lagging indicator that tells you what happened in the past rather than providing insight into the present. Relying too heavily on velocity to plan future work can be misleading if the conditions change. The document recommends using a balanced set of metrics including factors like quality, team well-being and flow through the development pipeline to get a more holistic view of project health and performance.
How do you cut the Big Data clutter and tell interesting, insightful and impacting stories? This session talks about the need for Data Visualization & how Visual stories can come to the aid of the Big Data problem associated with meaningful consumption. The point is illustrated by leveraging several industry case studies.
Velocity is one of the most common metrics used—and one of the most commonly misused—on agile projects. Velocity is simply a measurement of speed in a given direction—the rate at which a team is delivering toward a product release. As with a vehicle en route to a particular destination, increasing the speed may appear to ensure a timely arrival. However, that assumption is dangerous because it ignores the risks with higher speeds. And while it’s easy to increase a vehicle’s speed, where exactly is the accelerator on a software team? This presentation covers Hawthorne Effect and Goodhart’s Law to explain why setting goals for velocity can actually hurt a project's chances. Take a look at what can negatively impact velocity, ways to stabilize fluctuating velocity, and methods to improve velocity without the risks.
Data-Driven DevOps: Improve Velocity and Quality of Software Delivery with Me...Splunk
Much of the value of DevOps comes from a (renewed) focus on measurement, sharing, and continuous feedback loops. In increasingly complex DevOps workflows and environments, and especially in larger, regulated, or more crystallized organizations, these core concepts become even more critical.
This session will show how, by focusing on 'metrics that matter,' you can provide objective, transparent, and meaningful feedback on DevOps processes to all stakeholders. Learn from real-life examples how to use the data generated throughout application delivery to continuously identify, measure, and improve deployment speed, code quality, process efficiency, outsourcing value, security coverage, audit success, customer satisfaction, and business alignment.
AgileLIVE Webinar: Measuring the Success of Your Agile Transformation - Part 2VersionOne
The key to a successful agile journey is to identify concrete, measurable goals. Whether your challenge is to improve software quality, time to market, productivity, customer satisfaction, innovation, employee engagement, or some combination of these, agile metrics are crucial to your success. How do you use agile metrics early and often to know that you’re going in the right direction? And how do you know when your goals have been met? This set of slides shows you how to do it using VersionOne. Watch the recording here: http://bit.ly/1m1nXEl
Agile Metrics : Velocity is NOT the Goal - NDC Oslo 2014Doc Norton
Velocity is one of the most common metrics used-and one of the most commonly misused-on agile projects. Velocity is simply a measurement of speed in a given direction-the rate at which a team is delivering toward a product release. As with a vehicle en route to a particular destination, increasing the speed may appear to ensure a timely arrival. However, that assumption is dangerous because it ignores the risks with higher speeds. And while it’s easy to increase a vehicle’s speed, where exactly is the accelerator on a software team?
Michael “Doc" Norton walks us through the Hawthorne Effect and Goodhart’s Law to explain why setting goals for velocity can actually hurt a project's chances. Take a look at what can negatively impact velocity, ways to stabilize fluctuating velocity, and methods to improve velocity without the risks. Leave with a toolkit of additional metrics that, coupled with velocity, give a better view of the project's overall health.
How do you cut the Big Data clutter and tell interesting, insightful and impacting stories? This session talks about the need for Data Visualization & how Visual stories can come to the aid of the Big Data problem associated with meaningful consumption. The point is illustrated by leveraging several industry case studies.
Velocity is one of the most common metrics used—and one of the most commonly misused—on agile projects. Velocity is simply a measurement of speed in a given direction—the rate at which a team is delivering toward a product release. As with a vehicle en route to a particular destination, increasing the speed may appear to ensure a timely arrival. However, that assumption is dangerous because it ignores the risks with higher speeds. And while it’s easy to increase a vehicle’s speed, where exactly is the accelerator on a software team? This presentation covers Hawthorne Effect and Goodhart’s Law to explain why setting goals for velocity can actually hurt a project's chances. Take a look at what can negatively impact velocity, ways to stabilize fluctuating velocity, and methods to improve velocity without the risks.
Data-Driven DevOps: Improve Velocity and Quality of Software Delivery with Me...Splunk
Much of the value of DevOps comes from a (renewed) focus on measurement, sharing, and continuous feedback loops. In increasingly complex DevOps workflows and environments, and especially in larger, regulated, or more crystallized organizations, these core concepts become even more critical.
This session will show how, by focusing on 'metrics that matter,' you can provide objective, transparent, and meaningful feedback on DevOps processes to all stakeholders. Learn from real-life examples how to use the data generated throughout application delivery to continuously identify, measure, and improve deployment speed, code quality, process efficiency, outsourcing value, security coverage, audit success, customer satisfaction, and business alignment.
AgileLIVE Webinar: Measuring the Success of Your Agile Transformation - Part 2VersionOne
The key to a successful agile journey is to identify concrete, measurable goals. Whether your challenge is to improve software quality, time to market, productivity, customer satisfaction, innovation, employee engagement, or some combination of these, agile metrics are crucial to your success. How do you use agile metrics early and often to know that you’re going in the right direction? And how do you know when your goals have been met? This set of slides shows you how to do it using VersionOne. Watch the recording here: http://bit.ly/1m1nXEl
Agile Metrics : Velocity is NOT the Goal - NDC Oslo 2014Doc Norton
Velocity is one of the most common metrics used-and one of the most commonly misused-on agile projects. Velocity is simply a measurement of speed in a given direction-the rate at which a team is delivering toward a product release. As with a vehicle en route to a particular destination, increasing the speed may appear to ensure a timely arrival. However, that assumption is dangerous because it ignores the risks with higher speeds. And while it’s easy to increase a vehicle’s speed, where exactly is the accelerator on a software team?
Michael “Doc" Norton walks us through the Hawthorne Effect and Goodhart’s Law to explain why setting goals for velocity can actually hurt a project's chances. Take a look at what can negatively impact velocity, ways to stabilize fluctuating velocity, and methods to improve velocity without the risks. Leave with a toolkit of additional metrics that, coupled with velocity, give a better view of the project's overall health.
Using SPC to Make Better Management DecisionsMark Graban
In this webinar (sponsored by Gemba Academy), Mark Graban, author of Lean Hospitals, will show how simple statistical process control (SPC) methods can be used by managers and leaders to make better decisions about their businesses.
Using examples from manufacturing, healthcare, and services industries, Mark will illustrate the basic SPC rules and will show you how to create and interpret a control chart, allowing you to spot statistically valid trends and avoid overreacting to common cause variation in your performance measures.
Please join us for a lively discussion and interactive Q&A!
http://www.MarkGraban.com
http://www.GembaAcademy.com
Updated version of this talk as presented at Pacific Northwest Software Quality Conference in 2012. This is a longer version, including content on scatter diagrams and standard deviation.
This Presentation course will help you in understanding the Machine Learning model i.e. Generalized Linear Models for classification and regression with an intuitive approach of presenting the core concepts
Agile and Beyond 2017 Presentation on Tuckman's Theory of Team Development. This theory was based on non-scientifically gathered surveys and has never been empirically proven despite dozens of scientific attempts. This talk covers why stable teams may have been a good thing and why we want to consider dynamic teams as we face new challenges.
The world as we know it is growing more complex. As we automate away those things that can be easily repeated, we leave ourselves with ever more challenging work. The way we've worked in the past won't necessarily work for today's problems¦ or will it? Join Diane and Doc as they explore dimensions of complexity in software development and look at how teams and leaders might adjust their behaviors (and the software they create) based on the complexity of the problem at hand.
This hands-on, interactive workshop will provide a practical introduction to Cynefin (a sense-making framework for complexity) and show how it applies to the work we do every day as creators of software. You'll map your own work to Cynefin and learn about applicable management styles and optimal team interactions for each of the Cynefin contexts.
Using SPC to Make Better Management DecisionsMark Graban
In this webinar (sponsored by Gemba Academy), Mark Graban, author of Lean Hospitals, will show how simple statistical process control (SPC) methods can be used by managers and leaders to make better decisions about their businesses.
Using examples from manufacturing, healthcare, and services industries, Mark will illustrate the basic SPC rules and will show you how to create and interpret a control chart, allowing you to spot statistically valid trends and avoid overreacting to common cause variation in your performance measures.
Please join us for a lively discussion and interactive Q&A!
http://www.MarkGraban.com
http://www.GembaAcademy.com
Updated version of this talk as presented at Pacific Northwest Software Quality Conference in 2012. This is a longer version, including content on scatter diagrams and standard deviation.
This Presentation course will help you in understanding the Machine Learning model i.e. Generalized Linear Models for classification and regression with an intuitive approach of presenting the core concepts
Agile and Beyond 2017 Presentation on Tuckman's Theory of Team Development. This theory was based on non-scientifically gathered surveys and has never been empirically proven despite dozens of scientific attempts. This talk covers why stable teams may have been a good thing and why we want to consider dynamic teams as we face new challenges.
The world as we know it is growing more complex. As we automate away those things that can be easily repeated, we leave ourselves with ever more challenging work. The way we've worked in the past won't necessarily work for today's problems¦ or will it? Join Diane and Doc as they explore dimensions of complexity in software development and look at how teams and leaders might adjust their behaviors (and the software they create) based on the complexity of the problem at hand.
This hands-on, interactive workshop will provide a practical introduction to Cynefin (a sense-making framework for complexity) and show how it applies to the work we do every day as creators of software. You'll map your own work to Cynefin and learn about applicable management styles and optimal team interactions for each of the Cynefin contexts.
Building Blocks of a Knowledge Work Culture - NDC London 2016Doc Norton
Re-designed presentation on Autonomy, Connection, Excellence, and Diversity. This version shows a bit more about the management styles appropriate in different domains of complexity, connects knowledge work to Complicated and Complex, and then walks through the Building Blocks.
Even high functioning teams occasionally have a hard time making decisions or coming up with creative ideas. There are times when the conversation seems to drag on long after a decision is reached. There are times when we have too many people involved in the discussion or the wrong people involved. There are times when we’re not sure whose the actual decision maker. And there are those times when we just seem to be out of synch with each other. This creative collaboration workshop provides tools that help resolve all of these issues.
Among the traits that distinguish a good team from a great team is their ability to innovate. Despite the rhetoric in favor of innovation, most organizations are stuck in an implementation mindset, stifling creativity, excellence, and the resultant innovation. The experimentation mindset frees us from self-imposed constraints, allowing us to continually learn and improve. In this session, we'll talk about how we learn as individuals and how we learn as organizations. We'll take a look at some examples of the experimentation mindset happening in the agile community today and we'll talk about how you can foster such a mindset in your own organization.
This is a version of the talk given at Dev Bootcamp in Chicago.
Technical Debt has become a catch-all phrase for any code that needs to be re-worked. Much like Refactoring has become a catch-all phrase for any activity that involves changing code. These fundamental misunderstandings and comfortable yet mis-applied metaphors have resulted in a plethora of poor decisions. What is technical debt? What is not technical debt? Why should we care? What is the cost of misunderstanding? What do we do about it? Doc discusses the origins of the metaphor, what it means today, and how we properly identify and manage technical debt.
Switching horses midstream - From Waterfall to AgileDoc Norton
You’ve been working for several months on a key software initiative for the company and leadership has decided they want it faster than projected, so the team has been told they’re getting “the agile” installed next week.
“Great.”, you think, “Right in the middle of the project. Nothing like changing horses in midstream. One way or another, this will go swimmingly.”
Sarcasm and puns aside, you’ve got a point. It isn’t easy to switch methodologies in the middle of a project. Doc shares some stories from his own experiences helping teams make this change and provides a few pointers that can help you do the same.
While this talk is focused on testing, it involves the whole team, as agile methods usually do.
Autonomy, Connection, and Excellence; The Building Blocks of a DevOps CultureDoc Norton
DevOps, to a great extent, is about people working together. Without true cross-discipline collaboration, the full value of DevOps cannot be realized.
But you can’t just mandate collaboration. Many organizations do more than separate developers and operations, they design systems, metrics, and rewards that make the two seem like natural enemies. “They don’t get it.”, you hear from both sides.
In this talk, Doc will take a look at what motivates teams, how our systems produce the exact results we design them to produce, and how we can use simple (but not necessarily easy) techniques to counter years of “us versus them” conditioning.
From NDC Oslo 2015 - Workshop with Denise Jacobs, Doc Norton, and Carl Smith
Even high functioning teams occasionally have a hard time making decisions or coming up with creative ideas. There are times when the conversation seems to drag on long after a decision is reached. There are times when we have too many people involved in the discussion or the wrong people involved. There are times when we're not sure whose the actual decision maker. And there are those times when we just seem to be out of synch with each other. This creative collaboration workshop provides tools that help resolve all of these issues. Come have some laughs with Denise, Doc, and Carl, play with new friends, and learn one or two new techniques you can try at home.
SDEC 2014 Keynote - Among the traits that distinguish a good team from a great team is their ability to innovate. And despite the rhetoric in favor of innovation, most organizations are stuck in an implementation mindset, stifling creativity, excellence, and the resultant innovation. The experimentation mindset frees us from self-imposed constraints, allowing us to continually learn and improve.
Technical Debt has become a catch-all phrase for any code that needs to be re-worked. Much like Refactoring has become a catch-all phrase for any activity that involves changing code. These fundamental misunderstandings and comfortable yet mis-applied metaphors have resulted in a plethora of poor decisions. What is technical debt? What is not technical debt? Why should we care? What is the cost of misunderstanding? What do we do about it? Doc discusses the origins of the metaphor, what it means today, and how we properly identify and manage technical debt.
How does the common cold spread through a group of friends or co-workers. What about other contagions? Can a contagion be used for good? Doc explores how things like disease, politics, and even moods travel through (meat-space) social networks. What impact do we have on others? What impact do they have on us? And what does this mean for members of the software development community?
Teamwork ain’t always easy. From meetings where everybody has something to say but nothing gets done to poor decisions being made because the most senior or most forceful team member won the argument; sometimes you long for the days of high-walled cubicles and lone ranger coding. Long no more.
In this workshop, you will learn a few simple techniques that drastically improve a team’s ability to work together toward common goals with less conflict and more genuine collaboration.
Creating a Global Engineering Culture - Agile india 2014Doc Norton
A short (and incomplete) telling of how we got to where we are as an engineering organization for Groupon. A little philosophy about what motivates individuals and teams. And finally a little bit about what we're doing at Groupon.
When it comes to creating a global culture, remember that you are more archeologist than architect. Uncover the good that is already happening and help to share it rather than trying to design something new.
Love is a Contagion. Let's Start an Epidemic.
This is the slide deck to go along with the Keynote I gave at That Conference in August 2013. This talk is all about the stories. The visuals support the stories told, but do not tell them on their own. I will add details to my blog and may upload another version of the slide deck with notes.
Agile Metrics: Velocity is NOT the Goal - Agile 2013 versionDoc Norton
A newly formatted version of "Velocity is NOT the Goal" for Agile 2013. I've removed some details about standard deviation, added a few more thoughts around the "psychology" of setting targets for metrics, and show a bit more about how we do this at Groupon.
Teamwork ain’t always easy. From meetings where everybody has something to say but nothing gets done to poor decisions being made because the most senior or most forceful team member won the argument; sometimes you long for the days of high-walled cubicles and lone ranger coding. Long no more.
In this workshop, you will learn about two simple techniques that drastically improve a team’s ability to work together toward common goals with less conflict and more genuine collaboration.
Growing Into Excellence talk given at the Pacific Northwest Software Quality Conference. This is yet another version on this theme. A little more on Collaboration 8 and Six Thinking Hats along with new material from Dave Hoover on stretching into incompetence.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
43. Seven Deadly Diseases
of
Western Management
1) Lack of constancy of purpose
2) Emphasis on short-term profit
3) Evaluation of performance, merit rating or annual reviews
4) Mobility of top management
5) Running a company on visible figures alone
6) Excessive medical costs
7) Excessive legal damage awards
71. Attributions
Planning By Velocity Photo
http://www.flickr.com/photos/carfull/4984803509/sizes/l/in/photostream/
Are You Confident Photo
http://www.brookston.org/photoblog/images/20060113083815_thumbs_up.jpg
Hugh Laurie Photo
http://www.freakingnews.com/pictures/58000/Hugh-Laurie-with-a-Thermometer-58178.jpg
Back to The Future
http://www.wallpaperdev.com/imageres/1920x1440-back-to-the-future-wallpaper-hd.jpg
Success Baby
http://ncclassof2013.files.wordpress.com/2013/04/success.jpg
Double Dutchess (Standard Deviants)
http://www.mtviggy.com/wp-content/uploads/2013/04/double_dutchess.jpg
Math is hard
http://www.washingtonpost.com/blogs/answer-sheet/files/2013/03/math.jpg
Past Doesn’t Equal The Future
http://sphotos-b.xx.fbcdn.net/hphotos-ash4/402800_10151021129543907_1273189465_n.jpg
You’re not hearing me
http://farm3.staticflickr.com/2670/3948482669_93d49c1dc8_o.jpg
Angry Tony
http://marcianitosverdes.haaan.com/wp-content/uploads/2012/07/TonyRobbins_thumb.jpg
Holding you back
http://sphotos-a.xx.fbcdn.net/hphotos-ash4/p480x480/382197_426710810746267_1475892304_n.jpg