This document provides an overview of agile concepts and the Scrum framework. It defines key roles in Scrum like the Product Owner, Scrum Master, and Development Team. It also explains common agile ceremonies like sprint planning, daily standups, sprint reviews and retrospectives. The document emphasizes the importance of collaboration, adaptive planning, and valuing individuals over processes in agile development. It includes examples of how Scrum can be applied to plan a brochure development project in a series of short sprints.
The document outlines key roles and events in Scrum methodology:
The Product Owner represents stakeholders and manages the Product Backlog of requirements. The Scrum Master ensures the team follows Scrum process and removes impediments. The team works through Sprint cycles to deliver working software. Key events include Sprint Planning to commit to work, Daily Scrums for progress updates, and Retrospectives for process improvement.
Prioritization Techniques for Agile TeamsTarang Baxi
Have you ever been in a prioritization discussion where the only priorities are High, Higher, and Highest? Or tried using MoSCoW to prioritize user stories only to find
that 80% of the cards are 'Must Have'?
In this tutorial, we introduce a gamut of different prioritization methods, ranging from simple techniques like stacked ranking or MoSCoW that classify items along a single dimension to multi-dimensional techniques like priority quadrants, Story Maps, and Innovation Games®. We cover pruning feature trees, spending fake currency, and using visual metaphors, while truly identifying what the most important stuff really is. This was most recently presented at the Agile India 2013 conference in Bangalore.
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
A Multi-Team, Full-Cycle, Product-Oriented Scrum (Agile game) Simulation with LEGO Bricks. Based on the lego4scrum.com.
Lego4Scrum is teaching game is used by the Scrum trainers community worldwide including various certification classes, in-house trainings, formal business programs and team workshops.
The document describes the Design Sprint process, which allows teams to solve design problems and test ideas with customers in 2-5 days. The process involves 5 stages: 1) Understand the problem through research, 2) Diverge by generating many potential solutions through brainstorming techniques, 3) Converge by defining a prototype and assumptions to test, 4) Prototype quickly using paper or digital tools, and 5) Validate by testing the prototype with users and gathering feedback. Design Sprints use methods from Design Thinking to help teams break out of processes and focus on the user perspective to create innovative products.
This document outlines the process and activities for a design sprint to solve problems and validate ideas over 4 days. It involves expert interviews on Day 1 to understand problems and frame them as design challenges. Teams then generate ideas and concepts and vote on the most promising ones. On Day 2, they create storyboards and prototypes. On Day 3, they conduct user testing of prototypes. On Day 4, they test prototypes with 5-7 external users, collect feedback, and identify lessons to apply to the next sprint. The outcome is a working prototype with validated user testing and accelerated learning about what works and doesn't work.
A design sprint is a five-phase framework that helps answer critical business questions through rapid prototyping and user testing. Sprints let your team reach clearly defined goals and deliverables and gain key learnings, quickly. The process helps spark innovation, encourage user-centered thinking, align your team under a shared vision, and get you to product launch faster.
The sprint backlog is a list of tasks identified during sprint planning to complete user stories selected from the product backlog. It is commonly maintained as a spreadsheet containing the user story, tasks needed to complete it, and estimates of hours to complete each task. The sprint backlog is updated at least daily, such as during scrums, and used to track work remaining via a burn down chart.
Primer on Agile Project Management and SCRUMJoe Riego
The document provides an overview of Agile project management using Scrum. It discusses key Scrum concepts like iterative development, product backlogs, sprints, daily stand-ups, and burn downs. The document aims to explain how Scrum addresses scheduling, planning, estimating, and risk management compared to traditional project management approaches.
The document discusses the roles in Scrum, an agile software development methodology. It describes the three main roles: the Scrum Team which develops the software; the Product Owner who prioritizes features and represents customers; and the Scrum Master who leads the team and ensures they follow Scrum practices. The roles work together iteratively with the Scrum Team delivering working software increments each sprint while the Product Owner and Scrum Master provide feedback and guidance.
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)."
A design sprint is a 5-phase framework that helps teams answer critical business questions through rapid prototyping and user testing. The phases are: Map (understand the problem), Sketch (generate ideas), Decide (select the best concept), Prototype (build something testable), and Test (get user feedback). This process helps spark innovation, encourage user-centered design, align teams, and launch products faster. A key benefit is that it provides validated direction and user input to inform product development. Design sprints are best for when a team needs clarity on a new opportunity or is stuck on an issue.
This document provides a summary of the book "Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days" by Jake Knapp. It outlines the sprint process, which is a 5-day method for answering critical business questions through prototyping and testing ideas with customers. The process involves setting a challenge on Day 1, sketching potential solutions on Day 2, deciding on the top solution on Day 3, building a prototype on Day 4, and testing it with customers on Day 5 to learn key insights. The goal of the sprint is to help teams quickly solve problems and get feedback before committing significant resources.
Backlog refinement is not a Scrum event, but instead is an ongoing activity during the Sprint required to decompose, describe, estimate, and order backlog items in the Product Backlog.
This material is divided into two sections. The first section reviews the basics of backlog refinement, covering various options for conducting the activity. The second section covers tips for maintaining a healthy backlog and potential anti-patterns.
This material was presented at Agile New England in July and August 2022 as "101" introduction and "202" advanced sessions.
Validate Your Ideas Quickly with Google Design SprintBorrys Hasian
This was presented at Compfest, an annual one-stop IT event held by students of Faculty of Computer Science, University of Indonesia. The deck is about Design Thinking and Google Design Sprint.
A design sprint is a five-day process for taking a product or feature from design through prototyping and testing. It involves five steps: understand, diverge, decide, prototype, and validate. The goal is to get early feedback on ideas by conducting user research, rapidly generating concepts, building quick prototypes, and testing them with real users to learn what works and what doesn't work.
The document describes methods for conducting a design sprint, which is a framework for teams to solve design problems in 2-5 days. It discusses the typical stages of a design sprint: understand the problem, define strategies, diverge ideas, decide on ideas, prototype the selected ideas, and validate them with users. It provides examples of specific methods that can be used at each stage, such as conducting user interviews and lightning talks in the understand stage, creating user journeys and defining design principles in the define stage, and testing prototypes with users in the validate stage. The document is intended to help teams plan and facilitate effective design sprints.
Aubrey Smith, Sparked Advisory
In this training, we will build on the foundation established in Lean Startup 101 and 201 by delving into examples and cases of the Lean Startup concepts in action. Attendees of Lean Startup 301 will be exposed to cutting edge work from thought leaders and experts using Lean Startup in practice today — at startups and within the enterprise. Participation in this session is essential: You will be asked to help design an MVP and experiment to test critical Leap of Faith Assumption(s) in groups and will be encourage to share experiences. The session is designed to allow attendees to stretch their skills and to push one-another to ‘learn by doing’. The session will also include:
Sample cases and live interviews with practitioners highlighting the application of core concepts;
Exercises designed to bring the concepts to life and challenge participants to deepen their skills;
Discussion of advanced topics such organizational culture and governance as well as industry-specific concepts such as using Lean Startup in heavily regulated markets.
Thanks to Lean Startup Co.’s law firm, Orrick, for being the sponsor for this track.
Collaboration Les Cles Pour Lever Les Freins A L InnovationValtech
The document discusses collaboration as key to innovation in product development. It outlines the product development lifecycle including identifying customer needs, developing solutions, and launching/learning. It then details techniques for innovation including generating and evaluating ideas, rapid prototyping, and testing/iterating. An example of developing a "universality" shopping platform across brands is provided to illustrate applying these techniques. The presentation emphasizes customer collaboration, assumption-based evaluation of ideas, iterative testing to learn rather than prove ideas, and using results to prioritize and refine work.
Cox Automotive: Testing Across Multiple BrandsOptimizely
Cox Automotive, the world’s leader in automotive remarketing services, and parent company to such brands as Autotrader, Kelley Blue Book, Manheim, and Dealer.com, has more than 40,000 auto dealer clients across five continents.
Cox Auto focuses on continually improving its products to create faster vehicle transactions and enabling consumers to have a seamless online-to-offline experience. Testing has a natural space to play here - as Cox Automotive’s businesses have learned to scale experimentation to optimize the design of its digital experiences.
In this webinar, Frances Reyes, Seth Stuck, and Sabrina Ho will discuss how Cox Automotive is building a culture of experimentation and testing across their digital properties.
You’ll learn:
- The impetus of testing at Cox Automotive
- How they leverage and share information across their business units, creating shared goals despite different business priorities
- How they created a framework for data-driven decisions across the company
SaaSFest 2015: Accelerating Organic Growth Through High Tempo TestingSean Ellis
The key to sustainable growth is strong organic growth. These slides show you how to maximize organic growth. Then they should you how to pour fuel on the first through high tempo testing - outlining the team and process needed to executing testing at a high velocity.
Rapid turnaround usability testing: not just a pipe dreamKyle Soucy
This document describes a method for rapid-turnaround usability testing that allows product teams to get customer feedback more quickly without the time and expense of traditional usability testing. Key aspects of the method include conducting short usability tests with 1-3 participants over 3 days, improvising tasks based on interviews with participants, debriefing with the product team immediately after each test, and revising prototypes based on findings within 2 weeks to start the next iteration. The rapid approach aims to keep product teams and decision makers aligned through involvement in testing and debriefing, and provides quick feedback to guide design iterations.
Multi-team Release Planning, as it is often executed, fails to bring alignment beyond one-time inter-team coordination. This hands-on session teaches the techniques and exercises for a Product Wall Release Planning Workshop. The Product Wall Release Planning Workshop brings together all the elements of business needs, user experience, value proposition, dependency resolution, risk mitigation and user story planning. By combining various Agile collaboration techniques in a guided sequence, your multi-team Release Planning can create alignment through learning together and building together a clear path to success, from the release vision all the way to Sprint Backlogs.
Alan Dayley brings more than 25 years of software engineering experience to his Agile Coaching practice. Agile Coach, CSM, CSPO, CSP. Alan works to strengthen the people side of creative work. Alan loves to help people learn and create innovation in their life. Besides Agile coaching, he spreads this passion as a founding member of the Phoenix Scrum User Group and speaker coach for the Ignite Phoenix series of events.
This document introduces Experiment-Driven Development (EDD), which focuses on validating assumptions through experiments rather than adding features. The key aspects of EDD are identifying a product hypothesis and associated assumptions, running small experiments to test the highest priority assumptions, and using validated learnings to decide whether to pivot or persevere. An in-person simulation of a "Ball Point Game" is used to demonstrate how EDD principles can be applied through building, measuring, learning in short iterations, with the goal of developing the right product.
The document discusses the benefits of early testing in software development. It uses a dice product challenge exercise to demonstrate how misunderstandings can occur when requirements are not well understood. Without asking questions, the delivered product may not match what was intended. Early testing allows teams to identify assumptions and gaps. By questioning requirements upstream during design and development, testing can help ensure the final product meets expectations.
Test Improvement - Any place, anytime, any whereRuud Teunissen
Test Improvement is all about giving an organization or a team the “means they can use” to help achieve their goals. Means that are in line with their skills and they can use in their context. That’s why successful Test Improvement requires leadership and management. In this presentation I share experiences in Test Improvement in a wide variety of environments, using different models and approaches.
SaaSFest 2015 - "Scaling Authentic Growth" by Sean Ellis of GrowthHackersPrice Intelligently
Growth isn't a system of tactics; it's a specific framework and strategy within the heart of a business. Sean Ellis - CEO of GrowthHackers - walks through how he's built growth machines that have scaled business such as LogMeIn, Qualaroo, and GrowthHackers itself to millions in revenue.
Testing Across the Enterprise: How Cox Automotive Scales Experimentation to M...Optimizely
In today’s digital economy, consumers expect to buy everything online, even a purchase as significant as a car. Cox Automotive, parent company to brands including Autotrader and Kelley Blue Book, has more than 40,000 auto dealer clients across five continents, and is enabling them to keep up with consumer behavior and insights by implementing an enterprise wide experimentation program. Cox is bridging the gap between consumers, manufacturers, dealers, and lenders at every stage of the automotive experience.
In this session, you’ll hear how this multi-brand, international, matrixed organization has built an enterprise experimentation program that is flexible enough to adapt to various business models and modern-day demands for speed while maintaining testing best practices, r
Introduction to Design Thinking & Correlation to ScrumJeff ANGAMA
The document discusses how design thinking and agile frameworks like Scrum can be combined to deliver user-centered solutions. Some key points:
- Design thinking focuses on empathy, defining problems from the user's perspective, ideating solutions, prototyping, and testing iteratively.
- Scrum is an agile framework that uses sprints, daily stand-ups, backlogs and retrospectives for iterative delivery.
- Design thinking can be incorporated into Scrum through techniques like backlog grooming to understand user needs, prototyping solutions, and testing with users after each sprint.
- This approach ensures solutions are designed and delivered with a focus on the user experience through collaborative feedback loops.
WEBINAR: How to Set Up and Run Hypothesis Tests (ENCORE!)GoLeanSixSigma.com
The first live presentation of this webinar was so popular that we’re doing an encore presentation!
Join us for this 1-hour advanced webinar where we answer the question, “Why do we need hypothesis tests in process improvement?” and then stay with us as we walk you through a real, live hypothesis test direct from the Bahama Bistro!
Should you follow what others are doing ,just becuase it works for them?
Instead ,choose from Innovative models and Practices best suited to your business model.
#innovation #gartner #leanstartup #designthinking #agileleadership #leadershipexcellence #innovationstrategy #innovationleadership
This document discusses how experiment-driven product development works at Optimizely and best practices for organizations. It provides analysis of over 100,000 experiments from 1,000 companies to identify best practices. These include:
- Running thousands of small experiments continuously to learn and improve products.
- Using feature flags to limit risks when rolling out new features and conduct staged rollouts.
- Validating ideas with "painted door" experiments before building them out.
- Measuring business impacts through A/B testing and iterative adjustments.
Path to Agility: Avoiding Common Pitfalls in Agile AdoptionAgile Velocity
Why do 53% of all Agile projects ultimately fail? Navigating common pitfalls can be hard to do. Find out which five hurdles to Agile adoption are the most challenging and how to implement a plan of action to overcome them.
Discovery is an iterative process of reducing uncertainty. It's an essential part of how we do Product Development; routinely involving our customers in the act of deciding what we build, before we build it. Without discovery we increase the risk of building solutions that our customer won’t want, use or value. With discovery we maximise our chances of investing in ideas that are likely to succeed.
Caitlin shares with Product Anonymous how Seek have been working with Teresa Torres to improve their product management practice with continuous discovery + use of Opportunity tree's.
The document provides an overview of an Agile Project Management workshop being conducted by Abhishek Prasoon, Chief Scrum Master at Coforge. The workshop agenda includes introductions to Agile concepts, simulations of Scrum meetings like sprint planning, daily standups, demos and retrospectives. The goal is to help participants understand Scrum rituals and artifacts, roles and responsibilities, estimation techniques, and career opportunities in Agile project management.
Similar to Google Design Spint Fundamental Guide (20)
Love Problem Solution Expert +91 0000//0000 Call Now for Quick Solution Vashi...antxmodels60
Love Problem Solution Expert +91 0000//0000 Call Now for Quick Solution Vashikaran Specialist In Delhi
Website For Rent :- ranjeetsinginfo009@gmail.com
Call:- 000000000000
Whatsapp Now: 00000000000
Mastering Web Design: Essential Principles and Techniques for Modern WebsiteswebOdoctor Inc
Dive into the dynamic world of web design with our comprehensive guide that covers everything from foundational principles to advanced techniques. Whether you're a beginner looking to understand the basics or a seasoned designer aiming to refine your skills, this article offers invaluable insights. Explore topics such as responsive design, user experience (UX) optimization, color theory, typography essentials, and the latest trends shaping the digital landscape. Gain practical knowledge and actionable tips to create visually appealing, functional, and user-friendly websites that stand out in today's competitive online environment. Perfect for designers, developers, and anyone passionate about crafting compelling web experiences, this guide equips you with the tools needed to elevate your web design proficiency to new heights.
In human communication, explanations serve to increase understanding, overcome communication barriers, and build trust. They are, in most cases, dialogues. In computer science, AI explanations (“XAI”) map how an AI system expresses underlying logic, algorithmic processing, and data sources that make up its outputs. One-way communication.
How do we craft designs that "explain" concepts and respond to users’ intent? Can AI identify, elicit and apply relevant user contexts, to help us understand AI outputs? How do explanations become two-way?
We must create experiences with systems that will be required to respect user needs and dynamically explain logic and seek understanding. This is a significant challenge that, at its heart, needs UX leadership. The safety, trust, and understandability of systems we design hinge on the way we craft models for explanation.
Right Choice Landscaping offers exceptional villa landscape maintenance servi...rightchoicelandscapi
"Right Choice Landscaping offers exceptional villa landscape maintenance services in Dubai. Our dedicated team ensures that your villa’s outdoor spaces are beautifully maintained, enhancing both the aesthetic appeal and the value of your property. We offer landscaping and Garden design services to commercial property owners and homeowners all over the UAE.
MATKA GUESSING | SATTA GUESSING | MATKA BOSS OTG | INDIAN MATKA | INDIAN SATTA | INDIA MATKA | INDIA SATTA | MATKA | SATTA BATTA | DP BOSS | INDIA MATKA 786 | FIX FIX FIX SATTA NAMBER | FIX FIX FIX OPEN | MATKA BOSS 440
Satta Matka, Kalyan Matka, Satta , Matka, India Matka ,Satta Matka 420, Satta Matka Guessing, India Satta,Matka Jodi Fix ,Kalyan Satta Guessing, Fix Fix Fix SattaMATKA GUESSING | SATTA GUESSING | MATKA BOSS OTG | INDIAN MATKA | INDIAN SATTA | INDIA MATKA | INDIA SATTA | MATKA | SATTA BATTA | DP BOSS | INDIA MATKA 786 | FIX FIX FIX SATTA NAMBER | FIX FIX FIX OPEN | MATKA BOSS 440
Satta Matka, Kalyan Matka, Satta , Matka, India Matka ,Satta Matka 420, Satta Matka Guessing, India Satta,Matka Jodi Fix ,Kalyan Satta Guessing, Fix Fix Fix SattaMATKA GUESSING | SATTA GUESSING | MATKA BOSS OTG | INDIAN MATKA | INDIAN SATTA | INDIA MATKA | INDIA SATTA | MATKA | SATTA BATTA | DP BOSS | INDIA MATKA 786 | FIX FIX FIX SATTA NAMBER | FIX FIX FIX OPEN | MATKA BOSS 440
Satta Matka, Kalyan Matka, Satta , Matka, India Matka ,Satta Matka 420, Satta Matka Guessing, India Satta,Matka Jodi Fix ,Kalyan Satta Guessing, Fix Fix Fix Satta
Mastering the Art of Textures and Patterns in Interior Design.pdfFreixa Home Design
When it comes to enhancing your living space, interior design services play a crucial role in transforming mere rooms into personalized sanctuaries. From selecting the right textures and patterns to arranging furniture and accessories, interior design services encompass a broad spectrum of expertise aimed at creating harmonious and functional environments.
Exploring Writer's Studio Interior Design: A Prototype Case StudyAditi Sh.
This PowerPoint presentation delves into a comprehensive case study and prototype study of a Writer's Studio, focusing on understanding the psychology of the writer through the spaces they use. The study emphasizes the innovative concepts of flexibility and small space optimization tailored specifically for the creative process. By analyzing the spatial dynamics, ergonomic considerations, and aesthetic choices within the studio, the presentation aims to uncover how environment influences creativity and productivity. Through detailed examination and visual documentation, it explores various design strategies employed to enhance functionality without compromising on comfort and inspiration. This presentation is ideal for architects, interior designers, and anyone interested in the intersection of psychology, design, and creative workspaces. It offers insights into designing spaces that foster concentration, creativity, and overall well-being for individuals engaged in intensive writing and creative endeavors.
2. Vijf daagse pressure cooker waarin aan een challenge wordt gewerkt
door middel van vastgelegde stappen & doelstellingen.
Google Design Sprint?
Understand Diverge Converge Prototype Validate
1 2 3 4 5
3. Snelle methode om nieuwe mogelijkheden en verbeteringen te ontdekken & toetsen
voor reeds bestaande processen & producten
Waarom Google Design Sprints?
Innovatieve manier van werken waarbij “bedrijfs-silo’s” worden doorbroken en
problemen vanuit verschillende perspectieven worden bekeken.
Door betrokkenheid vanuit verschillende bedrijfstakken is steun voor uiteindelijke
toepassingen en of uitvoering van learnings groter
Innovatieve product development manier waarbinnen vijf dagen realistische
oplossingen en concepten worden bedacht
4. Voorbereiding
Set the stage
Een goede voorbereiding is key!
Samenstelling team
Bestaande uit:
beslisser, marketing,
service & techniek
Challenge statement
Duidelijke omschrijving
waar het team aan gaat
werken
Wat is er al?
Verzamel voor dat je
begint alle informatie
over de challenge
5. Voorbereiding
Set the stage
Een goede voorbereiding is key!
Samenstelling team
Bestaande uit:
beslisser, marketing,
service & techniek
Challenge statement
Duidelijke omschrijving
waar het team aan gaat
werken
Wat is er al?
Verzamel voor dat je
begint alle informatie
over de challenge
6. Challenge statement
First steps
• Interview key stakeholders
• Identify or review use cases
• Review all relevant user research
• Review current designs
Should be …
• Purposeful
• Concise and inspiring
• Targeted to users
• Aligned and timely
Create (what) (for whom) (by when) (in order to…).
Design a mobile app that helps a visitor plan and find the most
relevant, personalised and exiting activities to do in a city if the
visitor has only one day to for the visit.
7. Tijdens de sprint
Follow the proces
Wijk niet af van het proces, dat krijg je later in
de sprint anders terug.
Focus
100% aanwezigheid
& betrokkenheid
Timebox
Elke stap heeft een
vaste duur
Snacks
Zorg ervoor dat er
gezonde snacks zijn
8. Uitkomst
Possible outcomes
Wat leer je er van?
Optimization
Betere bestaande
processen
New concepts
De eerste stappen in
een nieuwe richting
Usabillity input
Een optimale
klantbeleving
11. The assumption board - Wherefor is it?
To collect assumptions during the proces regarding
the problem statement which have a great impact
on your prototype.
Understand Diverge Converge Prototype Validate
1 2 3 4 5
12. The assumption board
Assumption Validated ifTest with
Customers will
understand what we
do after they’ve seen
the landingspage
Interview
customers are
able to explain
what we do
Understand Diverge Converge Prototype Validate
1 2 3 4 5
13. The assumption board - When to use it?
Day 1: understand Day 3: decide Day 5: testDay 4: prototypeDay 2: define
Collect Test plan Validate
Understand Diverge Converge Prototype Validate
1 2 3 4 5
14. Review research
Understand Diverge Converge Prototype Validate
1 2 3 4 5
• Quickly identify existing research to determine what research
should be shared throughout the day (10 minutes)
• Define the business & the customer (1 hour)
• Define the problem, the value proposition, Success (1 hour)
• Lightning demos of any existing product or competitors sites (45
minutes)
19. Dag 2: Diverge
Understand Diverge Converge Prototype Validate
1 2 3 4 5
• Standup
• Value proposition
• Mind mapping
• UI elements
• Crazy eights
• Storyboard
• Group critique (Zen voting)
• Recap
20. Dag 2: Diverge
Understand Diverge Converge Prototype Validate
1 2 3 4 5
• Standup
• Value proposition
• Mind mapping
• UI elements
• Crazy eights
• Storyboard
• Group critique (Zen voting)
• Recap
21. Crazy eights!
Understand Diverge Converge Prototype Validate
1 2 3 4 5
Pak een a4
Vouw hem zo, dat je een
vel krijgt met 8 vlakken
Nu heb je 5 minuten
om 8 schetsen te maken
Challenge:
22. Dag 2: Diverge
Understand Diverge Converge Prototype Validate
1 2 3 4 5
• Standup
• Value proposition
• Mind mapping
• UI elements
• Crazy eights
• Storyboard
• Group critique (Zen voting)
• Recap
24. Dag 2: Diverge
Understand Diverge Converge Prototype Validate
1 2 3 4 5
• Standup
• Value proposition
• Mind mapping
• UI elements
• Crazy eights
• Storyboard
• Group critique (Zen voting)
• Recap
25. Dag 3: Converge
Understand Diverge Converge Prototype Validate
1 2 3 4 5
• Standup
• Identify conflicts
• Create assumption / test table
• Create testing plan
• Whiteboard the final storyboard
• Recap
26. Dag 3: Converge
Understand Diverge Converge Prototype Validate
1 2 3 4 5
• Standup
• Identify conflicts
• Create assumption / test table
• Create testing plan
• Whiteboard the final storyboard
• Recap
27. Identify conflicts - What is a conflict?
A conflict is a place where there are two or more
different approaches to solving the same problem.
Conflicting approaches are super helpful because
they illuminate the choices for your product.
Understand Diverge Converge Prototype Validate
1 2 3 4 5
28. Identify conflicts - The conflicts board
Product
page
Single
photo
Video
Diagrams
Sign up
Facebook
only
Email
Facebook &
E-mail
Onboarding
Overlay
tutorial
Wizard
Nothing
Problems
Approaches
29. Identify conflicts - Battle Royal or Best Shot
Battle Royale
Prototype several different approaches and test them against each other.
Takes more time since you have to make several prototype
Especially interesting for new spaces where there are not that many conventions
Best Shot
Go with a single approach which everybody agrees on is the best approach.
You can put a lot more time into one approach (or just finish it faster)
Understand Diverge Converge Prototype Validate
1 2 3 4 5
30. Identify conflicts - The conflicts board
Product
page
Single
photo
Video
Diagrams
Sign up
Facebook
only
Email
Facebook &
E-mail
Onboarding
Overlay
tutorial
Wizard
Nothing
31. Identify conflicts - The conflicts board
Product
page
Single
photo
Video
Diagrams
Sign up
Facebook
only
Email
Facebook &
E-mail
Onboarding
Overlay
tutorial
Wizard
Nothing
Battle
Royale
Best
Shot
32. Dag 3: Converge
Understand Diverge Converge Prototype Validate
1 2 3 4 5
• Standup
• Identify conflicts
• Create assumption / test table
• Create testing plan
• Whiteboard the final storyboard
• Recap
34. Dag 5: Validate
Understand Diverge Converge Prototype Validate
1 2 3 4 5
• Standup
• Interview & observe
• Decide on next steps
• Implentation plan
• Impact on IT
• Recap
35. Retrospective
• Looking Back – Fire and hot air: What helps us go higher?
What are the things that push us forward?
• – Looking Back – Forces pulling down: Which are the
forces pulling us down?
• – Looking Ahead – Storm: What is the storm ahead of us?
What will have our trip turbulenta?
• – Looking Ahead – Sunny day: What could we do to avoid
the storm and turn towards sunny days? What shall we do
to overcome the possible challenges ahead of us?