Love tracing bugs in a defect tracking system? Love the bug-fix cycle? If so, then don't come to this presentation. We'll be discussing how Specification by Example (also known as Acceptance Test Driven Development) will help move you towards a zero defect system by building the right thing the first time.
EuroSTAR Software Testing Conference 2010 presentation on Testing "slow flows" Fast, Automated End-2-End Testing using interrupts by Dominic Maes. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Niels Malotaux - Help We Have a QA Problem!TEST Huddle
EuroSTAR Software Testing Conference 2009 presentation on Help We Have a QA Problem! by Niels Malotaux. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
EuroSTAR Software Testing Conference 2010 presentation on Testing "slow flows" Fast, Automated End-2-End Testing using interrupts by Dominic Maes. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Niels Malotaux - Help We Have a QA Problem!TEST Huddle
EuroSTAR Software Testing Conference 2009 presentation on Help We Have a QA Problem! by Niels Malotaux. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses the current date and time? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away Agile testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.
You want to integrate skilled testing and development work. But how do you accomplish this without developers accidentally subverting the testing process or testers becoming an obstruction? Efficient, deep testing requires “critical distance” from the development process, commitment and planning to build a testable product, dedication to uncovering the truth, responsiveness among team members, and often a skill set that developers alone—or testers alone—do not ordinarily possess. James Bach presents a model—a redesign of the famous Agile Testing Quadrants that distinguished between business vs. technical facing tests and supporting vs. critiquing―that frames these dynamics and helps teams think through the nature of development and testing roles and how they might blend, conflict, or support each other on an Agile project. James includes a brief discussion of the original Agile Testing Quadrants model, which the presenters believe has created much confusion about the role of testing in Agile.
Growing a Company Test Community: Roles and Paths for TestersTEST Huddle
Over the past three years, our company’s test team has grown from three lonesome testers to a community of nine – with more planned. Since we don’t see testers as “click monkeys”, but as valuable and integrated project members who bring a specific skill set to the table, it’s important for us to choose testers well and to train them in various areas so that they can contribute, grow and see their own career path within testing.
To structure to our internal tester training program, we have been developing role descriptions, education paths and career options for our testers, which I’d like to share with you in this webinar.
View webinar - https://huddle.eurostarsoftwaretesting.com/resource/webinar/growing-company-test-community-roles-paths-testers/
Some notions of continuous testing (CT) have been applied in software development methodologies for a while but it was never called by that term. Another term sometimes used for CT is parallel testing. While some have mastered CT, most of us struggle with how to transform our current testing approaches to CT approaches and align them with evolving development methodologies. Join Tom Wissink as he discusses current examples of CT implementations across different software development methodologies (agile, waterfall, incremental) and describes where parallel or CT type testing yields the best benefits. Arguably the most challenging methodology that demands CT testing is DevOps. DevOps requires all phases of testing to be done quickly and in parallel with the development process and some contend that testing continues into actual operations. Leave this session with a better understanding of CT, and how this approach can be best leveraged in your development environment.
'How To Apply Lean Test Management' by Bob van de BurgtTEST Huddle
Cost reductions and the quest for more efficiency are more evident in today’s business world. It also follows that our testing processes will ultimately be affected. When test techniques and methods for structured testing are introduced, this results in improvements in the production of more consistent and predictable results.
Introducing a risk based approach to testing makes it easier for the business to determine to what extent testing is necessary and most efficient. The resulting Go/No- Go decision process may not be sufficient for all companies so other creative methods need to be investigated. Many management theories speak about “Lean” as being one of the solutions. One of the key steps in using “Lean” is the identification of which steps add value to the customer and which do not. This track will give you information to start using “Lean” within testing and more specifically within test management.
The presenter will also look at Lean Six Sigma as being one of the more popular theories that introduces the concept of “Lean” in combination with obtaining higher quality products. This subject will also be explained in combination with testing and test management. This track will focus on applying Lean Six Sigma techniques to test management processes using practical examples from customer cases. The audience can take home a practical “Lean Test Management” overview which they can apply in their own companies.
This track is especially of interest to business managers, IT managers, QA managers and test managers that are involved in improving the quality of test management processes.
Klaus Olsen - Agile Test Management Using ScrumTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Agile Test Management Using Scrum by Klaus Olsen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Christian Bk Hansen - Agile on Huge Banking Mainframe Legacy Systems - EuroST...TEST Huddle
EuroSTAR Software Testing Conference 2011 presentation on Agile on Huge Banking Mainframe Legacy Systems by Christian Bk Hansen. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
'An Evolution Into Specification By Example' by Adam KnightTEST Huddle
For the last four years myself and my colleagues at RainStor have been evolving a process for testing a structure data archiving system in an Agile development environment. In this talk I will discuss the evolution of a team from a rudimentary Agile implementation on an unreleased product, to our current process which uses the fundamental elements of Specification By Example to successfully deliver software functionality across 30 different platform/backend configurations to a series of high profile and demanding customers. Last year our company was used as a case study for successful implementation in Gojko Adzic's book on Specification By Example.
My report will discuss the lessons learned during the early implementation and the challenges faced in moving away from a compressed waterfall approach. Through a process of incremental change we have identified and tackled the fundamental issues that undermined the development effort as a team. I’ll describe some of the mistakes made in attempting to implement a more formal process of requirements documentation into an Agile implementation and the benefits we uncovered on moving to a more flexible user story based approach. I’ll also discuss some of the issues around trying to implement user stories in a server system with no GUI and very technical and performance based requirements.
Raising the importance of quality and the status of testing both within the development team and the organisation as a whole has allowed the challenges facing the team to be recognised and respected. The result has been a more collaborative approach taken between developers and testers both through “collaborative specification” of user stories and tackling the problems that impact the delivery of value to the customers. I also plan to discuss how we’ve expanded from documenting acceptance criteria for each user story such that we now document Criteria, Assumptions and Risks for each feature and, rather than a ‘Done/Not Done’ approach how we identify the confidence in each of these categories to measure the confidence we have in each new feature being implemented.
Having the test team as an involved and influential team through the entire development process has also allowed us to implement a number of testability features to help to make the product more testable. I will discuss the benefits of having development understand and prioritise testability issues with some illustrative examples.
I will discuss the challenges and benefits of developing our own metadata driven test harnesses as opposed to an off the shelf solution. I’ll detail how having control over these harnesses has allowed us to work towards a self documenting test system using realistic customer examples as “Automated Specifications” of the RainStor system allowing us to explain current behaviour to Product Management in terms of well understood customer scenarios.
New Model Testing: A New Test Process and ToolTEST Huddle
In this webinar, Paul described his experiences of building and using a bot for paired testing and also propose a new test process suitable for both high integrity and agile environments. His bot – codenamed System Surveyor – builds a model of the system as you explore and captures test ideas, risks and questions and generates structured test documentation as a by-product.
Combinatorial Black-Box Testing with Classification TreesTechWell
A basic problem in software testing often is choosing a subset from the near infinite number of possible test cases. Consider the challenges of testing multiple browsers, multiple mobile devices, mobile applications, or use case paths. Testers must select test cases to design, create, and then execute to obtain sufficient coverage—all while managing the time it takes to test relative to risks. Even though test resources are limited, you still want to select the best possible set of tests. Peter Kruse shares his experiences designing test cases with TESTONA, the most popular tool for systematic test design of classification tree-based tests. Peter shows how to integrate expected test outcomes and how to obtain executable test scripts directly from the test specification or user stories. If you are looking to jumpstart your systematic test design and want to avoid unnecessary tests and overhead, this session is for you!
Dorothy Graham - Can The Past Tell Us The FutureTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Can The Past Tell Us The Future by Dorothy Graham. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
dbg Agile Testing Presentation, demonstrating the use of Test Charters, Exploratory Testing, Session Based Testing and Testing Tours. With thanks to James Bach, Lisa Crispin, Janet Gregory and James Whittaker
Test Improvement - Any place, anytime, any whereRuud Teunissen
Test Improvement is all about giving an organization or a team the “means they can use” to help achieve their goals. Means that are in line with their skills and they can use in their context. That’s why successful Test Improvement requires leadership and management. In this presentation I share experiences in Test Improvement in a wide variety of environments, using different models and approaches.
Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses the current date and time? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away Agile testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.
You want to integrate skilled testing and development work. But how do you accomplish this without developers accidentally subverting the testing process or testers becoming an obstruction? Efficient, deep testing requires “critical distance” from the development process, commitment and planning to build a testable product, dedication to uncovering the truth, responsiveness among team members, and often a skill set that developers alone—or testers alone—do not ordinarily possess. James Bach presents a model—a redesign of the famous Agile Testing Quadrants that distinguished between business vs. technical facing tests and supporting vs. critiquing―that frames these dynamics and helps teams think through the nature of development and testing roles and how they might blend, conflict, or support each other on an Agile project. James includes a brief discussion of the original Agile Testing Quadrants model, which the presenters believe has created much confusion about the role of testing in Agile.
Growing a Company Test Community: Roles and Paths for TestersTEST Huddle
Over the past three years, our company’s test team has grown from three lonesome testers to a community of nine – with more planned. Since we don’t see testers as “click monkeys”, but as valuable and integrated project members who bring a specific skill set to the table, it’s important for us to choose testers well and to train them in various areas so that they can contribute, grow and see their own career path within testing.
To structure to our internal tester training program, we have been developing role descriptions, education paths and career options for our testers, which I’d like to share with you in this webinar.
View webinar - https://huddle.eurostarsoftwaretesting.com/resource/webinar/growing-company-test-community-roles-paths-testers/
Some notions of continuous testing (CT) have been applied in software development methodologies for a while but it was never called by that term. Another term sometimes used for CT is parallel testing. While some have mastered CT, most of us struggle with how to transform our current testing approaches to CT approaches and align them with evolving development methodologies. Join Tom Wissink as he discusses current examples of CT implementations across different software development methodologies (agile, waterfall, incremental) and describes where parallel or CT type testing yields the best benefits. Arguably the most challenging methodology that demands CT testing is DevOps. DevOps requires all phases of testing to be done quickly and in parallel with the development process and some contend that testing continues into actual operations. Leave this session with a better understanding of CT, and how this approach can be best leveraged in your development environment.
'How To Apply Lean Test Management' by Bob van de BurgtTEST Huddle
Cost reductions and the quest for more efficiency are more evident in today’s business world. It also follows that our testing processes will ultimately be affected. When test techniques and methods for structured testing are introduced, this results in improvements in the production of more consistent and predictable results.
Introducing a risk based approach to testing makes it easier for the business to determine to what extent testing is necessary and most efficient. The resulting Go/No- Go decision process may not be sufficient for all companies so other creative methods need to be investigated. Many management theories speak about “Lean” as being one of the solutions. One of the key steps in using “Lean” is the identification of which steps add value to the customer and which do not. This track will give you information to start using “Lean” within testing and more specifically within test management.
The presenter will also look at Lean Six Sigma as being one of the more popular theories that introduces the concept of “Lean” in combination with obtaining higher quality products. This subject will also be explained in combination with testing and test management. This track will focus on applying Lean Six Sigma techniques to test management processes using practical examples from customer cases. The audience can take home a practical “Lean Test Management” overview which they can apply in their own companies.
This track is especially of interest to business managers, IT managers, QA managers and test managers that are involved in improving the quality of test management processes.
Klaus Olsen - Agile Test Management Using ScrumTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Agile Test Management Using Scrum by Klaus Olsen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Christian Bk Hansen - Agile on Huge Banking Mainframe Legacy Systems - EuroST...TEST Huddle
EuroSTAR Software Testing Conference 2011 presentation on Agile on Huge Banking Mainframe Legacy Systems by Christian Bk Hansen. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
'An Evolution Into Specification By Example' by Adam KnightTEST Huddle
For the last four years myself and my colleagues at RainStor have been evolving a process for testing a structure data archiving system in an Agile development environment. In this talk I will discuss the evolution of a team from a rudimentary Agile implementation on an unreleased product, to our current process which uses the fundamental elements of Specification By Example to successfully deliver software functionality across 30 different platform/backend configurations to a series of high profile and demanding customers. Last year our company was used as a case study for successful implementation in Gojko Adzic's book on Specification By Example.
My report will discuss the lessons learned during the early implementation and the challenges faced in moving away from a compressed waterfall approach. Through a process of incremental change we have identified and tackled the fundamental issues that undermined the development effort as a team. I’ll describe some of the mistakes made in attempting to implement a more formal process of requirements documentation into an Agile implementation and the benefits we uncovered on moving to a more flexible user story based approach. I’ll also discuss some of the issues around trying to implement user stories in a server system with no GUI and very technical and performance based requirements.
Raising the importance of quality and the status of testing both within the development team and the organisation as a whole has allowed the challenges facing the team to be recognised and respected. The result has been a more collaborative approach taken between developers and testers both through “collaborative specification” of user stories and tackling the problems that impact the delivery of value to the customers. I also plan to discuss how we’ve expanded from documenting acceptance criteria for each user story such that we now document Criteria, Assumptions and Risks for each feature and, rather than a ‘Done/Not Done’ approach how we identify the confidence in each of these categories to measure the confidence we have in each new feature being implemented.
Having the test team as an involved and influential team through the entire development process has also allowed us to implement a number of testability features to help to make the product more testable. I will discuss the benefits of having development understand and prioritise testability issues with some illustrative examples.
I will discuss the challenges and benefits of developing our own metadata driven test harnesses as opposed to an off the shelf solution. I’ll detail how having control over these harnesses has allowed us to work towards a self documenting test system using realistic customer examples as “Automated Specifications” of the RainStor system allowing us to explain current behaviour to Product Management in terms of well understood customer scenarios.
New Model Testing: A New Test Process and ToolTEST Huddle
In this webinar, Paul described his experiences of building and using a bot for paired testing and also propose a new test process suitable for both high integrity and agile environments. His bot – codenamed System Surveyor – builds a model of the system as you explore and captures test ideas, risks and questions and generates structured test documentation as a by-product.
Combinatorial Black-Box Testing with Classification TreesTechWell
A basic problem in software testing often is choosing a subset from the near infinite number of possible test cases. Consider the challenges of testing multiple browsers, multiple mobile devices, mobile applications, or use case paths. Testers must select test cases to design, create, and then execute to obtain sufficient coverage—all while managing the time it takes to test relative to risks. Even though test resources are limited, you still want to select the best possible set of tests. Peter Kruse shares his experiences designing test cases with TESTONA, the most popular tool for systematic test design of classification tree-based tests. Peter shows how to integrate expected test outcomes and how to obtain executable test scripts directly from the test specification or user stories. If you are looking to jumpstart your systematic test design and want to avoid unnecessary tests and overhead, this session is for you!
Dorothy Graham - Can The Past Tell Us The FutureTEST Huddle
EuroSTAR Software Testing Conference 2008 presentation on Can The Past Tell Us The Future by Dorothy Graham. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
dbg Agile Testing Presentation, demonstrating the use of Test Charters, Exploratory Testing, Session Based Testing and Testing Tours. With thanks to James Bach, Lisa Crispin, Janet Gregory and James Whittaker
Test Improvement - Any place, anytime, any whereRuud Teunissen
Test Improvement is all about giving an organization or a team the “means they can use” to help achieve their goals. Means that are in line with their skills and they can use in their context. That’s why successful Test Improvement requires leadership and management. In this presentation I share experiences in Test Improvement in a wide variety of environments, using different models and approaches.
James Whittaker - Pursuing Quality-You Won't Get There - EuroSTAR 2011TEST Huddle
EuroSTAR Software Testing Conference 2011 presentation on Pursuing Quality-You Won't Get There by James Whittaker. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Lean software engineering emphasizes continuous delivery of high quality applications. Ken Pugh explains the principles and practices that form the basis of lean software development―concentrating on developing a continuous flow by eliminating delays and loopbacks; delivering quickly by developing in small batches; emphasizing high quality which decreases delays due to defect repair; making policies, process and progress transparent; optimizing the whole rather than individual steps; and becoming more efficient by decreasing waste. Ken describes lean’s emphasis on cycle time, rather than resource utilization, and demonstrates the value stream map which helps you visualize the development cycle flow to identify bottlenecks. He explores the differences between push and pull flow, describes how lean thinking shows up in agile processes including Scrum and Extreme Programming, and discusses how lean can be applied to the entire workflow—not just the development portion. Ken concludes with a discussion of how you can begin your lean transformation.
Continuous Context Driven Test ImprovementTechWell
Classical test process improvement is often not today’s best solution. With virtualization, SOA, web, cloud, mobile, and integration with social media, the way we develop, test, and manage has drastically changed. Jeroen explores why Agile, context-driven testing, SCRUM, continuous integration/development and DevOps require a flexible and pragmatic context-driven approach to test improvement. Context-driven test improvement is organized on two levels. [1] The improvement architecture level starts by clarifying the goal, scope, and context. This results in the improvement approach, a mixture of fixed- and free-format models and methods. The analysis of the collected information provides improvement suggestions that help achieve the “new” approach. [2] The improvement implementation level starts with transforming and prioritizing the improvement suggestions into tasks in the improvement backlog and fitting them into business-as-usual projects. Continuous improvement requires a continuous process that includes checking improvement results against the objectives—and, of course, new insights.
Software Quality Assurance (QA) Testing Interview Questions & AnswersJanBask Training
Here are most frequently asked Quality Assurance (QA) Interview Questions and Answers: I would ask if interviewing a Quality Assurance engineer. The questions will emphasize more on the quality processes and the strategy, so please see that the question will not be asked for Testing.
Start with Quality - an Agile Tester's Case StudyNick Zdunić
A presentation given at MTUG 2016. The recording is available on the Code Genesys website as well http://www.codegenesys.com/start-with-quality/
Some inspiration from Henrik Knibergs presentation. Just so happens we didn't know of this until we had implemented it. It was so similar. We give credit to his material in the slide deck as well.
[Webinar] Test First, Fail Fast - Simplifying the Tester's Transition to DevOpsKMS Technology
DevOps is a spectacular mish-mash of development and operations processes and practices that has been growing increasingly popular in recent years. With the upward trending rate in adoption comes the need for organizations to fully understand the key practices as well as thoroughly integrating team members, especially testers, throughout the delivery pipeline. Getting started with DevOps practices can be a little tricky when choosing the right tools, people, and processes. In this webinar, we’ll focus on helping you make the switch without diminishing the team’s delivered product quality, so that the transition meets the enterprise objectives of speed and reliability.
Tune in to learn:
The biggest concern when moving to DevOps - and how to handle it
Why you need ‘Coding Testers’
The best tools for the job
The process of failing fast, and its significance to testers
Measuring the transition - recommended metrics
The value of DevOps long-term - efficiency, repeatability & reliability
Don’t worry about failing - it’s a part of the process!
Creating testing tools to support developmentChema del Barco
This is a presentation I made for the Kraków Java User Group on test automation and how to solve the challenges around it to make it really useful for development teams. It contains some examples of how we are doing it at Akamai's Web department, and some based on my own experience.
The DevOps Dance - Shift Left, Shift Right - Get It RightInflectra
As more organizations move towards continuous integration (CI) and continuous delivery (CD) with DevOps pipelines becoming the norm, where is the right place to do different kinds and levels of testing? In this presentation, I will provide a blueprint for test managers on how to think about shifting left and shifting right while keeping the overall QA picture and goals in mind.
Learn how to navigate organizational culture to change views toward Quality and Scrum
Testing as part of a Scrum team (Everyone owns quality!)
Ways to "write tests" without breaking the time-bank
Set yourself up for success, even without automation
(Automation is awesome, and you should use it if you have it, but it's not 100% required to succeed at Scrum.)
Despite the belief that a shared context and collaboration drives quality, too often, software testers and quality professionals struggle to find their place within today's integrated agile teams. This session is a practitioner’s view of testing and testing practices within an iterative/incremental development environment. We will begin with a discussion of some of the challenges of testing within an agile environment and delve into the guiding principles of Agile Testing and key enabling practices. Agile Testing necessitates a change in mindset, and it is as much, if not more, about behavior, as it is about skills and tooling, all of which will be explored.
Similar to Moving Towards Zero Defects with Specification by Example (20)
It’s the beginning of a new project and you’re ready to start building some software. But which stories should you start with and why? We’ll start the session by teaching you some strategies for identifying your first horizontal application slice. We’ll also cover how an MVP may or may not be relevant to your project (“My client doesn’t need a thermal detonator, they need a completed Death Star”). In the remainder of the session you’ll get a chance to practice identifying your first slice based on a sample user story map.
An executive once declared that "I don't see the point of project retrospectives, nothing ever changes." Honestly, she is right too much of the time. While retrospectives are a deceptively simple concept, they are often a waste of your team's time. On the other hand, they are also frequently lauded by experts as the "one weird tip" that can positively transform your team even if you ignore all the other agile practices.
In this session, I'll walk through effective and engaging retrospective techniques that will help your team improve on a consistent basis.
Since our first event in March of 2010 we have held over 40 sessions and brought people together to explore and develop how agile can help businesses in Winnipeg. After spreading all of that agile love and beauty, it begs the question: "Is it working?" So, to kick off the 2015/2016 Agile Winnipeg season, we'll conduct our first retrospective on agile in Winnipeg. We'll celebrate the areas of agile that are working well in Winnipeg, and also explore which areas we still struggle with.
In this session, Steve will lead us all through a group retrospective. You'll experience how a retrospective can be run with a larger group, and also receive some tips for making your own retrospectives more effective. At the end of the session, we'll have created a prioritized list of actions for improving agile in Winnipeg.
As an enthusiastic problem solver and solution designer you were thrilled to be asked to {design the UI | architect the system | design the kanban board | solve the bottleneck | plan the office mini-golf course | storm the castle}. You researched the problem, weighed the options, considered the alternatives, and put your best effort into the final deliverable. Your presentation to the team was flawless - not one PowerPoint slide with more than 5 words on it! But, while everyone knew that your solution was awesome, it was ultimately trashed, warped, abused, tortured, discarded, and ignored.
What happened? You fell victim to one of the classic blunders - the most famous of which is "never get involved in a land war in Asia" - but only slightly less well-known is this: "Your design sucks because it isn't mine."
At this point you must be wondering - "If we only had a wheelbarrow (i.e. Design Studio), that would be something." Join me for a workshop on using the Design Studio Approach to achieve effective collaborative design. Have fun storming the studio!
The agile manifesto says directly that "We are uncovering better ways of developing software by doing it and helping others do it." If this continual improvement is true, what new topics are currently being discussed and talked about at agile conferences? What are teams across the world struggling and experimenting with? What topics are the most heated? In this session, I'll give an overview of some of the new and hot agile topics.
Creating a backlog of user stories is pretty straight forward but it doesn't help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and plan the project, and how to visualize progress. The traditional backlog is simply too flat and often too long to help you see the bigger picture and make good decisions. User Story Mapping helps simplify all of these common project issues. By adding a third dimension to your backlog, your team will make better decisions about priorities, scope, and planning while improving your ability to visualize progress.
In this practical session I’ll cover the basics of user story mapping before walking you through case studies of how our teams are using this approach and the results we are achieving. I'll show you the before, during, and after pictures from several projects so that you can understand how our maps progress during the projects and how we use them to influence iterative development, promote good decision making, and visualize priorities, plans, scope and progress.
We’ve all sat through painful requirements, planning, and brainstorming sessions that provide little useful output, are painfully long, and where the outcome was already decided by the loudest few before the meeting even started. Learn how silence can increase collaboration *and* help your agile project be more productive. Silent brainstorming allows everyone to have a voice – the loud people can’t dominate the conversation, the quiet people are provided with a way to contribute, and cognitive fixation is reduced. We’ll discuss the science of brainstorming, walk through many agile practices that use silence, and then practice a few silent brainstorming techniques such as User Story Writing, Retrospectives, and UX Design Studio.
As presented at Mile High Agile 2012 in Denver.
Review and discuss the basic agile practices in the context of two games. The first game will illustrate why small batches are important and how they can help you address project risks sooner. The second game will illustrate how small batches can help give you better information about your project sooner and will demonstrate some of the basic agile practices at work like iterations, continuous flow, manage to done, velocity, retrospectives, etc.
Most of us find ourselves multitasking at some point and are possibly even proud of our multitasking skills. This presentation includes a game (link on last page) plus some discussion questions and ways to combat multitasking in your organization.
User stories are core to many agile methodologies but are often misunderstood by those new to agile. However, proper user stories are important for planning, scoping, delivering value, and change management. This hands-on event will be spent creating, evaluating, and hopefully improving our own user story skills. Bring post-its and sharpies.
The video for this presentation is available here: http://vimeo.com/33850718
User story mapping is a technique popularized by Jeff Patton that will cause you to revoke your membership in the Flat Backlog Society. A user story map allows you to see the big picture in your backlog; acts as a visual project plan; provides a technique for gathering scope and stories fast; supports better user story slicing, prioritization, and scoping; and helps you to build the right thing first. In this session you will find out what a user story map is and how to create one with your team immediately after the conference.
Using Value Stream Mapping to make the case for Acceptance Test Driven Develo...Steve Rogalsky
Acceptance Test Driven Development (ATDD) is a movement within agile to improve the quality of and success of our projects by changing how we capture our requirements and by changing how and when we test. Borrowing from the Lean toolbox, we’ll use Value Stream Mapping (VSM) to compare traditional test & fix cycles to ATDD used in an agile context. Participants will be given an introduction to ATDD and VSM and will participate in creating and analyzing two Value Stream Maps. Target audience includes all members of the team including Testers, PMs, Developers and Analysts. Caution: Participants are warned that using VSM to map out your partner’s wasted efforts in completing household chores will not cause the harmony you imagined it would. For more of the tragic details, attend the session.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
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.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
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.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
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/
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.
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
Leading Change strategies and insights for effective change management pdf 1.pdf
Moving Towards Zero Defects with Specification by Example
1. (Track Sponsor) Moving towards zero defects with Specification By Example Steve Rogalsky @srogalsky winnipegagilist.blogspot.com
2. Choose 2 of these topics to discuss: Talk about your approach to quality and the results of that approach. Talk about your approach to requirements and how you keep those requirements up to date. Talk about any previous experience with automated testing. Talk about your team’s current bug tracking process. Talk about zero defects – Is it possible? Is it responsible? Cost effective?
9. What is Specification By Example? Goal: To build the right thing the first time.
10. What is Specification By Example? Also known as / similar to: ATDD – Acceptance Test Driven Development BDD – Behaviour Driven Development
11. To do this we: 1. WRITE EXAMPLES (Acceptance Tests) (up front but not UP FRONT) instead of requirements Given muppet <Animal> When measuring <Craziness> Then return <10> Given muppet <Animal> When <Drumming> Then return <Phenomenal Skillz> Given muppet <Animal> When <talking> Then return <Grunt> SPECIFICATION BY EXAMPLE
12. To do this we: 2. TEST AS SOON AS POSSIBLE FIRST in collaboration with the developers and customers
15. AN EXAMPLE: Requirement: Bring home something small from Europe What I brought: What she wanted:
16. ANOTHER EXAMPLE User Story: As an employee I want to receive overtime pay For each week, hourly employees are paid: 2 times their wage for each hour worked on Sundays and holidays a standard wage per hour for the first 40 hours worked 1.5 times their wage for each hour after the first 40 hours
17. (40*$20) = $800.00 a standard wage per hour for the first 40 hours worked
18. (40*$20) + (5*$20*1.5) = $950.00 1.5 times their wage for each hour after the first 40 hours
19. 2 times their wage for each hour worked on Sundays and holidays (40*$20) + (8*$20*1.5) + (8*$20*2) = $1,360.00
20. 2 times their wage for each hour worked on Sundays and holidays (40*$20) + (8*$20*1.5) + (8*$20*2 ) = $1,360.00 *1.5
25. Where should we focus our automated testing? Later… Focus Here First UI Services TDD Classes/ Functions Credit: Testing Triangle first shown by Patrick Wilson-Welsh
26. What does it take to set this up? It is simpler than this… '''
27. Steps: Download FitNesse (free) Run FitNesse Add A Reference to your project Create a Fixture per set of examples Write the examples Press a button
28. How to do it? Tester Customer and Team Automate Examples Expand into Examples Choose Story High Level Tests Passes All tests = done Review Code / TDD Think about how Developer
31. Open the folded paper up and make two triangle folds for the ‘nose’ of the plane
32. Re-fold the plane in half and fold two wings (one on each side…)
33.
34. TO SUMMARIZE Specification By Example: Communicate! Write Executable Examples instead of requirements The Tooling is simple to use and free Zero Defects isn’t impossible – build it right the first time Trash your Defect Tracker
SETUPFitNesse example- Test that these work and are prepped and then close them down: - Run C:\\_Projects\\SampleProjects\\SpecByExample\\server.FitNesse.bat - Open http://localhost:8088 in FireFox - Confirm tests are still all passing. - In FitNesse, remove page SpeakerInformation- Open C# project C:\\_Projects\\SampleProjects\\SpecByExample\\PrairieDevCon\\PrairieDevCon.sln - In VS, open "CalculateWeeklyPay" - In VS, remove LookupSpeakerInformation.cs- Setup 2 tables at the front for the experiment- Open C:\\_Projects\\FitNesse\\ folderOpen script: C:\\Users\\srogalsky\\Dropbox\\Presentations\\PrDC11\\SpecificationByExample\\ScriptForDemo.docx2. ExperimentPut out paperSetup 2 tablesSetup dividersPut examples in the dividersOpen spreadsheet: C:\\Users\\srogalsky\\Dropbox\\Presentations\\PrDC11\\SpecificationByExample\\AirplaneMfgResults.xlsPut instructions on both side – for QA, for team
Table Talk: Learners form small collaborative groups and discuss what they already know about the topic and any questions they have that are related to the topic. (Training from the back of the room)Ask them to:Form groups of 3 to 5Assign a note takerChoose 2 topicsReport a one or two sentence summary of each topicWrite the results on big post-its
Table Talk: Learners form small collaborative groups and discuss what they already know about the topic and any questions they have that are related to the topic. (Training from the back of the room)Ask them to:Form groups of 3 to 5Assign a note takerChoose 2 topicsReport a one or two sentence summary of each topicWrite the results on big post-its
Table Talk: Learners form small collaborative groups and discuss what they already know about the topic and any questions they have that are related to the topic. (Training from the back of the room)Ask them to:Form groups of 3 to 5Assign a note takerChoose 2 topicsReport a one or two sentence summary of each topicWrite the results on big post-its
Introduce myself here first.Tell my story here of the first project using this. 6 defects in 12 person months of work. 3 mediums, 3 lows. Arguably no defects since the 6 found were not identified as tests.Points:Cost?Is there a cost to TDD?What is the cost of a defect? (have you seen that chart?)The later you find it, the more screwed you are.Defects that matter“Like” button vs FB securityBuild it right the first timeBuild each piece little by little. Perfect on top of perfect. Simple…Normalization of devianceBoiling the frogIf you are using iterations, you need to regression test each iterationHow can you afford not to do some automated examples? Do you want to regression test your whole app manually at the end of each iteration? After each story is completed?Click a buttonZero defects is going be to required on more and more projects.Google carSmart cars that self regulate speed in car pool lanes once you enter themLots of Health initiativesWe’re moving to be ‘more’ dependent on perfect apps, not lessThe difference between what you think you should do and what you actually do is the degree to which you suckCory Haines
HypothesisDefinitionsProof
The stuff that QA and the customer does before saying it is done.Functional TestingAcceptance TestingNot Unit TestingWe’re not talking about TDD (Test Driven Development) today. Although related, TDD applies more to design, flexible code and unit testing. We’re talking about testing at a higher level – customer, QA, etc.
Happy customersRemove frustrations
Happy customersRemove frustrations
Makes requirements less ambiguous – an example laterGWT example shown, but lots of ways to do this – start with your existing test case formats and see what works for you.If you can’t do the rest of ATDD, do this! A great place to start.
Catches misunderstandings early so they aren’t duplicated throughout other user storiesImproves communication between QA and developers and customers (whole team!)Reduces the time spent writing, reading, understanding, arguing items in a defect trackerWhen we test, we execute the examples together that we wrote earlier
This is a silly as a high school end of year exam that is worth 60%. If we fail, it is as much the teacher’s fault as ours.
To prove early that the system works as expected and eliminate the waste of reworkRequires and investment time up front required to write the tests – pay off is laterRegression testing effort disappears (click a button)
To prove early that the system works as expected and eliminate the waste of reworkRequires an investment of time up front to write the tests – pay off is laterRegression testing effort disappears (click a button)
example courtesy Allan Shalloway - The Role of Quality Assurance in Lean-Agile
An example using FitNesseWe run this test against the code and see it passes!
Now with some overtime
Now with overtime and holiday hours
Now with the corrected codeThis is the beginning of the “aha” moment
Putting it all together – this is what your executable requirements document now looks like.Complete traceabilityPush button testing and regression now existsCan replace all business logic in your requirements documentCan replace much of your bug tracking effortThis should be the ‘aha’ moment.
Show Quick example using C#, FitNesse, PrDC APIStart the fitnesse batch fileShow the added referenceShow the fixture code for “CalculateWeeklyPay”Open FitNesse (http://localhost:8088/)Show the markup language for “WeeklyPayWithOvertime”Add an example for 40 hours and 10/hour = 500Press the buttonFix the errorShow HistoryShow the suiteRun the suiteShow the defect we found and fixed in the example earlier.Comment: This was my own biggest hurdle – starting…
Janet Gregory’s slide modified. Talk about the process. Talk about not Up Front, but just in time – one story at a time.Follow this little roll play:Script:=========Choose story (create a new FitNesse page and put this in there): Create “SpeakerInformation” pageAs an attendee I want to know some information about a speaker so that I can make decisions on which sessions to attend2. High Level Tests (add to FitNesse page):a short bio* name and contact info* social media information3. Expand into examples:'''User Story: Speaker Information'''''As an attendee I want to know some information about a speaker so that I can make decisions on which sessions to attend''* a short bio* name and contact info* social media information'''Scenario: Show the contact information for a speaker'''!-&nbsp;&nbsp;&nbsp;&nbsp;-!Given a '''<Speaker Name>'''!-&nbsp;&nbsp;&nbsp;&nbsp;-!When I look up their information on the website!-&nbsp;&nbsp;&nbsp;&nbsp;-!Then it should return the '''<Email>'''!-&nbsp;&nbsp;&nbsp;&nbsp;-!And '''<Twitter Id>'''!-&nbsp;&nbsp;&nbsp;&nbsp;-!And '''<Blog>'''!-&nbsp;&nbsp;&nbsp;&nbsp;-!And '''<Company Name>'''!-&nbsp;&nbsp;&nbsp;&nbsp;-!And '''<Picture>''''''Examples:'''!|Lookup Speaker Information ||Speaker Name |Email? |Twitter Id?|Blog? |Company Name?|Picture? ||Steve Rogalsky|steve.rogalsky@protegra.com|@srogalsky |winnipegagilist.blogspot.com/|Protegra |steverogalsky.jpg|4. Review together5. Automate examplesusing System;using System.Collections.Generic;using System.Linq;using System.Text;namespace PrairieDevCon.FitnesseTests{ public class LookupSpeakerInformation : fit.ColumnFixture { public string SpeakerName; public string TwitterId; public string Blog; public string CompanyName; public string Picture; public string Email() {varspeakerInformation = PrairieDevCon.Services.SpeakerService.GetSpeakerByName(SpeakerName);TwitterId = speakerInformation.Twitter; Blog = speakerInformation.Blog;CompanyName = speakerInformation.Company; Picture = speakerInformation.Picture; return speakerInformation.Email; } }}6. Run the tests until done!
At this point we gather our volunteers and explain the experiment.Explain:First, the teams may not talk from this point forwardQAPreferably acted out by a non-QA person(ask who are the testers, and pick a non-tester)Will accept/reject the end productHas a little leeway in accepting – see the ‘test cases’ provided for you. As long as it is pretty close, you can accept it. I am your customer, so I can help you with that.If it isn’t right, please write up the defect on your paper using words or pictures and hand the defect log and the product back to the develop team to fixAsk the QA to person to write good defects – as a dev he/she will know how frustrating an unclear defect isManufacturing team = DevelopersThere will be a few steps to build the end productThese steps are similar to the steps that you create to build software – the classes, database tables, UI, layers, etc. QA won’t test the individual classes and steps, but they will perform functional or acceptance testing on the final productYou can pair program if you like, it is up to you to determine the best way to accomplish the task – but again, NO TALKINGTeam 1Will not use ATDD – they will test at the end and to simulate this they will not see the ‘test cases’ that QA ownsTeam 2Will use ATDD – they will create their test case at the beginning to simulate the effort of automating the tests up front and they will have access to the ‘test cases’ throughout developmentBoth teamsReminder – no talkingReminder – no fighting or blaming – everyone is doing the best they can with what they have been givenDon’t copy the other team’s product, the requirements are similar, but the test cases may not be the sameTry to be as successful as possible without cheatingIf you have a defect, don’t throw out the product and start fresh, but fix the defective productWe’ll be timing both teams and then examine the results through a value stream before we debrief with questions
Once the exercise is done:First: Fill out the spreadsheetSecond: Ask the observers to reportThird – ask questions:How did it go?How did you feel as you were developing (calm on one side, not on the other)What went well?What didn’t go well?Refer back to the original questions asked and their answers – how does this fit?Fourth: my observationsHow it related to agile: removing barriers; build the right thing the first time; fail fast not slow