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.
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 Stories and User Story Mapping by Jason JonesAgile ME
There are two eternal challenges to Software Development Projects. One is that there are always more to build than we have time or resources to do. Always! The other is that all project problems ultimately comes down to poor communication. User Stories is really the promise of a conversation and User Story Mapping is a proven way of using Stories for doing release planning. Thus, this session will address both eternal challenges. The simplicity of the technique makes it a great starting point on the agile journey for most companies and will also help you improve the User Experience of your product. Join Andreas in an interactive session filled with hands on exercises that provides you with all the tools you need to start using User Story Maps at your work place.
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.
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 Stories and User Story Mapping by Jason JonesAgile ME
There are two eternal challenges to Software Development Projects. One is that there are always more to build than we have time or resources to do. Always! The other is that all project problems ultimately comes down to poor communication. User Stories is really the promise of a conversation and User Story Mapping is a proven way of using Stories for doing release planning. Thus, this session will address both eternal challenges. The simplicity of the technique makes it a great starting point on the agile journey for most companies and will also help you improve the User Experience of your product. Join Andreas in an interactive session filled with hands on exercises that provides you with all the tools you need to start using User Story Maps at your work place.
The Story Mapping Game (1st Conf, Melbourne, Australia, 3rd March 2017)Victoria Schiffer
The user story format is well known and used in many companies applying agile principles. However, teams often don’t know how a user story relates to other user stories and how they all fit into the bigger picture. Chipping away at seemingly random user stories that only define a specific feature can be the result. In an ideal world, you’d like teams to own and deliver on the shared vision and to keep the user’s journey and interest at heart. Creating and collaborating on user story maps as a team can make all the difference and lead to better products.
Come along to playfully learn how to create a story map in collaboration with your (workshop) team. It’s a fun way to come up with your team’s big picture story map, reflecting the user’s journey. This story map will inform your future delivery cycles and releases.
Having experienced the technique in a game setting will make it easier to remember, so that you can apply it in your own work places thereafter.
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)."
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.
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
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.
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.
La técnica de Story Mapping; desarrollada por Jeff Patton; permite un enfoque visual a la construcción del product backlog. Está técnica; en la cual las historias de usuario se organizan en un modelo bidimensional; en lugar de la clásica lista-sábana; ayuda a pensar al producto desde los procesos de negocio y las necesidades de los usuarios. Luego de la difusion y aceptacion que tuvo esta tecnica; se plantean las dudas de su aplicacion en un proyecto real. En esta sesion; se contara una experiancia real; aplicada en el mundo del desarrollo de software; demostrando la utilidad de la tecnica; sus ventajas; y como se realizo el salto de la teoria a la practica.
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.
Life cycle of user story: Outside-in agile product management & testing, or...Ravi Tadwalkar
It has always been my pleasure and fun to facilitate workshops for PM (product management) community at and outside Cisco, although this was first time I did a BDD workshop with PMs alone. And I realized today how PayPal has been a really great venue for SVPMA annual product camp "unconference" for 1k+ PMs with 550 waitlisted this year! I look forward to this event every year now...huge success!
Abstract:
As Product Owners and Managers are driving innovation thru' those fuzzy ideas in terms of scenarios, testers have always been thinking about those in form of test cases which take form of acceptance criteria for those scenarios. When you talk about those scenarios to your teams or even peers, you see those diverging ideas converging to something concrete.
That's how BDD helps you shape that idea. That fuzzy scenario, when validated thru' an engineering "spike", can be useful for product management MRD/PRD/use-case-models/stories...whatever it is that you want to use to drive product development.
And this is where Agile Tester role begins! So instead of doing top-down or bottoms-up product management & testing, try this outside-in approach. Go for it!
My workshop on BDD is about what I term as "Outside-in agile product management". To understand what I really mean by that, here is my slideshare presentation used rarely when teaching from the back of the class during this hyper-interactive workshop.
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
Learn to use the user story backlog as a way to describe user’s experience with your product.
Section 1: Importance of Product Owners Roll.
Identifying Scrum’s Product Owners roll.
Diagrammatic representation of PO Activities.
Diagrammatic representation of Product Feature Development tracks.
Section 2: User stories & Product Backlog Management.
Agile User Stories overview .
Acceptance Criteria.
Backlog Management.
Section 3: Project Scope, Product Backlog and Story Mapping.
User Story Mapping Steps.
Story Mapping example with valuable releases.
Benefits of User Story Mapping.
At the start of a project or start of a major release, we always face the problem of "How do we break down this big release into stories?" " How do I move from this vision to lower level details in user stories?". My workshop & presentation at the #India Agile Week 2013 Pune was focussed on providing answers to this. This presentation provides a way to move from high level vision to user stories using Story Map.
Become familiar with the User Story approach to formulating Product Backlog Items and how it can be implemented to improve the value and quality of the product by facilitating a user-centric approach to development
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.
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.
The Story Mapping Game (1st Conf, Melbourne, Australia, 3rd March 2017)Victoria Schiffer
The user story format is well known and used in many companies applying agile principles. However, teams often don’t know how a user story relates to other user stories and how they all fit into the bigger picture. Chipping away at seemingly random user stories that only define a specific feature can be the result. In an ideal world, you’d like teams to own and deliver on the shared vision and to keep the user’s journey and interest at heart. Creating and collaborating on user story maps as a team can make all the difference and lead to better products.
Come along to playfully learn how to create a story map in collaboration with your (workshop) team. It’s a fun way to come up with your team’s big picture story map, reflecting the user’s journey. This story map will inform your future delivery cycles and releases.
Having experienced the technique in a game setting will make it easier to remember, so that you can apply it in your own work places thereafter.
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)."
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.
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
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.
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.
La técnica de Story Mapping; desarrollada por Jeff Patton; permite un enfoque visual a la construcción del product backlog. Está técnica; en la cual las historias de usuario se organizan en un modelo bidimensional; en lugar de la clásica lista-sábana; ayuda a pensar al producto desde los procesos de negocio y las necesidades de los usuarios. Luego de la difusion y aceptacion que tuvo esta tecnica; se plantean las dudas de su aplicacion en un proyecto real. En esta sesion; se contara una experiancia real; aplicada en el mundo del desarrollo de software; demostrando la utilidad de la tecnica; sus ventajas; y como se realizo el salto de la teoria a la practica.
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.
Life cycle of user story: Outside-in agile product management & testing, or...Ravi Tadwalkar
It has always been my pleasure and fun to facilitate workshops for PM (product management) community at and outside Cisco, although this was first time I did a BDD workshop with PMs alone. And I realized today how PayPal has been a really great venue for SVPMA annual product camp "unconference" for 1k+ PMs with 550 waitlisted this year! I look forward to this event every year now...huge success!
Abstract:
As Product Owners and Managers are driving innovation thru' those fuzzy ideas in terms of scenarios, testers have always been thinking about those in form of test cases which take form of acceptance criteria for those scenarios. When you talk about those scenarios to your teams or even peers, you see those diverging ideas converging to something concrete.
That's how BDD helps you shape that idea. That fuzzy scenario, when validated thru' an engineering "spike", can be useful for product management MRD/PRD/use-case-models/stories...whatever it is that you want to use to drive product development.
And this is where Agile Tester role begins! So instead of doing top-down or bottoms-up product management & testing, try this outside-in approach. Go for it!
My workshop on BDD is about what I term as "Outside-in agile product management". To understand what I really mean by that, here is my slideshare presentation used rarely when teaching from the back of the class during this hyper-interactive workshop.
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
Learn to use the user story backlog as a way to describe user’s experience with your product.
Section 1: Importance of Product Owners Roll.
Identifying Scrum’s Product Owners roll.
Diagrammatic representation of PO Activities.
Diagrammatic representation of Product Feature Development tracks.
Section 2: User stories & Product Backlog Management.
Agile User Stories overview .
Acceptance Criteria.
Backlog Management.
Section 3: Project Scope, Product Backlog and Story Mapping.
User Story Mapping Steps.
Story Mapping example with valuable releases.
Benefits of User Story Mapping.
At the start of a project or start of a major release, we always face the problem of "How do we break down this big release into stories?" " How do I move from this vision to lower level details in user stories?". My workshop & presentation at the #India Agile Week 2013 Pune was focussed on providing answers to this. This presentation provides a way to move from high level vision to user stories using Story Map.
Become familiar with the User Story approach to formulating Product Backlog Items and how it can be implemented to improve the value and quality of the product by facilitating a user-centric approach to development
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.
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.
Product and UX - are the roles blurring?Jesse Gant
For most web-based companies, it appears that product managers have started to evolve their user experience (UX) skills in order to sell key concepts to developers, executives and even customers. On the flip side, UX folks contribute significant requirements and user stories in their design process and user research. So are the two roles becoming one? This covers the roles and why they are unique or not and even delves into the creation of annotated wireframes or prototypes instead of long-winded requirements docs - in an attempt to speed up the process to validate features and designs sooner rather than later with customers.
User Story Mapping Definitions & Basics - StoriesOnBoard.pdfStoriesOnBoard
User Story Mapping Definitions & Basics - by StoriesOnBoard
Learn more & start your 14-day free trial: https://storiesonboard.com/
- How to start story mapping
- Definitions
- Basics
- What is user story mapping?
- How do you conduct a story mapping session?
- What does a story map consist of?
- Who created story mapping?
- What is the lifecycle of story mapping?
- What is a user story workshop?
- Why is story mapping important?
- How do you make a story map?
- What is user story in Agile?
- How to write a good story?
- How do you use story mapping?
- User goals & steps in a narrative flow
- Who writes a user story?
- What is user persona on the story map?
- What are releases?
- How to brainstorm user stories?
- Why is prioritization crucial while working with user stories?
- How to convert a story map into conventional product backlog?
- What is MVP release?
- What is the difference between epics and user stories?
StoriesOnBoard is a visual and collaborative story mapping tool to prioritize the customer value sprint by sprint.
Build your story map on StoriesOnBoard.com
Why your product team should use User Story Mapping to link user research to ...John Murray
How well do you think your product team takes what they learn from their users and puts it into the next iteration of the product? How well does your team come to a common understanding of what the next iteration of the product will look like and then build a product that reflects that common understanding?
These two problems — improving your product with user research and effective team collaboration — can both be solved with a design tool called User Story Mapping.
In this session, attendees will hear how to apply User Story Mapping to connect user research to user stories for Design Thinking and Agile Development and the experience our teams have with the method. Attendees will get a taste of going through running a simple user story mapping workshop so that they will feel comfortable taking the process back to their business.
Why your product team should use User Story Mapping to link user research to ...UXPA International
How well do you think your product team takes what they learn from their users and puts it into the next iteration of the product? How well does your team come to a common understanding of what the next iteration of the product will look like and then build a product that reflects that common understanding?
These two problems — improving your product with user research and effective team collaboration — can both be solved with a design tool called User Story Mapping.
In this session, attendees will hear how to apply User Story Mapping to connect user research to user stories for Design Thinking and Agile Development and the experience our teams have with the method. Attendees will get a taste of going through running a simple user story mapping workshop so that they will feel comfortable taking the process back to their business.
It's told that if you don't like a cat you just don't know how to cook it. It's the same if we're talking about estimating and prioritizing user stories. This time we will back to unfinished the subject about bad examples of user stories and the stuff which one don't know how to treat as the user story. We will talk about which role, when and how work with user story and cover the main principles of user stories (no)estimations.
Subjects:
- What is and what is not a user story?
- Who, when and why — roles and ceremonies.
- To estimate or not to estimate?
- Case studies/practice
Agile Network India | Effective User story writing and story mapping approachAgileNetwork
Session Title: Effective User story writing and story mapping approach
Abstract:Get a high-level view is story mapping, how to create features and epics, release planning and key concepts to understand how stories work and how they come to life in Agile a story’s lifecycle. Example of effective Agile scrum User story.
Key Takeaways:
1. Learn how to convert this to working software.
2. User story vs Use Case
3. Flat backlog vs story map
4. Technical vs functional stories
5. Creating stories collaboratively.
From Use to User Interface- This 3-4 hour tutorial describes a practical approach to translating the goals users would like to achieve and the tasks they wish to accomplish into user interface designs that effectively support those goals and tasks.
Why should you use User Stories? What is specification by example?
What is a valid role (As a...)
This presentation covers some of the concepts and uses of user stories
The quality of a User Experience can be measured by using "time" as a measurable dimension. Spikes in an "expedited" task/time analysis can place the spotlight of problems areas in UI, general cognition and usability.
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 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.
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.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
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.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
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
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.
4. About Me Agilist and team member at Protegra in Winnipeg (It says “Application Architect” on my business card) Founder of Winnipeg Agile User Group @srogalsky http://winnipegagilist.blogspot.com
5. Learning Outcomes Demonstrate the ability to create a User Story Map (You’ll create three) Explain what a user story is (and isn’t) Demonstrate the ability to slice user stories in your map Describe the benefits of User Story Mapping Explain the difference between iterative and incremental and how that relates to User Story Mapping
7. What User Stories are not Tasks Create user table Create password encryption service Create login service Create CSS Create page template Add login button Outcome: Explain what a user story is (and isn’t)
8. 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. Outcome: Explain what a user story is (and isn’t)
9. 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 Outcome: Explain what a user story is (and isn’t)
10. 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 Outcome: Explain what a user story is (and isn’t)
11. What User Stories are… A small piece of functionality that provides some value to a user As a user, I want to login with my password, so that I can gain access to the site. “A place holder for a conversation.” Outcome: Explain what a user story is (and isn’t)
12. What User Stories are… I Independent * N Negotiable (can be prioritized) V Valuable (to a user) E Estimable S Small T Testable Outcome: Explain what a user story is (and isn’t)
13. Formats By the book: As a [role], I want to [some action], so that [goal] As a [user] I want to [login with my pwd] so that [I can gain access to the site] Outcome: Explain what a user story is (and isn’t)
14. Formats Who What Why As a [user] I want to [login with my pwd] so that [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 Outcome: Explain what a user story is (and isn’t)
15. Formats Title; Sentence; Acceptance Tests Title: Login w/ pwd Login w/ password and show welcome page Test upper, lower, numbers, special characters, accents, spaces Test mandatory lengths Test invalid pwds Outcome: Explain what a user story is (and isn’t)
16. Formats Lean Startup: Feature [X] will move Metric [Y] Feature [show sad face before logging off] will move Metric [time spent logged into the site] Outcome: Explain what a user story is (and isn’t)
20. Why slice? User Story Slices go here: Outcome: Demonstrate the ability to slice user stories in your map
21. How not to Slice? Outcome: Demonstrate the ability to slice user stories in your map Tasks Create user table Create password encryption service Create login service Create CSS Create page template Add login button
22. How to Slice? By screen (for basic screens only) By button By group of fields By workflow step Optional workflow steps Validation Error handling * Admin functions (maintaining drop downs, etc) By priority By applying the INVEST model By acceptance criteria By option By role By Subjective quality (never by objective quality: always be defect free) By value Outcome: Demonstrate the ability to slice user stories in your map
23. 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 Outcome: Demonstrate the ability to slice user stories in your map
24. Outcome: Demonstrate the ability to slice user stories in your map Take the Purplecards and re-sort them
25. Outcome: Demonstrate the ability to create a User Story Map User Activities User Tasks User Stories
37. Outcome: Describe the benefits of User Story Mapping Take the Greencards and re-sort them
38. Iterative 1 2 3 4 5 Incremental Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping Credit: Jeff Patton
39. Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping
40. Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping
41. Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping
42. Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping
43. Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping
44. Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping
45. Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping
46. Iterative vs. Incremental Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping
47. Iterative Advantages Validate your architecture and solution early See and test the whole application early Encourages important stories to be built first Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping
48. Iterative Advantages Elicits improved feedback on the whole application early Deliver your application early as early as possible Discourages "gold plating" Helps contain scope Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping
49. 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 Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping
50. Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping Take the Pinkcards and re-sort them
51. Our Final Map As a table, choose 2 of the outcomes Outcome: Demonstrate the ability to create a User Story Map Demonstrate the ability to create a User Story Map Explain what a user story is (and isn’t) Demonstrate the ability to slice user stories in your map Describe the benefits of User Story Mapping Explain the difference between iterative and incremental and how that relates to User Story Mapping
52. Questions? THANKS! Contact Info steve.rogalsky@protegra.com @srogalsky winnipegagilist.blogspot.com http://www.slideshare.net/SteveRogalsky/?????/
Editor's Notes
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.
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?
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!