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.
User Story Mapping, Discover the whole storyJeff Patton
Variations of these slides have been used in a variety of talks.
These slides support discussions on why stories work, and when they don't. And, on story mapping, how and why it works.
User Story Maps: Secrets for Better Backlogs and PlanningAaron Sanders
User story mapping is an intuitive way to build and organize a product backlog. During this session you’ll get hands-on experience building a user story map. You’ll learn:
How story mapping drives productive conversations with users and stakeholders.
How to plan incremental releases of your product using minimal holistic slices that deliver value at each product release.
Secrets to effective prioritization for both planning releases, and figuring out what to build next.
Tactical management of your backlog as you grow your working software to releasability.
The backlog building and managing strategies in this session will take you well beyond the agile basics.
Lean Startup + Story Mapping = Awesome Products FasterBrad Swanson
To deliver the right outcomes, you need to learn your customers needs and validate your assumptions as early as possible. This means getting an early version of your product completed to start testing, validating and improving. This session will demonstrate how to combine Lean Startup and User Story Mapping techniques to determine where to start and how to learn early and often.
Participants will start with a partially completed Lean Canvas to flesh out and then define a product roadmap by building a Story Map. We will use Lean Startup concepts of Minimal Viable Product (MVP) and validated learning to focus on outcome over output.
Learning objectives:
Understand the importance of accelerated learning and techniques to achieve it
How a Lean Canvas can help shape your product vision and MVP
How to build a story map to create a product roadmap
How to use a story map to validate your users' journey
User Story Mapping, Discover the whole storyJeff Patton
Variations of these slides have been used in a variety of talks.
These slides support discussions on why stories work, and when they don't. And, on story mapping, how and why it works.
User Story Maps: Secrets for Better Backlogs and PlanningAaron Sanders
User story mapping is an intuitive way to build and organize a product backlog. During this session you’ll get hands-on experience building a user story map. You’ll learn:
How story mapping drives productive conversations with users and stakeholders.
How to plan incremental releases of your product using minimal holistic slices that deliver value at each product release.
Secrets to effective prioritization for both planning releases, and figuring out what to build next.
Tactical management of your backlog as you grow your working software to releasability.
The backlog building and managing strategies in this session will take you well beyond the agile basics.
Lean Startup + Story Mapping = Awesome Products FasterBrad Swanson
To deliver the right outcomes, you need to learn your customers needs and validate your assumptions as early as possible. This means getting an early version of your product completed to start testing, validating and improving. This session will demonstrate how to combine Lean Startup and User Story Mapping techniques to determine where to start and how to learn early and often.
Participants will start with a partially completed Lean Canvas to flesh out and then define a product roadmap by building a Story Map. We will use Lean Startup concepts of Minimal Viable Product (MVP) and validated learning to focus on outcome over output.
Learning objectives:
Understand the importance of accelerated learning and techniques to achieve it
How a Lean Canvas can help shape your product vision and MVP
How to build a story map to create a product roadmap
How to use a story map to validate your users' journey
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.
User Story Mapping workshop facilitated at NYC Scrum User group.
Inspired by Jeff Patton's book "User Story Mapping. Discover the Whole Story, Build the Right Product"
http://shop.oreilly.com/product/0636920033851.do
User Story Mapping Workshop (Design Skills 2016)Bartosz Mozyrko
User Story Mapping (USM) is a top-down approach of gathering "requirements" in agile environments.
"A user story map arranges user stories into a useful model to help understand the functionality of the system, identify holes and omissions in your backlog, and effectively plan holistic releases that deliver value to users and business with each release (from Jeff Patton's The New User Story Backlog Is a Map)."
"How to write better User Stories" por @jrhuertawebcat
Presentación realizada en el #webcat Barcelona de Abril 2013
Autor: José E. Rodríguez (@jrhuerta)
------------------------------------------------
RECURSOS:
- Agile Barcelona
http://agile-barcelona.org/
- "User Stories Applied: For Agile Software Development", Mike Cohn, 2004, Addison-Wesley Professional
http://www.amazon.com/User-Stories-Applied-Software-Development/dp/0321205685
- "Lean UX", Jeff Gothelf & Josh Seiden, 2012, O'Reilly Media
http://www.leanuxbook.com/
Introduction to user story mapping open camp editionMichael Calleia
Revised and expanded talk on User Story Mapping.
User Story Mapping is a simple yet powerful and flexible tool that combines the visualization of software systems and user needs. While not the only tool you need, it is a powerful one to learn and keep in your toolkit. Learn to go from user stories to better conversations while increasing shared understanding.
"From Design Thinking to Design Doing" Suzanne Pellican's presentation from the O'Reilly Design conference on January 21, 2016 at Fort Mason in San Francisco, CA.
A talk I gave at Google on Strategy and Product Discovery
We discussed:
Discovering Features and Products (Product Strategy)
Discovering Products and Product Lines (Product Line / Company Strategy)
Marty Cagan: Using High Fidelity Prototypes for Product Discovery
Arlen Bankston
Arlen is an established leader in the application and evolution of process management methodologies such as Lean, Six Sigma and BPM, as well as Agile software development processes such as Extreme Programming (XP) and Scrum. He is a Lean Six Sigma Master Black Belt and Certified ScrumMaster Trainer. He also has twelve years of experience in product design, leveraging principles of information architecture, interaction design and usability to develop innovative products that meet customers’ expressed and unspoken needs. Arlen has led Agile and Lean deployment and managed process improvement projects at clients such as Capital One, T. Rowe Price, Freddie Mac, and the Armed Forces Benefits Association. Arlen’s recent work has centered on combining Lean Six Sigma process improvement methods with Agile execution to dramatically improve both the speed and quality of business results. He has also led the integration of interaction design and usability practices into Agile methodologies, presenting and training frequently at both industry conferences and to Fortune 100 clients.
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.
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.
Aula para a disciplina Produção e Ferramentas Colaborativas
Pós-Graduação em Engenharia de Software Centrada em Métodos Ágeis
Prof. Marcello de Campos Cardoso
www.mcardoso.com.br
Maio 2011
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.
User Story Mapping workshop facilitated at NYC Scrum User group.
Inspired by Jeff Patton's book "User Story Mapping. Discover the Whole Story, Build the Right Product"
http://shop.oreilly.com/product/0636920033851.do
User Story Mapping Workshop (Design Skills 2016)Bartosz Mozyrko
User Story Mapping (USM) is a top-down approach of gathering "requirements" in agile environments.
"A user story map arranges user stories into a useful model to help understand the functionality of the system, identify holes and omissions in your backlog, and effectively plan holistic releases that deliver value to users and business with each release (from Jeff Patton's The New User Story Backlog Is a Map)."
"How to write better User Stories" por @jrhuertawebcat
Presentación realizada en el #webcat Barcelona de Abril 2013
Autor: José E. Rodríguez (@jrhuerta)
------------------------------------------------
RECURSOS:
- Agile Barcelona
http://agile-barcelona.org/
- "User Stories Applied: For Agile Software Development", Mike Cohn, 2004, Addison-Wesley Professional
http://www.amazon.com/User-Stories-Applied-Software-Development/dp/0321205685
- "Lean UX", Jeff Gothelf & Josh Seiden, 2012, O'Reilly Media
http://www.leanuxbook.com/
Introduction to user story mapping open camp editionMichael Calleia
Revised and expanded talk on User Story Mapping.
User Story Mapping is a simple yet powerful and flexible tool that combines the visualization of software systems and user needs. While not the only tool you need, it is a powerful one to learn and keep in your toolkit. Learn to go from user stories to better conversations while increasing shared understanding.
"From Design Thinking to Design Doing" Suzanne Pellican's presentation from the O'Reilly Design conference on January 21, 2016 at Fort Mason in San Francisco, CA.
A talk I gave at Google on Strategy and Product Discovery
We discussed:
Discovering Features and Products (Product Strategy)
Discovering Products and Product Lines (Product Line / Company Strategy)
Marty Cagan: Using High Fidelity Prototypes for Product Discovery
Arlen Bankston
Arlen is an established leader in the application and evolution of process management methodologies such as Lean, Six Sigma and BPM, as well as Agile software development processes such as Extreme Programming (XP) and Scrum. He is a Lean Six Sigma Master Black Belt and Certified ScrumMaster Trainer. He also has twelve years of experience in product design, leveraging principles of information architecture, interaction design and usability to develop innovative products that meet customers’ expressed and unspoken needs. Arlen has led Agile and Lean deployment and managed process improvement projects at clients such as Capital One, T. Rowe Price, Freddie Mac, and the Armed Forces Benefits Association. Arlen’s recent work has centered on combining Lean Six Sigma process improvement methods with Agile execution to dramatically improve both the speed and quality of business results. He has also led the integration of interaction design and usability practices into Agile methodologies, presenting and training frequently at both industry conferences and to Fortune 100 clients.
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.
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.
Aula para a disciplina Produção e Ferramentas Colaborativas
Pós-Graduação em Engenharia de Software Centrada em Métodos Ágeis
Prof. Marcello de Campos Cardoso
www.mcardoso.com.br
Maio 2011
User story mapping para planejamento de produtos interativos (ambiente ágil)Karine Drumond
Esta foi minha apresentação no IHC2010. Artigo industrial que apresentou a técnica de story mapping, sua aplicação, benefícios e desafios para planejamento de produtos interativos em ambientes ágeis.
Remote collaboration is important for any line of work where people are divided by time and space, but the need is expanded in a creative industry where there is an increased requirement of collaboration, communication, and execution of ideas.
When you work for a creative agency with colleagues and clients around the country (and developers around the world), how can you improve and streamline the creative collaboration process?
Découvrir la technique des User Story Mapping facilement et en s'inspirant de votre expérience du matin, d'après la version de Jeff PATTON !
Public : Product Owner, Product Manager, Innovation, Startup, UX, etc
Heredamos de nuestros progenitores dos juegos de cromosomas, uno procedente del padre, y otro, de la madre. Todas las células somáticas del ser humano tienen 23 pares de cromosomas. Cada par contiene uno de los caracteres, una pareja de genes en posiciones análogas, aunque no necesariamente con las misma información. Esos dos genes portadores de la información para el mismo carácter se denominan alelos, y la pareja de cromosomas se conoce como par de cromosomas homólogos
Introduce gathering stories technologies as user interview, questionnaires, observation & story-writing workshops.
Share some guidelines and real cases about to make good stories as size the story to the horizon & including user roles in the stories.
Jumpstart Your Web App
Presented by Ari Rizzitano on
July 11th, 2012
Just about everyone has an idea for a web app, whether you want to implement a business tool, found a startup, or just host a fun project. Learn how to tackle design and technical challenges, take advantage of best practices, power through obstacles, and grow your idea into a successful application.
We spend so much time focusing on conventional programming. Everyone focuses on standards, code clarity, testing, and what gems to use. Let's chat about what's done before your fingers hit the keys. Let's talk about brainstorming, requirements, stakeholders, mock-ups, and writing solid user stories and acceptance tests with Cucumber. Every project has a story - how will your next one end?
Are agile and user experience design compatible? Can they work together or is agile a square hole to the UX round peg? We contend that they are compatible. We help you recognize your company's UX appetite, regardless of software methodology. We then look at how agile changes things, discuss some of the UX practices developers need to understand (including CRAP), show how UX and developers can collaborate, and finally discuss agile and UX in the wild.
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.
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.
This presentation helps non-coders understand the mechanics behind a web application.
Use it to shorten the time to build your first web app or better communicate your development needs to a progammer.
Product development - From Idea to Reality - VYE Leader TalkBui Hai An
Product development - From Idea to Reality - Viet Youth Entrepreneur Bootcamp Leader Talk.
Sharing to help VYE Boot-camper solidify their ideas and prepare for better pitch.
Tools for Entrepreneurs: Create. Collaborate. Communicate.Sara Rosso
I created this presentation for entrepreneurs who need online tools to make their ideas happen (I gave it earlier this year at the Professional Women's Association in Milan).
The presentation "Tools for Entrepreneurs: Create. Collaborate. Communicate." started out as a way to explain very technical things to non-technical people, but I quickly realized that most people when approaching technology get intimidated by the "What's DNS? Do I need a dedicated server?" kind of questions and therefore feel they can't understand technology.
I feel that this technology intimidation is really due to the fact that they don't really own their idea, and better understanding it will guide any decisions they have to make with their idea moving forward.
So I focus on how to further refine your idea so you can move it forward, even with help, by having a better mastery over what you need and what your users need. I also cover some techniques and tools for collaborating with developers, external consultants, and other remote workers. Then, I briefly touch on communication strategies online and how your site won't be the only place communication happens but it should be the digital hub with the most useful and authoritative information about your company, and how you can develop a communication strategy that spans several types of networks.
The appendix includes some open source software alternatives for growing a business on a bootstrap budget.
Web design training , Web Design Training In KolkataW3webschool
W3webschool trusted and best Digital Marketing Training,Web Design Training,SEO Training,Php Training center Kolkata,India.
https://www.w3webschool.com/web-design/
Rapid Evolution of Web Dev? aka Talking About The WebPINT Inc
Thomas Powell gives a Meme peppered talk at Interactive Day San Diego about the Web and Web Dev tech focusing on how far (or not) we have come since the late 1990s.
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
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.
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
Moving Towards Zero Defects with Specification by ExampleSteve Rogalsky
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.
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.
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
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.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
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.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
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
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
4. Group Group Group
Task Task Task Task Task Task
5. About Me
• Agilist and team member at Protegra in
Winnipeg
– (It says “Application Architect” on my business
card)
• A Founder of Winnipeg Agile User Group
http://www.agilewinnipeg.com
• Twitter: @srogalsky
• http://winnipegagilist.blogspot.com
6. Learning Outcomes
User
User
Story
Stories
Mapping
What is a User How to Why Iterative vs.
User Story create bother? Incremental
Story Slicing them?
7.
8. What User Stories are not
Tasks • Create user table
• Create password
encryption service
• Create login service
• Create CSS
• Create page template
• Add login button
9. What User Stories are not
Big* • Login page
• “the web site”
• 160 hours of effort
* Exception – stories that are in the distance can be big. These stories will
shrink in size and grow in detail as they get closer to being implemented.
10. What User Stories are not
Use cases • Login Use Case
– Happy path:
• Login w/ valid pwd
– Alternate Paths:
• Login w/ invalid pwd
• Forgot password
• Reset password
• Password rules
A use case will often contain many user stories
11. What User Stories are not
A document • Login.docx
• “this document, by its
very size, ensures
that it will never be
read.” – Sir Winston
Churchill
12. What User Stories are…
A small piece of • As a user, I want to
functionality that login with my
provides some value to password, so that I
a user can gain access to
the site.
“A place holder for a conversation.”
13. What User Stories are…
I Independent *
N Negotiable (can be prioritized)
V Valuable (to a user)
E Estimable
S Small
T Testable
14. Formats
By the book:
As a [role], As a [mom]
I want to I want to
[some action], [login with my pwd]
so that so that
[goal] [I can gain access to the
site]
15. Formats
As a
Who [mom]
I want to
What [login with my pwd]
so that
Why [I can gain access to
the site]
The “by the book” format is great for learning, but at its
core, it is just Who/What/Why
16. Formats
Title; Sentence; • Title: Login w/ pwd
Acceptance Tests • Login w/ password and
show welcome page
• Test upper, lower,
numbers, special
characters, accents,
spaces
• Test mandatory lengths
• Test invalid pwds
17. Formats
Lean Startup:
Feature Feature
[X] [show sad face before
logging off]
will move Metric will move Metric
[Y] [time spent logged into
the site]
22. How not to Slice?
Tasks • Create user table
• Create password
encryption service
• Create login service
• Create CSS
• Create page template
• Add login button
23. How to Slice?
• By screen (for basic screens • By priority
only)
• By applying the INVEST
• By button model
• By group of fields • By acceptance criteria
• By workflow step • By option
• Optional workflow steps • By role
• Validation • By Subjective quality
• Error handling * (never by objective
• Admin functions (maintaining quality: always be
drop downs, etc)
defect free)
• By value
24. Other Tips
• Keep them as stories!
• Slice them small when needed, but don’t
get silly
• Slice any time
• When you are fighting over your planning
poker estimates – slice away.
• Slice more liberally if the story is higher
priority
33. How to do it?
1. Divide into groups of 3-5 people
2. Start by gathering “things people do” – the tasks. Write them
down individually and then read them aloud to your group
– Likely they start with a verb.
– These are high level user stories called “Tasks” (walking
skeleton)
– This forms your story map skeleton
3. Group them silently (simply because it is faster)
4. Name the groups and lay them out in order of time (left to
right)
– These are called “User Activities” (backbone)
5. Add more detailed user stories below the main tasks
6. Prioritize top to bottom
7. Break into releases
34. How to do it?
smithcdau (@smithcdau)
11-08-11 2:12 PM
RT @shanehastie: @jeffpatton if you're arguing
about sequence it probably means it doesn't
matter. #Agile2011 #yam
48. Iterative Advantages
• Validate your architecture and solution
early
• See and test the whole application early
• Encourages important stories to be built
first
49. Iterative Advantages
• Elicits improved feedback on the whole
application early
• Deliver your application early as early as
possible
• Discourages "gold plating"
• Helps contain scope
50. Iterative Disadvantages
• Your code and design has to be change
tolerant
• You have to be proficient at slicing your
user stories
• You won't know the final solution at the
beginning of the project
Prep:Print out cardsBring post-its and markers/pens
Cards: Agree/ Disagree / Not SureOutcome: Explain what a user story is and isn’tThis is a user story: As a developer, I want to setup the continuous integration server so that we can deploy continuously.This is a user story: Create the service to validate a username and passwordThis is a user story: Forget Password link by emailThis is a user story: Create and Implement the Login pageEach user story should be totally independentOutcome: Describe some reasons to slice stories and list a few ways of doing so“As a user I want to see my profile information so that I can verify its accuracy”. A good example of slicing this story is:Create the profile database tablesCreate the profile service to read the profile dataCreate the profile page to call the service and display the dataUser stories can be sliced by objective qualityUser stories should not be sliced by validation rulesA screen or web page is often a good size for a user story slice.A large story doesn’t need to be slicedOutcome: Describe the benefits of a user story mapA backlog is a list of tasks needed to complete a project.When starting a project a backlog is a great model for seeing the big pictureA user story mapping session can speed up project discoveryA user story map is a better way to visualize priorities than a traditional backlogA traditional backlog isn’t a good vehicle for finding project gapsOutcome: Describe to someone else the difference between iterative and incrementalIt is possible to build an entire horizontal slice of the application in one or two iterationsUser Story Mapping and Iterative Development are strongly relatedIt isn’t possible for your users to see and test the whole application within one or two iterationsIt is difficult to control scope on agile projectsKnowing the final solution before you start is importantOutcome: Be able to create your own user story map
Step 1: Generate tasksSplit up into groups of 3 to 5As individuals, think about your morning routine – the things you do.Write down each thing you do on one post-it note. Have everyone in your group use the same colour post-it for this exercise.Step 2: Read them outHave each person read their post-its out loud to the group and then place them in the middle of the table so that you can see all the post-its at once.Comments: Notice the similarities between your post-its and other peoples. Notice also that if you missed a few things, somebody else came up with the missing tasks. You probably all have things like “Brush Teeth”, “Get Dressed”, “Eat breakfast”. All starting with verbs.Step 3: GroupNow as a group, and without talking, move the post-its that are similar to each other closer to each other, and those that are not similar, move them farther apart. Those that are exact duplicates you can eliminate or put on top of each other.Step 4: Name the groupsYou should now have some distinct groups. As a group again, start labeling these groups with a different colour post-it. Just put the group name on top of the grouping.Step 5: Now re-arrange your groups in order of time from left to right. Put the group post-it at the top and the tasks below the group, but still in order left to right.(At this point, show a simple example)Overall comments:Your first user story map!The groups are called “User Activities” – this is the backbone of your applicationThe items below are called “User Tasks” – this is the walking skeleton of your application
Also posted as a kanban board in the room – but large enough to put stickies under in the ending exercise.
Boundary Object (scope). If used properly, you can use it to keep other scope out.Each story encompass all layers of the system. No value to the user without the layersHas value when completed
Talk – keep them as stories. Remember INVEST.
Highlighted my favourite ones…
User Activities are things that users do towards achieving a particular goal.User Tasks are specific steps within an activity. Tasks by themselves do not move towards a goal, but are required components of an activity.User Stories are small end-to-end vertical slices of functionality that implement User Tasks.
Time across (link back to breakfast)Priorities down (no more H/M/L, or must have, etc…Releases
An alternative to a backlogAllows you to see the big picture in your backlogBetter than a ‘flat’ backlog
Allows you to “Walk the map”A nice way to make sure you haven’t missed anythingBring in different users to walk through their scenarios.
Visualize building the important things firstbuilding a complete system firstIt isn’t about the precision of the model, but about a common understanding of the model
We created this in less than 30 minutes. Another 30 minutes it would have been estimated and we’re ready to go.Some in the lean community question whether backlogs (because it is inventory) is waste. When you use a user story map, your backlog now becomes the story of your project – something you look to understand the model as a whole. Plus, since you can create one so fast with this technique, it is hard to argue that it is wasteful.
We’re going to create a second map with some more detail and more relevance to software. You can move your old map out of the way.Practice – build your own MS Outlook competitor.Step 1: Generate tasksSplit up into groups of 3 to 5As individuals, think about your usage of your favourite e-mail toolWrite down each thing you do on one post-it note. Have everyone in your group use the same colour post-it for this exercise.Step 2: Read them outHave each person read their post-its out loud to the group and then place them in the middle of the table so that you can see all the post-its at once.Comments: Notice the similarities between your post-its and other peoples. Notice also that if you missed a few things, somebody else came up with the missing tasks. You probably all have things like “Send Email”, “Read Email”, “View Calendar”, “Create Contact”, etc.Again, all starting with verbs.Step 3: GroupNow as a group, and without talking, move the post-its that are similar to each other closer to each other, and those that are not similar, move them farther apart. Those that are exact duplicates you can eliminate or put on top of each other.Step 4: Name the groupsYou should now have some distinct groups. As a group again, start labeling these groups with a different colour post-it. Just put the group name on top of the grouping.Step 5: Now re-arrange your groups in order of time from left to right. Put the group post-it at the top and the tasks below the group, but still in order left to right.Overall comments:Your second user story map!Reminder:The groups are called “User Activities” – this is the backbone of your applicationThe items below are called “User Tasks” – this is the walking skeleton of your applicationNotice how fast you were able to create a reasonable outline for your whole application?Keep this map as we will be adding to it shortly. At this point we have no user stories.
In your user story map you should probably have a “Compose Email” or “Create Email” user task under the “Email Management” user activity or something similar. (if not, then what kind of e-mail have you been using?)We’re going to create the stories that go under that User Activity.Step 1: Generate tasksSplit up into groups of 3 to 5As individuals, think about creating an e-mail and write one user story (just the title, don’t worry about the rest) on each post-it. Slice each story thinly.Again, have everyone in your group use the same colour post-it for this exercise but use a different colour than the ones you have used so far.Step 2: Read them outHave each person read their post-its out loud to the group and then place them in the middle of the table so that you can see all the post-its at once.Again:Notice the similarities between your post-its and other peoples. Notice also that if you missed a few things, somebody else came up with the missing tasks. Step 3: GroupNow as a group, and without talking, move the post-its that are similar to each other closer to each other, and those that are not similar, move them farther apart. Those that are exact duplicates you can eliminate or put on top of each other.Step 4: PrioritizeInstead of naming our groups, this time we are just going to prioritize them top to bottom. The ones at the top will be created first and the others second.Think about the order that each piece would have to be built (again, reminder of the I in INVEST)If you are disagreeing about any story, feel free to split it again if you can.You can do this out loud.Overall comments:Again, notice how fast you were able to create a reasonable outline for your whole application? Has requirements gathering ever been this fast for you?You would repeat this for each activity and there are other requirements facilitation techniques to use like personas, scenarios, UX Design Studio, etc. These models are all inclusive models. They involve everyone and take advantage of all ideas without resorting to the trouble that is brainstorming or even writing down the correct interview questions in order to generate your high level scope and requirements.Do this with your customer!!!
Notice how if we turn this upside down it looks suspiciously like a user story map?
Notice how if we turn this upside down it looks suspiciously like a user story map?
Notice the similarities to Prune the Product Tree - #InnovationGames – the
Allows you to validate your architecture and solution early Allows users to see and test the whole application early Minimizes the affects of change to a feature Ensures important stories are built first Elicits improved feedback on the whole application early Allows you to deliver your application early Discourages "gold plating" It partners nicely with user story mapping (turn the diagram upside down and you have your story map)
Allows you to validate your architecture and solution early Allows users to see and test the whole application early Minimizes the affects of change to a feature Ensures important stories are built first Elicits improved feedback on the whole application early Allows you to deliver your application early Discourages "gold plating" It partners nicely with user story mapping (turn the diagram upside down and you have your story map)
As a group, choose 2 of the outcomesStep 1: Generate learnings.As individuals, write down 3 things you learned for each of the learning outcomes. One on each post-itStep 2: Read them outHave each person read their post-its out loud to the group and then place them in the middle of the table so that you can see all the post-its at once.Step 3: GroupNow as a group, and without talking, move the post-its that are similar to each other closer to each other, and those that are not similar, move them farther apart. Those that are exact duplicates you can eliminate or put on top of each other.Step 4: Name the groupsYou should now have some distinct groups. As a group again, start labeling these groups with a different colour post-it. Just put the group name on top of the grouping.Step 5: Put them up.Have one person in your group read the ‘group’ post-its and post them on the board with the individual post-its underneath.Your 3rd user story map!