Muutke küpsiste eelistusi

E-raamat: User Story Mapping: Discover the Whole Story, Build the Right Product

4.20/5 (6689 hinnangut Goodreads-ist)
  • Formaat: 324 pages
  • Ilmumisaeg: 05-Sep-2014
  • Kirjastus: O'Reilly Media
  • Keel: eng
  • ISBN-13: 9781491904862
Teised raamatud teemal:
  • Formaat - EPUB+DRM
  • Hind: 28,07 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Lisa ostukorvi
  • Lisa soovinimekirja
  • See e-raamat on mõeldud ainult isiklikuks kasutamiseks. E-raamatuid ei saa tagastada.
  • Formaat: 324 pages
  • Ilmumisaeg: 05-Sep-2014
  • Kirjastus: O'Reilly Media
  • Keel: eng
  • ISBN-13: 9781491904862
Teised raamatud teemal:

DRM piirangud

  • Kopeerimine (copy/paste):

    ei ole lubatud

  • Printimine:

    ei ole lubatud

  • Kasutamine:

    Digitaalõiguste kaitse (DRM)
    Kirjastus on väljastanud selle e-raamatu krüpteeritud kujul, mis tähendab, et selle lugemiseks peate installeerima spetsiaalse tarkvara. Samuti peate looma endale  Adobe ID Rohkem infot siin. E-raamatut saab lugeda 1 kasutaja ning alla laadida kuni 6'de seadmesse (kõik autoriseeritud sama Adobe ID-ga).

    Vajalik tarkvara
    Mobiilsetes seadmetes (telefon või tahvelarvuti) lugemiseks peate installeerima selle tasuta rakenduse: PocketBook Reader (iOS / Android)

    PC või Mac seadmes lugemiseks peate installima Adobe Digital Editionsi (Seeon tasuta rakendus spetsiaalselt e-raamatute lugemiseks. Seda ei tohi segamini ajada Adober Reader'iga, mis tõenäoliselt on juba teie arvutisse installeeritud )

    Seda e-raamatut ei saa lugeda Amazon Kindle's. 

User story mapping is a valuable tool for software development, once you understand why and how to use it. This insightful book examines how this often misunderstood technique can help your team stay focused on users and their needs without getting lost in the enthusiasm for individual product features.

Author Jeff Patton shows you how changeable story maps enable your team to hold better conversations about the project throughout the development process. Your team will learn to come away with a shared understanding of what you’re attempting to build and why.

  • Get a high-level view of story mapping, with an exercise to learn key concepts quickly
  • Understand how stories really work, and how they come to life in Agile and Lean projects
  • Dive into a story’s lifecycle, starting with opportunities and moving deeper into discovery
  • Prepare your stories, pay attention while they’re built, and learn from those you convert to working software
Foreword xi
Martin Fowler
Foreword xiii
Alan Cooper
Foreword xvii
Marty Cagan
Preface xxi
Read This First xxix
1 The Big Picture
1(20)
The "A" Word
1(2)
Telling Stories, Not Writing Stories
3(1)
Telling the Whole Story
3(2)
Gary and the Tragedy of the Flat Backlog
5(1)
Talk and Doc
6(2)
Frame Your Idea
8(1)
Describe Your Customers and Users
9(1)
Tell Your Users' Stories
10(4)
Explore Details and Options
14(7)
2 Plan to Build Less
21(16)
Mapping Helps Big Groups Build Shared Understanding
22(3)
Mapping Helps You Spot Holes in Your Story
25(1)
There's Always Too Much
26(1)
Slice Out a Minimum Viable Product Release
27(1)
Slice Out a Release Roadmap
28(1)
Don't Prioritize Features---Prioritize Outcomes
29(1)
This Is Magic---Really, It Is
30(2)
Why We Argue So Much About MVP
32(2)
The New MVP Isn't a Product at All!
34(3)
3 Plan to Learn Faster
37(14)
Start by Discussing Your Opportunity
38(1)
Validate the Problem
39(1)
Prototype to Learn
40(1)
Watch Out for What People Say They Want
41(1)
Build to Learn
41(3)
Iterate Until Viable
44(1)
How to Do It the Wrong Way
44(2)
Validated Learning
46(2)
Really Minimize Your Experiments
48(1)
Let's Recap
48(3)
4 Plan to Finish on Time
51(16)
Tell It to the Team
52(1)
The Secret to Good Estimation
53(1)
Plan to Build Piece by Piece
54(2)
Don't Release Each Slice
56(1)
The Other Secret to Good Estimation
56(1)
Manage Your Budget
57(5)
What Would da Vinci Do?
59(3)
Iterative AND Incremental
62(1)
Opening-, Mid-, and Endgame Strategy
63(1)
Slice Out Your Development Strategy in a Map
64(1)
It's All About Risk
64(1)
Now What?
65(2)
5 You Already Know How
67(22)
1 Write Out Your Story a Step at a Time
67(4)
Tasks Are What We Do
68(1)
My Tasks Are Different Than Yours
69(1)
I'm Just More Detail-Oriented
70(1)
2 Organize Your Story
71(1)
Fill in Missing Details
72(1)
3 Explore Alternative Stories
72(3)
Keep the Flow
74(1)
4 Distill Your Map to Make a Backbone
75(1)
5 Slice Out Tasks That Help You Reach a Specific Outcome
76(13)
That's It! You've Learned All the Important Concepts
77(1)
Do Try This at Home, or at Work
78(1)
It's a Now Map, Not a Later Map
79(2)
Try This for Real
81(1)
With Software It's Harder
82(2)
The Map Is Just the Beginning
84(5)
6 The Real Story About Stories
89(8)
Kent's Disruptively Simple Idea
89(2)
Simple Isn't Easy
91(1)
Ron Jeffries and the 3 Cs
92(3)
1 Card
93(1)
2 Conversation
93(1)
3 Confirmation
94(1)
Words and Pictures
95(1)
That's It
96(1)
7 Telling Better Stories
97(12)
Connextra's Cool Template
97(5)
Template Zombies and the Snowplow
102(2)
A Checklist of What to Really Talk About
104(3)
Create Vacation Photos
107(1)
It's a Lot to Worry About
108(1)
8 It's Not All on the Card
109(12)
Different People, Different Conversations
109(1)
We're Gonna Need a Bigger Card
110(3)
Radiators and Ice Boxes
113(3)
That's Not What That Tool Is For
116(5)
Building Shared Understanding
116(2)
Remembering
118(1)
Tracking
119(2)
9 The Card Is Just the Beginning
121(10)
Construct with a Clear Picture in Your Head
122(1)
Build an Oral Tradition of Storytelling
123(1)
Inspect the Results of Your Work
124(2)
It's Not for You
126(1)
Build to Learn
127(1)
It's Not Always Software
128(1)
Plan to Learn, and Learn to Plan
129(2)
10 Bake Stories Like Cake
131(6)
Create a Recipe
132(1)
Breaking Down a Big Cake
133(4)
11 Rock Breaking
137(18)
Size Always Matters
137(2)
Stories Are Like Rocks
139(1)
Epics Are Big Rocks Sometimes Used to Hit People
140(2)
Themes Organize Groups of Stories
142(1)
Forget Those Terms and Focus on Storytelling
142(1)
Start with Opportunities
143(1)
Discover a Minimum Viable Solution
144(2)
Dive into the Details of Each Story During Delivery
146(2)
Keep Talking as You Build
148(1)
Evaluate Each Piece
149(1)
Evaluate with Users and Customers
150(2)
Evaluate with Business Stakeholders
152(1)
Release and Keep Evaluating
153(2)
12 Rock Breakers
155(12)
Valuable-Usable-Feasible
156(2)
A Discovery Team Needs Lots of Others to Succeed
158(1)
The Three Amigos
159(4)
Product Owner as Producer
163(1)
This Is Complicated
164(3)
13 Start with Opportunities
167(14)
Have Conversations About Opportunities
167(1)
Dig Deeper, Trash It, or Think About It
168(5)
Opportunity Shouldn't Be a Euphemism
173(1)
Story Mapping and Opportunities
173(6)
Be Picky
179(2)
14 Using Discovery to Build Shared Understanding
181(20)
Discovery Isn't About Building Software
181(1)
Four Essential Steps to Discovery
182(17)
1 Frame the Idea
183(1)
2 Understand Customers and Users
183(3)
3 Envision Your Solution
186(10)
4 Minimize and Plan
196(3)
Discovery Activities, Discussions, and Artifacts
199(1)
Discovery Is for Building Shared Understanding
200(1)
15 Using Discovery for Validated Learning
201(16)
We're Wrong Most of the Time
201(2)
The Bad Old Days
203(1)
Empathize, Focus, Ideate, Prototype, Test
204(4)
How to Mess Up a Good Thing
208(1)
Short Validated Learning Loops
209(1)
How Lean Startup Thinking Changes Product Design
210(5)
Start by Guessing
211(1)
Name Your Risky Assumptions
212(1)
Design and Build a Small Test
212(2)
Measure by Running Your Test with Customers and Users
214(1)
Rethink Your Solution and Your Assumptions
215(1)
Stories and Story Maps?
215(2)
16 Refine, Define, and Build
217(22)
Cards, Conversation, More Cards, More Conversations...
217(1)
Cutting and Polishing
218(1)
Workshopping Stories
218(4)
Sprint or Iteration Planning?
222(3)
Crowds Don't Collaborate
225(2)
Split and Thin
227(5)
Use Your Story Map During Delivery
232(1)
Use a Map to Visualize Progress
233(1)
Use Simple Maps During Story Workshops
234(5)
17 Stories Are Actually Like Asteroids
239(8)
Reassembling Broken Rocks
241(2)
Don't Overdo the Mapping
243(1)
Don't Sweat the Small Stuff
244(3)
18 Learn from Everything You Build
247(12)
Review as a Team
247(4)
Review with Others in Your Organization
251(2)
Enough
253(1)
Learn from Users
254(1)
Learn from Release to Users
255(1)
Outcomes on a Schedule
255(1)
Use a Map to Evaluate Release Readiness
256(3)
The End, or Is It? 259(2)
Acknowledgments 261(4)
References 265(2)
Index 267
Jeff makes use of over 15 years experience with a wide variety of products from on-line aircraft parts ordering to electronic medical records to help organizations improve the way they work. Where many development processes focus on delivery speed and efficiency, Jeff balances those concerns with the need for building products that deliver exceptional value and marketplace success. Jeff has focused on Agile approaches since working on an early Extreme Programming team in 2000. In particular he specializes in integrating effective user experience design and product management practice with strong engineering practice.Jeff currently works as an independent consultant, agile process coach, product design process coach, and instructor. Current articles, essays, and presentations on variety of topics in Agile product development can be found at www.AgileProductDesign.com and in Alistair Cockburn's Crystal Clear. Jeff is founder and list moderator of the agile-usability Yahoo discussion group, a columnist with StickyMinds.com and IEEE Software, a Certified Scrum Trainer, and winner of the Agile Alliance's 2007 Gordon Pask Award for contributions to Agile Development.