Design Sprint. A Practical Guidebook for Building Great Digital Products - Helion

ISBN: 978-14-919-2312-2
stron: 272, Format: ebook
Data wydania: 2015-09-28
Księgarnia: Helion
Cena książki: 109,65 zł (poprzednio: 127,50 zł)
Oszczędzasz: 14% (-17,85 zł)
With more than 500 new apps entering the market every day, what does it take to build a successful digital product? You can greatly reduce your risk of failure with design sprints, a process that enables your team to prototype and test a digital product idea within a week. This practical guide shows you exactly what a design sprint involves and how you can incorporate the process into your organization.
Design sprints not only let you test digital product ideas before you pour too many resources into a project, they also help everyone get on board—whether they’re team members, decision makers, or potential users. You’ll know within days whether a particular product idea is worth pursuing.
Design sprints enable you to:
- Clarify the problem at hand, and identify the needs of potential users
- Explore solutions through brainstorming and sketching exercises
- Distill your ideas into one or two solutions that you can test
- Prototype your solution and bring it to life
- Test the prototype with people who would use it
Osoby które kupowały "Design Sprint. A Practical Guidebook for Building Great Digital Products", wybierały także:
- Biologika Sukcesji Pokoleniowej. Sezon 3. Konflikty na terytorium 127,27 zł, (14,00 zł -89%)
- Windows Media Center. Domowe centrum rozrywki 66,67 zł, (8,00 zł -88%)
- Podręcznik startupu. Budowa wielkiej firmy krok po kroku 93,33 zł, (14,00 zł -85%)
- Ruby on Rails. Ćwiczenia 18,75 zł, (3,00 zł -84%)
- Scrum. O zwinnym zarz 77,78 zł, (14,00 zł -82%)
Spis treści
Design Sprint. A Practical Guidebook for Building Great Digital Products eBook -- spis treści
- Design Sprint: A Practical Guidebook for Building Great Digital Products
- Â
- Foreword
- Why Care About Design Sprints?
- This book is for you.
- Preface
- Who This Book Is For
- Who Are We to Tell You?
- How We Wrote This Book
- How This Book Is Organized
- Chapter 1, What Is a Design Sprint?
- Chapter 2, When (and When Not) to Do a Design Sprint
- Chapter 3, How to Approach Design Sprints
- Chapter 4, Before the Design Sprint: Make a Plan
- Chapter 5, Phase 1: Understand
- Chapter 6, Phase 2: Diverge
- Chapter 7, Phase 3: Converge
- Chapter 8, Phase 4: Prototype
- Chapter 9, Phase 5: Test
- Chapter 10, After the Design Sprint: Capture, Iterate, and Continue
- Acknowledgments
- I. The What, Why, and How of Design Sprints
- 1. What Is a Design Sprint?
- Uses of a Design Sprint
- At the beginning of a project
- In the middle of a project
- For a mature project
- How the Design Sprint Came to Be
- From Agile
- From design charrettes
- From digital product design
- From Google Ventures
- Created for Startups, Great for Enterprises
- For startups
- For enterprises
- Success = Time and Money Saved + Minds Blown
- Success by preventing failure
- When you get validation
- Some validation, some things to fix
- When you dont get validation
- Takeaways:
- Uses of a Design Sprint
- 2. When (and When Not) to Do a Design Sprint
- Why Do a Design Sprint?
- Speed, efficiency, and focus will increase
- To align a diverse team
- To have a clear process
- To start a new project in a clear direction
- When Not to Use a Design Sprint
- The product is already very well-defined
- Significant research is needed beyond the scope of 12 days of interviews
- The project is only a few days in scope
- The business opportunity isnt clear
- The scope is far too broad
- A more sophisticated product development effort is required
- You wont break up with your idea: The IKEA effect
- Takeaways:
- Why Do a Design Sprint?
- 3. How to Approach Design Sprints
- Whats the Best Application of Design Sprints?
- A wide variety of projects and people
- A framework for timeboxed activities
- The Ideal Design Sprint: Five Days
- A full design cycle in one week
- Alternative Approach #1: Compact It
- I cant give you five days. I can give you two.
- Alternative Approach #2: Shorten the Days
- I can give you five to six hours each day
- Beware of too short
- Alternative Approach #3: Spread It Out
- Lets do bite-sized chunks over four weeks.
- Alternative Approach #4: Ultra-Compact It: A Few Hours
- I can give you a few hours. What can we get done?
- Alternative Approach #5: Align with Your Teams Agile/Scrum
- My engineering team follows Agile, how can this work together?
- Match the design sprint length to the Scrum length
- Takeaways:
- Whats the Best Application of Design Sprints?
- 1. What Is a Design Sprint?
- II. How to Design Sprint
- 4. Before the Design Sprint: Make a Plan
- Determine the Timebox
- Construct the Agenda/s
- Set the Scope
- Pick a Facilitator
- What Makes a Good Facilitator?
- Recruit and Inform Team Members
- A small organization, such as a startup
- A team in a larger enterprise organization
- The studio, agency, or consulting model
- What Is the Difference Between Product Management and Project Management?
- Secure and Prepare the Space
- Stock Up on Supplies
- Whats in Your Sprint Kit?
- Conduct a Pre-Mortem
- Prepare and Distribute Background Materials
- Schedule Time with Users
- Post-it Note Pro Tip
- Takeaways:
- 5. Phase 1: Understand
- What Happens During the Understand Phase?
- Recommended Agenda
- Get the Background
- Get Inspired
- Define the Problem
- Know the User
- Wrap-up
- Get the Background
- Introductions
- How
- A Few of Our Favorite Icebreakers
- Introduce the Idea Parking Lot
- How
- Review Agenda
- How
- Rules of the Design Sprint
- Pitch Practice #1
- How
- Review Research and Past Work
- How
- Introductions
- Get Inspired
- Goals and Anti-Goals
- How
- Existing Product, Competitors, and Substitutes
- How
- Facts and Assumptions
- How
- Question Formulation Technique (QFT)
- How
- Context
- Goals and Anti-Goals
- Define the Problem
- Problem Statement
- How
- Reframe the Problem with Challenge Maps
- Challenge Maps
- How
- Problem Statement
- Know the User
- Who/Do
- How
- Personas
- How
- Discovery Interview
- How
- User Journey Map
- How
- Daily Retrospective (Plus/Delta)
- How
- Team Drinks: Less Filling and Tastes Great!
- How
- Who/Do
- Takeaways:
- 6. Phase 2: Diverge
- What Happens During the Diverge Phase?
- Recommended Agenda
- Gear Up
- Generate Solutions (At least once; 12 more times are optional)
- Generate More Solutions (Optional)
- Individual Wireframes (Optional)
- Wrap-up
- Gear Up
- Review Agenda and Rules
- How
- Background Phase Recap
- How
- Job Stories
- How
- Review Agenda and Rules
- Generate Solutions
- Mind Map
- How
- 8-Ups (AKA Crazy Eights)
- How
- Storyboard
- How
- Silent Critique
- How
- Group Critique
- How
- Super Vote (Optional)
- How
- Mind Map
- Generate More (and More) Solutions
- Individual Wireframes
- Wireframes
- How
- Takeaways:
- 7. Phase 3: Converge
- What Happens During the Converge Phase?
- Recommended Agenda
- Get Started
- Scrutinize Your Work
- Wireframe the Prototype
- Wrap-up
- Recommended Agenda
- Get Started
- Scrutinize Your Work
- $100 Test/Risks
- How
- Identify Alternatives
- How
- 2x2 Matrix (optional)
- How
- Review Assumptions
- How
- Wireframe the Prototype
- Team Sketching
- How
- Ritual Dissent
- How
- Repeat the Converge Cycle
- Final Sketch
- How
- Team Sketching
- Takeaways:
- What Happens During the Converge Phase?
- 8. Phase 4: Prototype
- What Happens During the Prototype Phase?
- Recommended Agenda
- Schedule and/or Confirm the Interviews
- Check Your Users Against the Target Persona
- Recruiting Test Takers: Where to Find People?
- Screen Out the Users Who Dont Fit
- Compensation: pay them something, even if it isnt money
- Build the Prototype
- What You Need
- Who Should Be Involved
- Review the Previous Days Work and Plan the Day
- Delegate and Assign Tasks
- Sketch First, Mock Up Later (Or Not)
- Make It
- A Word of Warning
- Prototyping Tools
- Examples of Prototypes
- Finalize the Test Plan
- Assumptions Table/Validation Board
- How
- Decide on the Pre-Roll Questions
- Define the Tasks
- Create the Post-Roll Questions
- Assumptions Table/Validation Board
- Takeaways
- 9. Phase 5: Test
- What Happens During the Test Phase?
- Recommended Agenda
- Test Your Prototype
- Tools for Testing
- The Testing Environment
- When Possible: Go to the Users
- It Happens: Someone Will Cancel
- Dont Coach Your Testers Through the Prototype
- Capture Artifacts
- User Test Interview
- How
- Debrief and Retrospective
- When It Works as Expected
- When Results Dont Match Your Expectations
- When You Still Have Questions
- Takeaways
- 10. After the Design Sprint: Capture, Iterate, and Continue
- What Happens Next?
- Capture and Document
- For the design firm
- For the product team within an organization
- Determine Next Steps
- Continue the Practice
- Make Design Sprints Commonplace
- Its in Your Hands
- Takeaways
- 4. Before the Design Sprint: Make a Plan
- A. Image Credits
- B. Oreilly: Design Sprint
- Index
- About the Authors
- Copyright