Session Abstract:
Agile framework is based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. It’s a set of values and principles that help teams respond to unpredictability through incremental, iterative work cadences and continuous feedback.
Scrum is the most popular methodology under the Agile umbrella. Scrum emphasizes empirical feedback, team self-management, and striving to build shippable product increments within short iterations.
Kanban is another popular flavor of Agile that focuses on visualizing and managing the flow of work, in order to balance demand with available capacity and remove bottlenecks.
Learning Objectives:
> Gain a broad understanding of the Agile framework
> Discover Scrum and Kanban, the two most widely used Agile methodologies, and see how they can be used in construction industry
> Find out how Scrum and Kanban can be combined to have the best of both worlds (Scrumban)
This presentation introduces agile methodology, talks about scrum and the pros and cons of agile from a various perspectives. It also talks about cost of an agile project
Session Abstract:
Agile framework is based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. It’s a set of values and principles that help teams respond to unpredictability through incremental, iterative work cadences and continuous feedback.
Scrum is the most popular methodology under the Agile umbrella. Scrum emphasizes empirical feedback, team self-management, and striving to build shippable product increments within short iterations.
Kanban is another popular flavor of Agile that focuses on visualizing and managing the flow of work, in order to balance demand with available capacity and remove bottlenecks.
Learning Objectives:
> Gain a broad understanding of the Agile framework
> Discover Scrum and Kanban, the two most widely used Agile methodologies, and see how they can be used in construction industry
> Find out how Scrum and Kanban can be combined to have the best of both worlds (Scrumban)
This presentation introduces agile methodology, talks about scrum and the pros and cons of agile from a various perspectives. It also talks about cost of an agile project
Agile methodology is a framework for modern software development.
What is the philosophy behind Agile?
How does it differ from traditional project management strategies like waterfall?
What are the stages, meetings, tools, and team roles?
What is Scrum?
[To download this complete presentation, visit: https://www.oeconsulting.com.sg/training-presentations]
This introduction to Agile and Scrum is a presentation that provides a high-level overview of Agile and Scrum methodologies. The presentation is aimed at individuals who may have heard of Agile and Scrum but are not familiar with the concepts or principles.
The presentation begins with an introduction of the basic principles and values of Agile and Scrum, which includes an explanation of the Agile philosophy and principles, and an overview of the Scrum framework and its origins. It also discusses the benefits and drawbacks of Agile and Scrum and compares them to traditional project management methodologies.
The key roles and responsibilities within a Scrum team are discussed next, including the three key roles of Scrum Master, Product Owner, and Development Team. An explanation on how these roles interact with each other and the wider organization is provided.
The Scrum framework and its key components, including an overview of Sprints, Backlog, and Artifacts are also explained. The Scrum events, including Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective, are also covered.
Lastly, successful examples of how Agile and Scrum are used in various industries, such as software development, marketing, and education are presented. Discussions on how Agile and Scrum can be adapted to fit the needs of different projects and organizations are also provided.
By the end of the Agile and Scrum PPT presentation, attendees would have a solid foundation in Agile and Scrum methodologies, including a basic understanding of the principles and values, the Scrum framework and its key components, and the roles and responsibilities of the Scrum team. They would be equipped with the necessary knowledge to apply Agile and Scrum to their own work.
LEARNING OBJECTIVES
1. Understand the basic principles, values, benefits and drawbacks of Agile and Scrum.
2. Understand the key roles of the Scrum team, and the Scrum framework and its key components.
3. Understand how Agile and Scrum can be applied to various industries and projects and adapted to fit different situations.
Kanban Boards to visualize work
Kanban Systems to create a pull system of work limiting work in progress
Evolutionary Change based on Improved Decision-Making through Leadership & Self-Organization
Focus on Customer Needs recognizing work as a Flow of Value
Feedback loops and Metrics for Continuous Improvement
Agile Testing: A pragmatic overview and new entry in Intelliware’s Agile Methodology Series.
What you’ll learn in this presentation:
Intelliware’s Chief Technologist, BC Holmes, provides a pragmatic overview of Agile testing. Complete with many examples, this presentation is ideal for those looking for a practical take on software testing in an Agile environment.
The presentation covers:
- Why do we use Agile testing?
- What Agile testing isn’t
- What Agile testing is: unit testing and test-driven development (TDD)
- High-level properties of good tests
- Testing in different languages
- Test suites and code coverage
- Using mock objects to help isolate units
- Beyond unit testing
- Understand the principles behind the agile approach to software development
- Differentiate between the testing role in agile projects compared with the role of testers in non-agile projects
- Positively contribute as an agile team member focused on testing
- Appreciate the challenges and difficulties associated with the non-testing activities performed in an agile team
- Demonstrate a range of soft skills required by agile team members
Scaling Scrum using Lean/Kanban in AmdocsYuval Yeret
Learn how Amdocs and Agilesparks took an enterprise Scrum implementation to the next step with Lean/Kanban - Presented in the Lean Software and Systems Conference 2010 in Atlanta
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
XBOSoft runs through the Top 10 Agile Metrics revealing the most fundamental data points Agile methodology requires to work effectively, and will put you on the highly targeted path to successful implementation of your Agile processes.
XBOSoft and Go2Group run through the top data points you should be measuring in your Agile Workflow. We’ll show you what to track, when and how often, and most importantly – why. Many believe that metrics are useless, but unless you measure, how can you systematically improve or know how you are doing? And with velocity as an overarching objective in agile, you should be tracking other things so that you know what else you could be impacting by going faster. But, with all the metrics so readily available to us today, how do we filter through to the most meaningful?
A New Introduction to Jira & Agile Product ManagementDan Chuparkoff
These are the corresponding slides from another one of my talks in the series for Great Product Teams: https://www.youtube.com/watch?v=TsG3OWTDAFY
FOR MORE:
If your team wants to learn more about building disruptive products, leveraging the power of data science, and exponential teamwork, check out my YouTube videos at: https://bit.ly/ChupSpeaks
IN THIS PRESENTATION:
In one video, I give you everything you need to understand the basics of Agile and get started in the new Jira interface! I'll show you basic Jira planning and working with Scrum and Kanban. We also talk about story points and about some of the most common customizations. With these basics, you'll get Jira to match the way your team works, so you and your team can focus on building great products.
Learn the basics of the agile way-of-life that has helped many companies realize their potential in the market. The agile secret sauce was once a thing that was only enjoyed by software organizations on the East and West coasts, but is now invading Indianapolis -- increasing productivity, making teams empowered (and happier!), and helping managers focus less on the taskmaster role and more on the important stuff.
One of the many reasons why the web browser Mozilla Firefox has become so popular is its ability to use add-ons (or extensions), small programs that allow you to personalize your internet surfing experience. They can do everything from blocking advertisements to giving you weather reports to making your email simpler to use. This walkthrough will tell you what add-ons are, how you can find and install them, and will detail a few that we particularly like: Adblock Plus, ForecastFox, Flashblock, and ReminderFox. While this walkthrough assumes you're using Microsoft Windows, the principles also apply if you're using Firefox on a computer running Linux or the Macintosh operating system.
This class was last presented at the Bay Area Seniors Computer Club in March 2010.
A presentation by full-stack agile on some of the myths regarding the Agile framework. There are important questions such as benefits, documentation, scalability, architecture, planning and discipline.
Agile methodology is a framework for modern software development.
What is the philosophy behind Agile?
How does it differ from traditional project management strategies like waterfall?
What are the stages, meetings, tools, and team roles?
What is Scrum?
[To download this complete presentation, visit: https://www.oeconsulting.com.sg/training-presentations]
This introduction to Agile and Scrum is a presentation that provides a high-level overview of Agile and Scrum methodologies. The presentation is aimed at individuals who may have heard of Agile and Scrum but are not familiar with the concepts or principles.
The presentation begins with an introduction of the basic principles and values of Agile and Scrum, which includes an explanation of the Agile philosophy and principles, and an overview of the Scrum framework and its origins. It also discusses the benefits and drawbacks of Agile and Scrum and compares them to traditional project management methodologies.
The key roles and responsibilities within a Scrum team are discussed next, including the three key roles of Scrum Master, Product Owner, and Development Team. An explanation on how these roles interact with each other and the wider organization is provided.
The Scrum framework and its key components, including an overview of Sprints, Backlog, and Artifacts are also explained. The Scrum events, including Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective, are also covered.
Lastly, successful examples of how Agile and Scrum are used in various industries, such as software development, marketing, and education are presented. Discussions on how Agile and Scrum can be adapted to fit the needs of different projects and organizations are also provided.
By the end of the Agile and Scrum PPT presentation, attendees would have a solid foundation in Agile and Scrum methodologies, including a basic understanding of the principles and values, the Scrum framework and its key components, and the roles and responsibilities of the Scrum team. They would be equipped with the necessary knowledge to apply Agile and Scrum to their own work.
LEARNING OBJECTIVES
1. Understand the basic principles, values, benefits and drawbacks of Agile and Scrum.
2. Understand the key roles of the Scrum team, and the Scrum framework and its key components.
3. Understand how Agile and Scrum can be applied to various industries and projects and adapted to fit different situations.
Kanban Boards to visualize work
Kanban Systems to create a pull system of work limiting work in progress
Evolutionary Change based on Improved Decision-Making through Leadership & Self-Organization
Focus on Customer Needs recognizing work as a Flow of Value
Feedback loops and Metrics for Continuous Improvement
Agile Testing: A pragmatic overview and new entry in Intelliware’s Agile Methodology Series.
What you’ll learn in this presentation:
Intelliware’s Chief Technologist, BC Holmes, provides a pragmatic overview of Agile testing. Complete with many examples, this presentation is ideal for those looking for a practical take on software testing in an Agile environment.
The presentation covers:
- Why do we use Agile testing?
- What Agile testing isn’t
- What Agile testing is: unit testing and test-driven development (TDD)
- High-level properties of good tests
- Testing in different languages
- Test suites and code coverage
- Using mock objects to help isolate units
- Beyond unit testing
- Understand the principles behind the agile approach to software development
- Differentiate between the testing role in agile projects compared with the role of testers in non-agile projects
- Positively contribute as an agile team member focused on testing
- Appreciate the challenges and difficulties associated with the non-testing activities performed in an agile team
- Demonstrate a range of soft skills required by agile team members
Scaling Scrum using Lean/Kanban in AmdocsYuval Yeret
Learn how Amdocs and Agilesparks took an enterprise Scrum implementation to the next step with Lean/Kanban - Presented in the Lean Software and Systems Conference 2010 in Atlanta
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
XBOSoft runs through the Top 10 Agile Metrics revealing the most fundamental data points Agile methodology requires to work effectively, and will put you on the highly targeted path to successful implementation of your Agile processes.
XBOSoft and Go2Group run through the top data points you should be measuring in your Agile Workflow. We’ll show you what to track, when and how often, and most importantly – why. Many believe that metrics are useless, but unless you measure, how can you systematically improve or know how you are doing? And with velocity as an overarching objective in agile, you should be tracking other things so that you know what else you could be impacting by going faster. But, with all the metrics so readily available to us today, how do we filter through to the most meaningful?
A New Introduction to Jira & Agile Product ManagementDan Chuparkoff
These are the corresponding slides from another one of my talks in the series for Great Product Teams: https://www.youtube.com/watch?v=TsG3OWTDAFY
FOR MORE:
If your team wants to learn more about building disruptive products, leveraging the power of data science, and exponential teamwork, check out my YouTube videos at: https://bit.ly/ChupSpeaks
IN THIS PRESENTATION:
In one video, I give you everything you need to understand the basics of Agile and get started in the new Jira interface! I'll show you basic Jira planning and working with Scrum and Kanban. We also talk about story points and about some of the most common customizations. With these basics, you'll get Jira to match the way your team works, so you and your team can focus on building great products.
Learn the basics of the agile way-of-life that has helped many companies realize their potential in the market. The agile secret sauce was once a thing that was only enjoyed by software organizations on the East and West coasts, but is now invading Indianapolis -- increasing productivity, making teams empowered (and happier!), and helping managers focus less on the taskmaster role and more on the important stuff.
One of the many reasons why the web browser Mozilla Firefox has become so popular is its ability to use add-ons (or extensions), small programs that allow you to personalize your internet surfing experience. They can do everything from blocking advertisements to giving you weather reports to making your email simpler to use. This walkthrough will tell you what add-ons are, how you can find and install them, and will detail a few that we particularly like: Adblock Plus, ForecastFox, Flashblock, and ReminderFox. While this walkthrough assumes you're using Microsoft Windows, the principles also apply if you're using Firefox on a computer running Linux or the Macintosh operating system.
This class was last presented at the Bay Area Seniors Computer Club in March 2010.
A presentation by full-stack agile on some of the myths regarding the Agile framework. There are important questions such as benefits, documentation, scalability, architecture, planning and discipline.
A small presentation by Ashley-Christian Hardy on the basics of Scrum methodology, covering the basics of roles & responsibilities, events & ceremonies and scrum artefacts.
Talk by Joakim Sundén and Anders Ivarsson about agile and scaling agile at Spotify. These particular slides are from a Kanban Open Space event in Ghent, Belgium, February 2013.
Presentation from full-stack agile on how you can scale your agile teams as your company grows. As your company grows your teams need to be able to adapt to change quickly.
Suggestions:
1) For best quality, download the PDF before viewing.
2) Open at least two windows: One for the Youtube video, one for the screencast (link below), and optionally one for the slides themselves.
3) The Youtube video is shown on the first page of the slide deck, for slides, just skip to page 2.
Screencast: http://youtu.be/VoL7JKJmr2I
Video recording: http://youtu.be/CJRvb8zxRdE (Thanks to Al Friedrich!)
In this talk, we take Deep Learning to task with real world data puzzles to solve.
Data:
- Higgs binary classification dataset (10M rows, 29 cols)
- MNIST 10-class dataset
- Weather categorical dataset
- eBay text classification dataset (8500 cols, 500k rows, 467 classes)
- ECG heartbeat anomaly detection
- Powered by the open source machine learning software H2O.ai. Contributors welcome at: https://github.com/h2oai
- To view videos on H2O open source machine learning software, go to: https://www.youtube.com/user/0xdata
WordCamp Nashville 2016: The promise and peril of Agile and Lean practicesmtoppa
Why you may to consider adopting Agile or Lean practices, how they differ from each other, what benefits you can expect, and what obstacles you may face
Boston Ruby Meetup: The promise and peril of Agile and Lean practicesmtoppa
Why you may to consider adopting Agile or Lean practices, how they differ from each other, what benefits you can expect, and what obstacles you may face
The promise and peril of Agile and Lean practicesmtoppa
Why you may to consider adopting Agile or Lean practices, how they differ from each other, what benefits you can expect, and what obstacles you may face.
Introduction to Agile & scrum, but a bit from an HR perspective.
This presentation was given at "JobInfo" as some background material for a better understanding of recruitment in an agile world.
Agile concepts for quality and process engineers for slideshareYuval Yeret
Excerpt from a session introducing agile concepts for a group of quality engineers in a big enterprise undergoing an agile transition.
The aim was to expose Quality/Process engineers to the concepts of agility and emphasize the impact on process/methodology development, the approach of evolution vs big design up front and its impact on their work. I used a lot of the classic agile examples (a lot of them by Henrik Kniberg) and adjusted for the development of methodology, to show that actually the agile approach should be discovered using an agile process.
Also covers some complexity thinking aspects.
And of course - this is not limited to methodology for IT/product development, but to many kinds of change management.
Similar to A real-life overview of Agile and Scrum (20)
RubyConf 2022 - From beginner to expert, and back againmtoppa
"In the beginner's mind there are many possibilities, in the expert's mind there are few."
- Shunryu Suzuki, from "Zen Mind, Beginner's Mind"
The Japanese Zen term shoshin translates as “beginner’s mind” and refers to a paradox: the more you know about a subject, the more likely you are to close your mind to further learning. In contrast, the beginner’s state of mind is judgment free. It’s open, curious, available, and present. We’ll draw on examples of these mindsets from fields as varied as aviation and geology, and discover lessons we can apply to the world of software development.
RailsConf 2022 - Upgrading Rails: The Dual Boot Waymtoppa
Upgrading Rails is easy, right? Sure, as long as you are upgrading your patch version. A Rails upgrade for a big application is not a trivial project: It took GitHub a year and a half to upgrade from Rails 3.2 to 5.2.
While upgrades have become easier with every new Rails version, your application has only become more complicated with every new dependency you added.
In this workshop you will learn a proven Rails upgrade process for major and minor version changes of Rails. You will leave this workshop with a roadmap to upgrade your Rails application.
Applying Omotenashi (Japanese customer service) to your workmtoppa
“There is customer service, and then there is Japanese customer service.” - Tadashi Yanai, CEO, Uniqlo
Americans visiting Japan are often dazzled by the quality of customer service they experience, but usually mistakenly perceive it as a well-executed form of customer service as they understand it from Western culture. The American notion of “the customer is always right,” does not apply in Japan, yet customer dissatisfaction is much less common. We’ll explore why this is, with some entertaining real-life examples, and discover lessons from it that we can apply to our work in the software industry.
I gave this as a lightning talk at Boston.rb on 7/14//2015. It's a discussion of the challenges of applying the Law of Demeter to Rails programming.
I gave an older, simpler version of this talk at Philly.rb on 1/15/2013. I've replaced those older slides.
A11Y? I18N? L10N? UTF8? WTF? Understanding the connections between: accessib...mtoppa
Web accessibility (A11Y) is about making the web usable for people with disabilities, and it also benefits others with changing abilities, such as older people. Internationalization (I18N) and localization (L10N) are about translating web sites into other languages. UTF8 is a Unicode character set, which is now the dominant one used on the web, and it’s designed to include characters from just about every written language. Each of these topics are typically discussed in isolation from each other, but in this talk – after a gentle introduction to each of them – we’ll explore their interconnections. We’ll also take a look at what WordPress provides for supporting them in your work creating sites, themes, or plugins.
We want code that is easy to understand, re-usable, and flexible. But we are always up against deadlines, so we rush, and end up with code that is messy, buggy, hard to maintain, and makes us go slower even though we’re trying to go faster.
What is clean code? In this talk I’ll provide some answers to this question, and introduce you to 10 good habits that will help keep your code clean, such as the use of meaningful names for your variables and functions, and following the “Boy Scout Rule” (leave the code cleaner than you found it). I will even try to persuade you that using a lot of code comments is a sign that there are problems with your code.
WordCamp Boston 2015: Agile Contracts for WordPress Consultantsmtoppa
Before going out on my own to start Poka Yoke Design this June, I worked at PromptWorks, where we signed over 30 Time & Materials (T&M) contracts with clients over the past 2 years, from local businesses to nationally known media companies. This is in contrast to traditional Fixed Scope, Fixed Cost (FS-FC) contracts.
Prospective clients typically have an initial preference for FS-FC contracts: they’re familiar, and at first glance, seem to guarantee the client will get what they want (by spelling out business requirements in detail), and place the business risk on the contractor. However, traditional contracts fail to recognize that web application development is more like an R&D project than a construction project. In the fast paced world of the web, business requirements can grow and change rapidly, technical challenges and opportunities can arise, and both parties benefit from being able to respond to these changes in a teamwork fashion, instead of spending time on lengthy contract re-negotiations.
In this talk we’ll explore what goes into a T&M contract, how to persuade a prospective client to sign one, and how to live up to the expectations you create in the persuasion process, to deliver a successful project.
WordCamp Nashville 2015: Agile Contracts for WordPress Consultantsmtoppa
When you develop a WordPress based project for a client in an Agile way, you deliver working features on a frequent basis, such as weekly, as you build out the project. This allows for review, feedback, and adapting to change. Evolving business requirements are welcome in an Agile process, instead of a source of frustration.
The problem is, even if clients think an Agile approach sounds good, they almost always have a preference for traditional Fixed Price, Fixed Scope contracts. These contracts, with detailed specifications, costs, and delivery dates, contradict the Agile approach, but they provide clients them with a sense of security and confidence that they will get what they want.
How do you convince them a traditional contract is actually riskier than they think, and persuade them to instead sign a contract that facilities Agile development? This is the most significant challenge facing consultants who want to follow Agile practices. At PromptWorks we use Time & Materials contracts with our clients, and we have signed over 30 of them in the past 2 years. In this talk we’ll discuss:
* What different types of contracts imply about the nature of the relationship with your client, and what it means for it to be a professional relationship of equals. Risk and reward should be shared, and the relationship should feel like a partnership.
* The persuasion and negotiation process for getting your prospective clients to sign a Time & Materials contract. We’ll discuss real-life situations from our experience at PromptWorks.
* PromptWorks’ typical project proposal, Master Service Agreement, and Scope of Work documents. We’ll highlight key aspects of our approach, and things to look out for if you have to use contract documents provided by your client.
WordCamp Nashville: Clean Code for WordPressmtoppa
Slides from my talk at WordCamp Nashville, including notes. Covers why clean code is important, and provides 10 tips to make your code cleaner, for WordPress and beyond
An overview of Agile and Scrum practices, and a comparison of 2 different, real-life Agile adoption experiences in a University setting. Presented at the Wharton Web Conference, July 2011
Object Oriented Programming for WordPress Plugin Developmentmtoppa
An introduction to object oriented programming in PHP. This is applicable to WordPress and other CMS/frameworks as well. Note the last half of the slideshow contains the notes for the slides shown in the first half.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
"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.
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.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
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.
2. www.toppa.com
@mtoppa
Mike Toppa
web engineer
610-322-7034
mike@toppa.com
www.toppa.com
Ruby, Rails, PHP, Wordpress, JS, HTML, CSS
SQL, NoSQL, AWS, TDD, Scrum, Kanban
20 years of experience in web development, project management, and functional management. I’ve worked in a variety of environments: dot coms,
universities, start-ups, consultancies. One thing I’ve learned is that organizations are like families - they’re all dysfunctional - it’s just a question of how
badly
3. Overview
✤ Tell me your problems…
✤ How traditional software development workflows can go wrong
✤ Tell me what you want…
✤ What makes software development enjoyable and rewarding?
✤ How do we get there?
✤ Agile principles
✤ The Scrum approach
✤ Additional best practices
✤ Scrum adoption anti-patterns and common difficulties
5. Features
Cost Schedule
1.The iron triangle
Client can
pick two
Quality
I’ve explained the triangle to dozens of clients over the years.
Programming is not magic. If the client tries to squeeze all 3 sides of the triangle, quality suffers.
6. Misalignment of authority and
responsibility
Cartoon by Mike Lynch
Used with permission
- Following this advise lets you cover yourself politically, and is a great way to make everyone who works for you miserable
- I've found that misalignment of authority and responsibility can explain a lot of dysfunction that happens in organizations
- When you have responsibility for your work but not enough authority over it, you will feel like a cog in machine
7. “If you go to the store with a huge shopping list and twenty
dollars, you need the authority to go to the money machine
for more cash, or the authority to make changes to the list.”
Ron Jeffries, Making the Date
What’s happening is that the client is trying to retain authority on the project while giving you the responsibility. But ultimately, for the project to be successful and for both
you and the client to be happy, responsibility and authority need to be brought into alignment.
8. 2. Multiple projects and multitasking
Source
Context switching between two projects eats about 20% of a full-time worker’s schedule. The sense of progress with multitasking is an illusion, compared
to not multitasking
13. Too much work
SWAG chart
9 developers, 2 product owners, and me supporting
- 22 clients with 124 applications
3 designers and 1 product owner supporting
- about 200 static content web sites
Taking inventory itself was a huge undertaking
14. Source
To have any chance of success in the long run, you have to claim authority you may not have had previously. You may have to fight for it…
15. Source
…but you have to always be professional. Think of how doctors behave in an ER. When the pressure is on is when you want them to be at their most
professional.
19. Traditional “Waterfall”Approach
Source
Features determine the cost and schedule
Define all requirements up front
Logically break down the work
Estimate the effort / durations
Plan out all the work
And only then begin the development…while trying to limit any change that will threaten the plan.
20. “I find your lack of faith disturbing”
5. No opportunity for feedback
Source
In combination with the cone of uncertainty, this is deadly
21. Result: we build the wrong features
Source
Ask customers what they want at the beginning, when they really don’t know
Penalize them for adding things later
TCL example
22. “The main thing that pushed Agile and Scrum was
that the success rate on traditional projects was
terrible; it was 45%. If that was a car-manufacturing
place, that would mean you’d throw out every other
car you built.”
Ken Schwaber, co-creator of Scrum, 6/21/2011
Overall result: low success rate
Source
23. Tell me what you want…
For yourself, and for your customers
24. What makes a job enjoyable?
✤ Autonomy
✤ Reward for effort
✤ Challenging/complex work
“Work that fulfills these three criteria is meaningful.”
– Malcolm Gladwell, “Outliers: The Story of Success”
25. “Novices believe that quality and velocity are inverse.
They think that hacking is fast.
They haven’t yet recognized what
professional developers know all to well:
…the higher the quality, the faster you go”
Bob Martin, Vehement Mediocrity
30. image source
* In 2001, a group of 17 very experienced software developers got together and came up with the Agile Manifesto. They had spent their careers experiencing all the
difficulties of the traditional approach, and were motivated to come up with something better
32. Scrum is the most popular Agile
methodology
The original ideas for Scrum came from an article published in Japan in the mid 1980s, which reviewed case studies of early implementations of the ideas
in Japanese manufacturing work. In the 1990s Ken Schwaber and Jeff Sutherland gradually formalized Scrum into a set of specific practices for software
development.
33. Agile solution: flip the triangle
Source
Agile takes into account the “cone of uncertainty” - things will change
34. Agile: frequent feedback is key
Source
Rather than fight the “cone of uncertainty” we embrace it. We are always checking in to make sure what we’re delivering is what the client wants, and we’re
ready to adjust priorities based on feedback. At some point we will run out of time or money, and when that time comes, we want to make sure we have
delivered the most important features.
36. Source
Develop systems in small portions at a time (incremental), through repeated cycles (iterative), and take advantage of what was learned in each cycle (for
both features and implementation)
37. Incremental development:
slice vertically, not horizontally
Source
This is where developers unfamiliar with Agile freak out
How do you develop a UI or a database in pieces? This seems like it would lead to a giant mess. Remember the iterative part - we can sketch out the overall
design, but we build incrementally, fleshing out the details of what’s needed soon
It is possible, it is practical, and there are a lot of people doing it.
It's actually the opposite of messy hacking. Doing it well requires a very disciplined development process, and strong application design skills, as you are
trying to maintain a solid application design while always being ready to adapt to change.
38. The Agile workflow
✤ Deliver business value incrementally
✤ Deliver in order of business priority
✤
Deliver in small, frequent batches
✤ Solicit and respond to business feedback at each delivery
✤ Measure what is left to do
✤ Make decisions based on track record
✤ Stop when it makes sense
Source
39. Why?
✤ The pace of business keeps getting faster
✤ Feedback is essential
✤ Time is scarce
✤
Things will change
40. Agile:“inspect and adapt”
Source
Single loop learning is “how can we do better”?
Double loop learning is “Why do we believe that?”
Double loop learning means challenging fundamental assumptions
42. Scrum: overview
✤ Scrum consists of these core elements:
✤ 3 roles
✤ 3 artifacts
✤ 5 events
✤
That’s it!
✤ But there are also several recommended best practices
The scrum book we’ve been reading presents doesn’t really distinguish the core elements from the recommended best practices.
43. Scrum has 3 roles
Highly collaborative approach - minimize handoffs and maximize advantages of bringing together people with different perspectives and backgrounds
44. Scrum role: Product Owner
Responsible for what the team will work on,
and setting priorities,
but not how the work is done
* Responsible for what the team will work on, but not how the work is done
* Works closely with clients to understand their needs
* Gathers and writes business requirements in small pieces, called “user stories”
* Based on client needs, sets priorities for the team
* Does not have authority over technical design decisions
* Cannot tell an individual team member what to do
* A good Product Owner is: available, business-savvy, communicative, decisive, empowered
45. Scrum role: Scrum Master
A “servant-leader” for the team
* A “servant-leader” for the team - analogous to a physical trainer
* Can coach and evangelize, but not issue commands
* But does have authority over the Scrum process
* Removes obstacles for the team
* A good Scrum Master is: responsible, humble, collaborative, committed, influential, and knowledgeable
46. The team: self-organizing
and cross-functional
Source
* Cross-functional team takes collective responsibility for estimating the work, and doing the work
* Doing it in the priority order they are asked to follow
* Keeping quality high by working together (inspecting each other's code, discussing best technical solutions, etc)
47. So who’s
the boss?
Source
Personnel management exists completely outside this structure.
Works best in relatively “flat” organizations where people are given autonomy and achievable goals
Antithetical to top-down, command and control hierarchies
49. Artifact #1: the product backlog
Source
* The product backlog is the prioritized list of features, usually written in the form of user stories.
* It is a living document, subject to re-prioritization between sprints.
* The product owner manages it
50. Event #1: the sprint (aka increment)
Source
* A regular, repeating work cycle
* Sprints should have a consistent length, no longer than 1 month
* Good to start with 2 weeks, and then adjust if needed
* Purpose:
* Establishing a regular cadence: a sprint should never be extended
* Get away from slow periods at the start of a project and death marches at the end
* Delivering working software at the end of each sprint becomes routine
* As you get better at scrum, you’ll want to move to shorter sprints, but usually no shorter than 1 week
51. Artifact #2: the sprint backlog &
Event #2: sprint planning
Source
* In the sprint planning meeting, the team reviews the highest priority stories from the product backlog and breaks them down into tasks.
* They estimate how many of the stories will fit into the sprint.
* Key point: the team decides how much can fit in the sprint, not the Product Owner. The team has authority over what they are responsible for.
* Ideally there can be a “sprint goal” where the set of stories come together as a feature set, but this isn’t always possible.
52. Artifact #3: the “product increment”
Source
To complete a campground project, we can deliver these
features, one at a time
etc…
* To deliver a holiday park, we can deliver these complete features, one at a time:
* Campsite for tents
* Reception area, for check-in and check-out
* Toilets and showers
* Hook ups for RVs
* Laundry facilities
* A shop
* Etc…
53. Event #3: the daily standup
(aka daily scrum)
Source
* You literally stand
* Timeboxed to 15 minutes
* The goal is to answer the 3 questions: "What did you do yesterday?", "What will you do today?", and "Are there any impediments preventing you from
completing your work?
* This meeting is by and for the team, to speak candidly about the status of the work
* The goal is to make sure everyone knows what’s going on, and to deal with any impediments quickly
* Management is ideally not there. If they need to be there, they do not speak and definitely do not run the meeting. They should stand behind the team,
so it’s clear the attention is not on them
54. Remote standups at ElectNext
* Works for remote teams too
* And in small organizations with good working relationships, everyone can join, not just developers
55. Event #4:The sprint retrospective
Source
* Post-mortem meeting at the end of each sprint.
* “Inspect & Adapt” is the focus
* Length rule of thumb: 1 hour per week in the sprint (2 weeks = 2 hours)
* The team generally focuses on these questions:
* What went well, and can we learn from it?
* What didn’t go well, and what can we learn from it?
* In general, how can we do better?
* I’ve found it’s also good to review progress on goals from previous retrospectives
* Management is absolutely not present, unless there’s a special reason
56. Event #5:The sprint review
Source
* The product owner runs the sprint review
* Length rule of thumb: same as retrospective
* Demo the work of the sprint to all stakeholders: customers, CEO, etc
* Get feedback: inspect and adapt the software
61. Splitting big stories
✤ “A job seeker can post and manage her resume…”
✤ One way to split it is along CRUD lines:
✤ create a resume…
✤ delete a resume…
✤ etc.
✤ Another way is data boundaries:
✤ add and edit education information…
✤ add and edit job history…
✤ etc.
62. Good stories: INVEST
✤ Independent
✤ Negotiable
✤ Valuable to customers
✤ Estimatable
✤
Small
✤ Testable
63. Estimating: story points
Source
* People are bad at estimating time, but we're good at estimating relative size or difficulty
* As the points go up, the range of uncertainty also goes up
64. Estimating: planning poker
Photo by Kelly Hirano
Used with permission
* The teams give “story points” to the work by playing planning poker
* After the PO describes the story and answers any questions from the team, each team member shows their card at once. This prevents them influencing
each other.
* Team based estimates are more accurate than estimates by individuals
65. Velocity enables scheduling and
“sustainable pace”
Source
* After a few sprints, teams have velocities, which allows for making time estimates for projects.
* And this is key to the Agile goal of “sustainable pace”
66. Many more I don’t have time to
describe….
✤ Handling non-functional
requirements
✤ Handling back-end system
stories
✤
Release planning
✤ Burn down charts
✤ Impact mapping
✤ Specification by example
✤ Pair programming
✤
Automated unit testing and
feature testing
✤ Continuous integration
✤ “Walking skeletons”
✤
Etc
72. A Scrum coach can help
Source
* A skilled external coach is often key for driving change - they bring a wide range of experience and can see things objectively
* If you’ve never led an Agile transition before, it’s surprisingly easy to do it wrong
* At Penn, I misunderstood the roles: the clients were acting as their own product owners, The scrum masters were our former project managers, and
continued doing traditional project management
* You need at least enough management support to pay the coach
* You need to make sure you’re bringing in someone good
74. The Scrum Promise
“In my Scrum classes I warn attendees of what I
call the Scrum Promise: If you adopt Scrum, there
will be a day you come into the office nearly in
tears over how hard the change can be. This is
because Scrum doesn’t solve problems, it
uncovers them and puts them in our face. Then,
through hard work we address them.”
– Mike Cohn, Agile Trainer
A common reaction when this happens is to blame Scrum rather than actually deal with the issues.
78. Reality…
Source
Team didn’t like it, and clients didn’t like it. It felt like just adding a new set of work and processes on top of the existing work
79. Handling “emergencies”
✤ Triage… and reject if not really a software issue
✤ Triage… and defer if important but not truly an emergency
✤ Reserve a buffer in the sprint for unplanned work… but beware!
✤
Deal with root causes… prevent ongoing emergencies
Source
81. Additional references
✤ “Succeeding with Agile: Software Development Using Scrum” and
“Agile Estimating and Planning” by Mike Cohn
✤ “Specification by Example” and “Impact Mapping” by Gojko
Adzic
✤ “Agile Retrospectives: Making Good Teams Great” by Esther
Derby
✤ Angry Dinosaurs: Accelerating Change and Institutional
Incompetence presentation by Cory Ondrejka, Wharton Web
Conference, 2010
✤ “The Nature of Software Development” by Ron Jeffries
82. References: technical practices
✤
“Clean Code” and “Agile Software Development, Principles,
Patterns, and Practices” by Bob Martin
✤ “Refactoring: Improving the Design of Existing Code” by Martin
Fowler
✤ “Agile Database Techniques” by Scott Ambler
✤ “Working Effectively with Legacy Code” by Michael Feathers