Let's Sharpen Your Agile Ax, It's Story Splitting TimeExcella
This slide deck is from the recent presentation Brian Sjoberg gave at the DC Scrum User Group on August 25, 2016. It is about User Stories and how to split them.
Do you want to write great User Stories (a.k.a. small features that are part of a product) that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration and be potentially shippable to production? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Additionally we will learn techniques for splitting stories in this interactive workshop.
Here is a link the meetup - https://www.meetup.com/DC-Scrum/events/232765657/
How to slice user stories, using concepts like low/high fidelity solutions, iterative vs incremental delivery, and hunting for small bits of value rather than breaking down work in technical chunks.
Learn how to divide work using the "vertical slicing" strategy.
This is particularly useful for Scrum teams to split backlog items allowing iterative and incremental product delivery.
Let's Sharpen Your Agile Ax, It's Story Splitting TimeExcella
This slide deck is from the recent presentation Brian Sjoberg gave at the DC Scrum User Group on August 25, 2016. It is about User Stories and how to split them.
Do you want to write great User Stories (a.k.a. small features that are part of a product) that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration and be potentially shippable to production? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Additionally we will learn techniques for splitting stories in this interactive workshop.
Here is a link the meetup - https://www.meetup.com/DC-Scrum/events/232765657/
How to slice user stories, using concepts like low/high fidelity solutions, iterative vs incremental delivery, and hunting for small bits of value rather than breaking down work in technical chunks.
Learn how to divide work using the "vertical slicing" strategy.
This is particularly useful for Scrum teams to split backlog items allowing iterative and incremental product delivery.
Do you want to write great User Stories that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Additionally we will learn techniques for splitting stories in this interactive workshop.
Anyone Can Write User Stories. It's the (Shared) Understanding That's ImportantKent McDonald
“Who should write user stories?”
“How can I write better user stories?”
When should we write user stories?”
All questions frequently asked. And all questions entirely missing the point.
Just as the *holding* is the most important part of the rental car reservation, the *shared understanding* is the most important part of the user story.
Join Kent to learn how user stories help you build shared understanding of the right solution with your team. Along the way, learn some techniques to address common issues that stand in the way of getting everyone telling the same story.
Learning Objectives:
* Start with value, then identify stories
* One way to stop solutioning
* Dealing with dependencies (that may not be there) within your backlog
* Ways to split user stories into a more manageable size
* Mapping your way to acceptance criteria
Techniques for Effectively Slicing User Stories by Naresh JainNaresh Jain
In order to achieve my goals, as a buyer of your product, I want awesome feature. AT: make sure your users stories don't get in the way.
Users Stories, the tool teams use to break big ideas into small demonstrable deliverable, are easy to describe and challenging to write effectively. In this hands-on workshop you'll learn how to write great user stories and acceptance criteria, that everyone on the team understands. We'll learn various techniques to slice your stories using the tracer-bullet approach. We will discuss what elements should be included in the stories, what criteria you should keep in mind while slicing stories; why the size of your user story is important and how to make them smaller and efficient.
Agenda:
What do you do to Large Stories? Spike, Split, Stub & Timebox (SSST) technique.
Core Slicing Techniques:
1. System Slice
1.a. Static vs. Dynamic
1.b. Real-time vs. Batch Processing
1.c. Build vs. Buy
1.d. Automated vs. Manual Steps
1.e. Defer certain roles
2. Behavioural Slice
2.a. Adjusting Sophistication - MVF (Minimum Viable Feature) or Walking Skeleton
2.a.1. Acceptance Criteria
2.b. By-pass certain steps in the workflow
2.c. Focus on Happy Path First (edge cases later)
2.d. No options - 1 option - Many options
3. Incrementally improve ‘Ilities' (Usability, Scalability, Reliability, etc.)
3.a. Simpler UI (even consider using a standard UI)
3.b. Minmal Data
3.c. Improve Performance Iteratively
User stories writing - Codemotion 2013Stefano Leli
Stefano Leli (Freelance) - Fabio Armani (OpenWare)
Scrivere user stories dovrebbe essere facile...almeno in teoria. In realtà nella pratica ci troviamo troppo spesso a combattere con storie vaghe o troppo tecniche, storie che non possono essere testate o addirittura che non portano alcun valore. In questo workshop cercheremo assieme di comprendere la differenza tra requisiti funzionali e User Story, tra User Story e Use Case, mediante dei case study.
User Stories Writing - Codemotion 2013Fabio Armani
Stefano Leli (Freelance) - Fabio Armani (OpenWare)
Scrivere user stories dovrebbe essere facile...almeno in teoria. In realtà nella pratica ci troviamo troppo spesso a combattere con storie vaghe o troppo tecniche, storie che non possono essere testate o addirittura che non portano alcun valore. In questo workshop cercheremo assieme di comprendere la differenza tra requisiti funzionali e User Story, tra User Story e Use Case, mediante dei case study.
What are User Stories? How should we write them? How to write them well?
Effective User Stories allow your team to be effective (deliver want the User needs) and efficient (Deliver it quickly and importantly don't deliver unneeded features).
Workshop for slicing stories, that leads you through concepts of thinning features and a technique for getting to the right level of stories for your teams using a slicing grid.
Materials to support the presentation and run a simulation are available here:
https://www.dropbox.com/sh/t04oqed47esv8ut/AACReMMiK_zYcRTBpjHPf4eDa?dl=0
Writing Good User Stories (Hint: It's not about writing)one80
User stories are typically the foundation of the Product Backlog. However, the original purpose has been lost. This is from a presentation that was given to help remind everyone of what User Stories are, and what they aren't. The purpose of User Stories is to drive conversations, not to hand "requirements" from one group to the next.
Behaviour Driven Development (BDD) is an evolution of test-driven development that places explicit emphasis on language, communication and 'outside-in' development. Many people are familiar with the 'Given,When,Then' structure used in BDD specifications (or acceptance tests) but is that really where it ends? In this session Antony Marcano gives a short intro to BDD, explains 'outside-in' development. Using a metaphor from learning theory and HCI principles, he'll show you how to go beyond 'Given,When,Then' to a shared understanding of
your customer's needs.
Do you want to write great User Stories that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Additionally we will learn techniques for splitting stories in this interactive workshop.
Anyone Can Write User Stories. It's the (Shared) Understanding That's ImportantKent McDonald
“Who should write user stories?”
“How can I write better user stories?”
When should we write user stories?”
All questions frequently asked. And all questions entirely missing the point.
Just as the *holding* is the most important part of the rental car reservation, the *shared understanding* is the most important part of the user story.
Join Kent to learn how user stories help you build shared understanding of the right solution with your team. Along the way, learn some techniques to address common issues that stand in the way of getting everyone telling the same story.
Learning Objectives:
* Start with value, then identify stories
* One way to stop solutioning
* Dealing with dependencies (that may not be there) within your backlog
* Ways to split user stories into a more manageable size
* Mapping your way to acceptance criteria
Techniques for Effectively Slicing User Stories by Naresh JainNaresh Jain
In order to achieve my goals, as a buyer of your product, I want awesome feature. AT: make sure your users stories don't get in the way.
Users Stories, the tool teams use to break big ideas into small demonstrable deliverable, are easy to describe and challenging to write effectively. In this hands-on workshop you'll learn how to write great user stories and acceptance criteria, that everyone on the team understands. We'll learn various techniques to slice your stories using the tracer-bullet approach. We will discuss what elements should be included in the stories, what criteria you should keep in mind while slicing stories; why the size of your user story is important and how to make them smaller and efficient.
Agenda:
What do you do to Large Stories? Spike, Split, Stub & Timebox (SSST) technique.
Core Slicing Techniques:
1. System Slice
1.a. Static vs. Dynamic
1.b. Real-time vs. Batch Processing
1.c. Build vs. Buy
1.d. Automated vs. Manual Steps
1.e. Defer certain roles
2. Behavioural Slice
2.a. Adjusting Sophistication - MVF (Minimum Viable Feature) or Walking Skeleton
2.a.1. Acceptance Criteria
2.b. By-pass certain steps in the workflow
2.c. Focus on Happy Path First (edge cases later)
2.d. No options - 1 option - Many options
3. Incrementally improve ‘Ilities' (Usability, Scalability, Reliability, etc.)
3.a. Simpler UI (even consider using a standard UI)
3.b. Minmal Data
3.c. Improve Performance Iteratively
User stories writing - Codemotion 2013Stefano Leli
Stefano Leli (Freelance) - Fabio Armani (OpenWare)
Scrivere user stories dovrebbe essere facile...almeno in teoria. In realtà nella pratica ci troviamo troppo spesso a combattere con storie vaghe o troppo tecniche, storie che non possono essere testate o addirittura che non portano alcun valore. In questo workshop cercheremo assieme di comprendere la differenza tra requisiti funzionali e User Story, tra User Story e Use Case, mediante dei case study.
User Stories Writing - Codemotion 2013Fabio Armani
Stefano Leli (Freelance) - Fabio Armani (OpenWare)
Scrivere user stories dovrebbe essere facile...almeno in teoria. In realtà nella pratica ci troviamo troppo spesso a combattere con storie vaghe o troppo tecniche, storie che non possono essere testate o addirittura che non portano alcun valore. In questo workshop cercheremo assieme di comprendere la differenza tra requisiti funzionali e User Story, tra User Story e Use Case, mediante dei case study.
What are User Stories? How should we write them? How to write them well?
Effective User Stories allow your team to be effective (deliver want the User needs) and efficient (Deliver it quickly and importantly don't deliver unneeded features).
Workshop for slicing stories, that leads you through concepts of thinning features and a technique for getting to the right level of stories for your teams using a slicing grid.
Materials to support the presentation and run a simulation are available here:
https://www.dropbox.com/sh/t04oqed47esv8ut/AACReMMiK_zYcRTBpjHPf4eDa?dl=0
Writing Good User Stories (Hint: It's not about writing)one80
User stories are typically the foundation of the Product Backlog. However, the original purpose has been lost. This is from a presentation that was given to help remind everyone of what User Stories are, and what they aren't. The purpose of User Stories is to drive conversations, not to hand "requirements" from one group to the next.
Behaviour Driven Development (BDD) is an evolution of test-driven development that places explicit emphasis on language, communication and 'outside-in' development. Many people are familiar with the 'Given,When,Then' structure used in BDD specifications (or acceptance tests) but is that really where it ends? In this session Antony Marcano gives a short intro to BDD, explains 'outside-in' development. Using a metaphor from learning theory and HCI principles, he'll show you how to go beyond 'Given,When,Then' to a shared understanding of
your customer's needs.
Tutorial: Implementing Specification-By-Example with GherkinChristian Hassa
1/2 day Tutorial held at XP 2013 conference in Vienna
Many teams struggle with the implementation of user story acceptance criteria and having a shared understanding about the expected story outcomes. This often results in missed stakeholder expectations, ad-hoc assumptions made by the team during implementation and conflict between team members and the product owner around testing.
In this tutorial, you will learn how specification-by-example and acceptance test driven development will address team conflict, missed stakeholder expectations and overall increasing the level of clarity on the project end-to-end. The presentation will cover the theory behind ATDD, case-studies and practical experience from real projects and several hands-on exercises to try out the presented concepts.
You will leave this tutorial with a fundamental understanding of specification-by-example and its benefits, as well as concrete pointers on how to get started using it in your own projects.
Specification by example and agile acceptance testinggojkoadzic
Specification by example and agile acceptance testing, presentation given to HSBC developers on 21/09/09 for more info see http://specificationbyexample.com
Many teams struggle with the implementation of user story acceptance criteria and having a shared understanding about the expected story outcomes. This often results in missed stakeholder expectations, ad-hoc assumptions made by the team during implementation and conflict between team members and the product owner around testing.
This session shows how specification-by-example and acceptance test driven development will address team conflict, missed stakeholder expectations and overall increasing the level of clarity on the project end-to-end. The presentation will cover the theory behind ATDD and case-studies and practical experience from real projects.
The talk was held at the ALM summit 3 in Redmond, January 2013. Recording of the talk can be found here: http://channel9.msdn.com/Events/ALM-Summit/ALM-Summit-3/Implementing-ATDD-and-Specification-By-Example
With the creation of the cucumber framework came the creation of the Gherkin Scripting format (also known as the Given-When-Then format). The structure of a Gherkin script is very straight-forward: Given provides you with the background When tells you what is being created Then tells you the expected results. Writing a script in a Given-When-Then format may be fairly simple. Writing a good Gherkin Script is an Art. Some are Picassos, some are Monets, some look like they were created by a toddler with a crayon. In this presentation Mr. Eakin will offer some tips on writing good Gherkin Scripts and show you how a well crafted Gherkin Script can be a beautiful work of Art.
An Overview of User Acceptance Testing (UAT)Usersnap
What is User Acceptance Testing? Also known as UAT or UAT testing.
it's basically, a process of verifying that a solution works for the user.
And the key word here, is user. This is crucial, because they’re the people who will use the software on a daily basis. There are many aspects to consider with respect to software functionality. There’s unit testing, functional testing, integration testing, and system testing, amongst many others.
What Is User Acceptance Testing?
I’ll keep it simple; according to Techopedia, UAT (some people call it UAT testing as well) is:
User acceptance testing (UAT) is the last phase of the software testing process. During UAT, actual software users test the software to make sure it can handle required tasks in real-world scenarios, according to specifications. UAT is one of the final and critical software project procedures that must occur before newly developed software is rolled out to the market.
User acceptance testing (UAT), otherwise known as Beta, Application, or End-User Testing, is often considered the last phase in the web development process, the one before final installation of the software on the client site, or final distribution of it.
Re-uploading my User Story Splitting workshop; it seems to have gone missing.
This is a slide deck I have used for helping people learn various user story splitting techniques.
Launches, SEO, Adwords, Twitter, Blog, Search Engine, Keyword ResearchMike Roberts
- Embarrassing Mistakes I've Made In Launches
- Things I've Learned
- Detailed Launch Plan for SpyFu SEO RECON Files (Agency Ready White Label SEO Reporting).
See the presentation here: http://vimeo.com/14965166
Jeff Lopez Presentation for Agile Impact Conference 2018 Day 1.
"Learn speedy affinity facilitation techniques to eliminate waste and boost productivity in creating, prioritizing and estimating a backlog."
Scrum XP è sempre più la metodologia di riferimento per i team e alcuni concetti sono divenuti di uso comune per chiunque operi nel mondo dell’IT (sia piccole realtà sia grandi aziende). Tra questi spiccano termini come user story e Product Backlog.
L’utilizzo delle user story ha sempre più spesso rimpiazzato i tradizionali documenti di specifiche funzionali e gli use case, mentre il Product Backlog è diventato lo strumento per tracciare tutto ciò che riguarda la realizzazione di un Prodotto.
Eppure entrambi hanno una serie di punti deboli. In questo talk mi concentrerò da una parte sulla difficoltà di avere un quadro completo ed evoluto a partire dal Backlog che è aihme piatto e mono dimensionale e dall’altro parlerò di cosa vuol dire veramente avere un approccio iterativo e incrementale nello sviluppo di un sistema.
Xp 2016 superchargeyourproductbacklogwithuserstories-suzannelazLaz Allen
Presented at xP2016 by Suzanne Morrison and Laz Allen.
Abstract: In this fun, interactive workshop you'll learn how manage your product backlog, write good user stories, split stories, add acceptance criteria and more.The workshop is a combination of theory and practice that alternates between teaching new concepts and techniques, practising them and then debriefing.
In this workshop you'll receive a list of home improvement requirements and you'll work in a group and in pairs to create user stories, critique user stories, use different patterns to split user stories and write acceptance criteria.
At the end of the session you'll have a clear understanding of how to keep your product backlog in good shape using user stories and other Agile techniques.
The workshop has been running at Skyscanner on a monthly basis for over a year and is attended by people in lots of different roles across the company including developers, testers, product owners, marketing managers and designers. Skyscanner is structured using a Spotify inspired squads and tribes model which we have adapted to work with our culture and values. We encourage our squads to self-organise in an agile way and use techniques as appropriate from Agile and Lean.
In this simple presentation, the logic of sub-tasking a User story is explained and an example is provided. Interesting information for teams trying to understand why they should be doing it and the thinking process to accomplish the logic.
The Customer Journey applied to the buying and shopping experience at IKEA: from the wow moment to the how moment.
Step by step as an example how to make the customer journey an interesting and useful tool.
User Story Writing & Estimation For Testers By Mahesh VaradharajanAgile Testing Alliance
This session aims to introduce the critical aspects of user story formulation like INVEST principle, requirements hierarchy in Agile - with focus on aspects related to Agile Testing, such that it fits into the overall theme of the event. Through an exercise, with Lego blocks, the session will address the following aspects: Testability of user stories and importance of acceptance criteria. Handling NFRs - either as part of acceptance criteria or a new user stories. DoD and accommodating testing efforts as part of user story estimation; Defects as user stories. Dependency management between user stories via story maps.
Talk including Demo for the learning objectives outlined above
Aubrey Smith, Sparked Advisory
In this training, we will build on the foundation established in Lean Startup 101 and 201 by delving into examples and cases of the Lean Startup concepts in action. Attendees of Lean Startup 301 will be exposed to cutting edge work from thought leaders and experts using Lean Startup in practice today — at startups and within the enterprise. Participation in this session is essential: You will be asked to help design an MVP and experiment to test critical Leap of Faith Assumption(s) in groups and will be encourage to share experiences. The session is designed to allow attendees to stretch their skills and to push one-another to ‘learn by doing’. The session will also include:
Sample cases and live interviews with practitioners highlighting the application of core concepts;
Exercises designed to bring the concepts to life and challenge participants to deepen their skills;
Discussion of advanced topics such organizational culture and governance as well as industry-specific concepts such as using Lean Startup in heavily regulated markets.
Thanks to Lean Startup Co.’s law firm, Orrick, for being the sponsor for this track.
Wrestling with Conway's Law: How to support cross-functional teams working on...Dr. Alexander Schwartz
Talk for the Agile Testing Days 2023.
Mel Conway published in 1968 the observation that the communication structure of a company has an impact on the architecture of the produced software components.
Nowadays many organizations use the “feature team approach”, that is, a preference for cross-functional teams which deliver value without depending on other teams. An implication is that several feature teams are going to work on the same components, which implies that the traditional concepts of strong component ownership are no longer applicable. This generates a myriad of challenges, e.g. teams waiting for code review from other teams.
In this talk we first revisit Conway’s Law and then explore what is required to ensure success of feature teams working on shared components. First and foremost, does the architecture, the processes, etc. really support the requirement of ease of changing a shared component?
Talk presented at the Agile Tour Vienna 2016 conference.
http://agiletourvienna.at/#scheduleModal-does-agile-mean-we-have-less-time-for-testing
ABSTRACT:
In the last decade, the speed of our industry has increased greatly. Agile Development, DevOps and Continuous Delivery are the main drivers for this paradigm shift which has now become widely accepted.
Ten years ago, it was common to only release a couple of new versions a year. Today, there are companies delivering hundreds of software deployments per day. This isn’t only true in IT, but also e.g. for Tesla-Automobile, which delivers its software updates a few times a week.
Where does quality happen when we’re releasing this often? Is it possible to have proper quality management and is there enough time for testing? How can we reduce what could be weeks of testing to deliver new features to our clients on a daily basis?
Alex is a long-term enthusiast for this topic. Based on his experiences with various products and companies, he’ll share his insights into the mystery of “faster testing”. The key questions are:
- When – When do we test?
- What – What should we test?
- Which quality aspects are important?
- How – How do we test? Which techniques are helpful?
- Who – Who is involved in testing, test automation, etc.?
- How much – How much should we test?
Furthermore, we discuss the financial benefits of Agile Testing and aiming for Continuous Quality. Last but not least we explore if it only exists in fairy tale land or if it is real.
Talk provided at ASQF meetup "Fachgruppentreffen" in Braunschweig, 18th August 2016
In the last decade, the speed of our industry has increased greatly. Agile Development, DevOps and Continuous Delivery are the main drivers for this paradigm shift which has now become widely accepted.
Ten years ago, it was common to only release a couple of new versions a year. Today, there are companies delivering hundreds of software deployments per day. This isn't only true in IT, but also e.g. for Tesla-Automobile, which delivers its software updates a few times a week.
Where does quality happen when we're releasing this often? Is it possible to have proper quality management and is there enough time for testing? How can we reduce what could be weeks of testing to deliver new features to our clients on a daily basis?
Alex is a long-term enthusiast for this topic. Based on his experiences with various products and companies, he'll share his insights into the mystery of "faster testing". The key questions are:
How can we guarantee quality
When do we test?
How do we test?
How often do we test and what don't we test?
and finallyt: Who does the testing?
Together we will discuss our common problems, approaches and best practices.
Flipcharts of the workshop (in german) "Splitting User Stories with Elefant Carpaccio", facicilated 7th June, 2016 at the Scrum-Day in Stuttgart.
#scrumday #scrumday16
Slides of a workshop facilitated by Fanny Pittack and Alex Schwartz at the conference Agile Testing Days 2015 in Potsdam.
Main Statement:
Change dojos are creating a safe environment for practicing skills for change agents. It sets fundamentals for you and allow you to perform change.
This workshop is for everyone who is involved in improving his or her environment. As the ATD 2015 conference theme states, mastering Agile might be the competitive edge for your organization – and this requires great skills to transform your environment, to change it towards the goal of Agile mastery.In our last years keynote “Insights of Happy Change Agents” we scratched the surface of how to become a “Happy Change Agent”, how to initiate changes with ease and enthusiasm, fun and success. In this workshop we aim to dive deeper.The first part of our workshop is dedicated to the “change dojo” format. Together with your pairing partner you simulate the interaction of a change agent with a team or coachee. We practice different scenarios and we will focus step by step on various aspects like pace, distance, keeping your own space, as well as communicating clearly with your body. This provides a chance to receive instant feedback how the change is perceived by the coachee. One key learning is to appreciate any sign of frustration as a valuable indicator.The second part is intended to storytelling and listening exercises. We all have buried a story of change that somehow failed. If you attend our workshop, please bring your story with you.
Key Learnings:
- Exercises to bring back to your workplace, to practice with your team
- How to be open for feedback and listen
- How to sketch your story on a story board
- How to use your frustration as indicator
- How to reflect in various situations
Audience:
Tester, Developer, Product Owner, Scrum Master, Agile Manager, Change Agents, Agile Coach
slides of a workshop (in German) facilitated at the ScrumDay 2015 (http://www.scrum-day.de/) in Stuttgart.
Lanyrd:
http://lanyrd.com/2015/scrum-day/sdpmgb/
Abstract:
Coding Dojos sind sehr bekannt und sind nun ein anerkanntes Hilfsmittel um Wissen zu vermitteln und unser Kung-Fu zu verbessern. Warum dieses Format, diese Lernmethode nicht auch für andere Themen verwenden?
In diesem Dojo fokussieren wir uns auf User Stories: ihre Akzeptanzkriterien und wie wir grosse Stories in kleinere zerschneiden können.
In Gruppenübungen werden wir unser Kung-Fu verbessern. Vielleicht wird Deine Gruppe auf Yoda-Niveau erreichen: alle Mini-Stories haben einen Wert und sind MMFs (minimal markatable features) im Sinne des Lean Startup?
Slides of a keynote talk by Fanny Pittack and Alexander Schwartz at the conference Agile Testing Days 2014 in Potsdam. http://www.agiletestingdays.com/ #AgileTd
presented at Berlin DevOps Meetup April 29, 2014.
Explains our experiences establishing DevOps and Continuous Delivery for the Places RESTful API at HERE, a Nokia business.
How our product, the HERE Places RESTful API, ripened over time and how our understanding of quality changed over time.
As every distinguished wine is the result of a long refining and ripening process, every software product is subject to a similar evolution, too. Of course along the journey of a product, the understanding of “Quality” is subject to major changes as well.
Lets join the 3-year journey of a software product through its various stages, from planning, seeding to its first wine tasting (that is, the beta offer), to selling the first bottles (that is, the service is used by other internal products), finally to its market readiness (that is, becoming a commercial B2B offer with SLAs).
The product under test is the Places RESTful API (places.demo.api.here.com), which delivers data for Places that are shown in various products, for instance for Nokia’s HERE.com maps.
We concentrate on three different aspects and how they change over time:
* the understanding of what quality means,
* the test strategy, and last but not least
* how to deal with the intrinsic complexity.
We are going to explore the post production deployment part of our process: How we ensure the high availability of this complex service, as well as which test techniques, feedback mechanisms and in particular which visualizations (monitoring 2.0) we leverage for this purpose.
Presented a the Agile Testing Days 2013.
Presented at the goto;conference in Berlin 2013 (http://gotocon.com/berlin-2013).
Most teams introducing Continuous Delivery face problems such as "How do we fit our 4-day QA phase into a daily release rhythm?"
The transition to a DevOps strategy and Continuous Delivery usually requires a significant readjustment of the testing approach.
Alex shares stories from various companies he worked for, and discusses different ideas on how to retrofit testing for frequent releases. This includes adapting the rhythm of testing, test techniques, scope of testing, and re-thinking the entire quality assurance approach.
presented at the conference Agile Testing Days 2012 in Berlin/Potsdam
Original version on prezi: http://prezi.com/o39xxactxm6o/how-releasing-faster-changes-testing/
ABSTRACT:
In his keynote at the ATD2011 Gojo Adzic covered the “Five key challenges for agile testers tomorrow”. The first one mentioned is the impact of shorter release cycles on testing: “release cycles will get shorter, so short even that there’s no time for testing.”
In this talk Alex shares what he learned about this topic during the last four years, on his journey with two companies. In both companies he helped to change the release rhythm dramatically, which had a deep impact on the all facets of the test strategy, of course including cooperation and communication structures.
Whereas some lessons learned are obvious, others are unexpected and even counter-intuitive.
Italy Agriculture Equipment Market Outlook to 2027harveenkaur52
Agriculture and Animal Care
Ken Research has an expertise in Agriculture and Animal Care sector and offer vast collection of information related to all major aspects such as Agriculture equipment, Crop Protection, Seed, Agriculture Chemical, Fertilizers, Protected Cultivators, Palm Oil, Hybrid Seed, Animal Feed additives and many more.
Our continuous study and findings in agriculture sector provide better insights to companies dealing with related product and services, government and agriculture associations, researchers and students to well understand the present and expected scenario.
Our Animal care category provides solutions on Animal Healthcare and related products and services, including, animal feed additives, vaccination
Meet up Milano 14 _ Axpo Italia_ Migration from Mule3 (On-prem) to.pdfFlorence Consulting
Quattordicesimo Meetup di Milano, tenutosi a Milano il 23 Maggio 2024 dalle ore 17:00 alle ore 18:30 in presenza e da remoto.
Abbiamo parlato di come Axpo Italia S.p.A. ha ridotto il technical debt migrando le proprie APIs da Mule 3.9 a Mule 4.4 passando anche da on-premises a CloudHub 1.0.
1.Wireless Communication System_Wireless communication is a broad term that i...JeyaPerumal1
Wireless communication involves the transmission of information over a distance without the help of wires, cables or any other forms of electrical conductors.
Wireless communication is a broad term that incorporates all procedures and forms of connecting and communicating between two or more devices using a wireless signal through wireless communication technologies and devices.
Features of Wireless Communication
The evolution of wireless technology has brought many advancements with its effective features.
The transmitted distance can be anywhere between a few meters (for example, a television's remote control) and thousands of kilometers (for example, radio communication).
Wireless communication can be used for cellular telephony, wireless access to the internet, wireless home networking, and so on.
Bridging the Digital Gap Brad Spiegel Macon, GA Initiative.pptxBrad Spiegel Macon GA
Brad Spiegel Macon GA’s journey exemplifies the profound impact that one individual can have on their community. Through his unwavering dedication to digital inclusion, he’s not only bridging the gap in Macon but also setting an example for others to follow.
This 7-second Brain Wave Ritual Attracts Money To You.!nirahealhty
Discover the power of a simple 7-second brain wave ritual that can attract wealth and abundance into your life. By tapping into specific brain frequencies, this technique helps you manifest financial success effortlessly. Ready to transform your financial future? Try this powerful ritual and start attracting money today!
5. Story Splitting Dojo
• Born end of 2010
• Inspired by Lisa Crispin,
at Agile Testing Days 2010
• Max participants: 50
• Number of sessions: approx. 30
most in my company (HERE/Nokia)
+ a few on conferences
6. Story Splitting Dojo: Setup & Roles
Responsibilities 1 x facilitator
1 x product owner
Facilitator
• Watches the process
• Does not answer question
regarding the story/epic
Product Owner
• Answers questions
regarding the story/epic
• Does not help to split the
story/epic
Padovan
• Works on splitting the
story/epic
…
Up to 5 working groups
with up to 8 padovans each
…
7. Story Splitting Dojo: Setup & Roles
2-5 product owner 1 x facilitator
…
Up to 10 working groups
with up to 10 padovans each
…
…
…
- XL variant -
…
8. Let’s take it away… or onegaishimasu!
Facilitator
mingles with POs
Build your team
• Introduce yourself
• Agree on a name for
your team
• Agree on the most
important purpose to
split stories
…
9. How we will split Epics/Stories?
Huge Story
or
Epic
Story #1
Story #2
Story #3
…
Story #4
First story with scenarios using
GIVEN-WHEN-THEN
10. Example for Scenarios
As a user of MyCoolBlog.com, I want to login into my blog, such
that I can start sharing my thoughts.
Scenario: Login with valid credentials works.
Given a user of MyCoolBlog.com with its login credentials
When the user logs in
Then the login is accepted
And the homepage of the user is shown.
Scenario: A login with invalid credentials is rejected.
Given a user of MyCoolBlog.com with its user name and wrong password
When the user logs in
Then the login is rejected
And the forgotten password page is displayed.
11. Warm-up Exercise
From the example story below, create acceptance criteria for
scenarios using the GIVEN-WHEN-THEN style.
Story
As an internet shopper, I want to specify the address to which
my items are to be shipped, so that I can get the items I
ordered.
Notes
• There are already items in the cart
• There is no shipping available outside of Germany
• An address checking service exists
• The next step in the flow is checkout
12. From the example story below,
create acceptance criteria for
scenarios using the GIVEN-WHEN-
THEN style.
Story
As an internet shopper, I want to
specify the address to which my
items are to be shipped, so that I
can get the items I ordered.
Notes
• There are already items in the
cart
• There is no shipping available
outside of Germany
• An address checking service
exists
• The next step in the flow is
checkout
Warm-up Exercise - Debrief
• What did you experienced
in your group?
• Was it easy to select the
WHEN?
• What if the external service
is down?
16. Questions for Round #2
• What is the smallest slice?
• Is there an example of “business value
without implementation”?
• Is there a potential legal issue?
• Thinking about hosting/operations: Is there a
risk of an outage? If so, how you deal with it?
17. Retrospective
• What did you experienced in your group?
• What did you learn about Story Splitting?
• How to better practice Story Splitting?
• Other example stories?
• What do you like about this Dojo format?
• What are your ideas for improvement?
19. Thanks!
or
domo arigato gozaimashita
Please provide feedback!
20. Background: Resources covering Story Splitting
• Arto Eskelinen conducted a workshop “Slicing User Stories” on the Global Scrum
Gathering Berlin 2014 and used a nice pragmatic technique
• Mike Cohn mentions in his book “Estimation and Planning” several good ideas for
slicing
• Gojko Adzic introduced the Hamburger Method for slicing stories:
http://gojko.net/2012/01/23/splitting-user-stories-the-hamburger-method/
• Paul Boos has a pretty comprehensive slide deck “User Story Splitting”,
http://de.slideshare.net/pmboos/user-story-splitting
• The InfoQ article http://www.infoq.com/news/2011/04/how-to-split-user-stories
provides a good overview of different approaches
Hint for searching for more references:
There are two terms: “story splitting” and “story slicing”.
21. Graphical
Summary
Benjamin
Felis
provided a
sketch of the
session:
https://twitter.com/be
njaminfelis/status/514
363329562038272/ph
oto/1
Thanks!