my stories aren’t long enough… · 2019-07-28 · 1.stable, whole teams tied to customer value...

18
My Stories Aren’t Long Enough… Rich Mironov For Synerzip 23 July 2019

Upload: others

Post on 05-Jun-2020

1 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

My Stories Aren’t Long Enough…

Rich MironovFor Synerzip23 July 2019

Page 2: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

• Software product management (1988+)• Mentor/coach product leaders• “Smokejumper” VP Product

• Blogger (2002+), founded Product Camp• Agile development (2005+)• Outcomes >> process

About Rich Mironov

@Synerzip @RichMironov

THE A

RT OF PRO

DUC

T MA

NA

GEM

ENT Rich M

ironov

THE ART OFPRODUCT MANAGEMENTL E S S O N S F R O M A S I L I C O N VA L L E Y I N N O VA T O R

Rich MironovCEO, Mironov Consulting

“Rich is a thought leader among technology practitioners. He balances practical experience with systematic insights into how products are built and what makes start-ups successful. This book captures the wisdom he has accumulated, along with considerable scar tissue.”

Henry Chesbrough, author of Open Innovation and professor at UC Berkeley’s Haas School of Business

The Art of Product Management takes us inside the head of a product management thought leader. With color and humor, Rich Mironov gives us a taste of Silicon Valley’s tireless pursuit of great technology and its creation of new products. He provides strategic advice about start-ups and big organizations, how to think like a customer, and what things should cost—while reminding us to love our products and our teams. The Art of Product Management brings together the best insights from more than seven years of Product Bytes.

“This book is for everyone who needs to understand how customers think and companies work. Don’t plan your next product until you’ve read these real-life lessons.”

Steve Westly, CEO of The Westly Group and former California State Controller

“The Art of Product Management is a true resource for product management and market-ing problem solving. This book should be on every product professional’s desk.”

David Taber, CEO of SalesLogistix

“Like a master filmmaker, Rich sheds a soft light on the sometimes harsh realities of prod-uct management, bringing a rare moment of entertainment to those of us solving hard problems for our customers.”

Luke Hohmann, CEO of Enthiosys

“I’ve trained thousands of product management professionals over the last 12 years at Pragmatic Marketing and have recommended Product Bytes to seminar attendees since it began in 2002. Each article hits a product management pain point and gives specific tips or tools to solve it”

Steve Johnson, VP, Pragmatic Marketing andauthor of The Strategic Role of Product Management

“In my 15 years working with technology companies, Rich is the ONLY product guy I’ve ever found who truly understands the processes, people, and politics behind creating products. This book should be required reading for every product manager in Silicon Valley!”

Andrea Corney, President, Acorn Consulting

“Any aspiring or experienced product manager can use Rich’s collection as an illuminat-ing set of career mile-markers.”

Steven Haines, President of Sequent Learning Networks and author of The Product Manager’s Desk Reference

Mironov ConsultingSan Francisco, CA 94102 www.mironov.com

US $21.95

2160647814399

ISBN 978-1-4392-1606-490000 >

Page 3: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

“All of my user stories need more detail, more context, clearer success metrics.”And…“My stories are too prescriptive, too focused on HOW, don’t give team room to creatively solve from a good WHAT statement.”

What’s happening?

What My Development Team Told Me

@Synerzip @RichMironov

Page 4: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

“What users say they want is often not what they actually

want -- or what’s good for them.”

-Rich Mironov

@Synerzip @RichMironov

Page 5: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

• Most customer requests are poorly framed or incorrect• Internal process suggestions often superficial• “Doing what we’re told to do” rarely delivers desired

outcomes• Product managers must understand context, unpack

issues, correctly frame problems, share with team• Development team should solve creatively

Symptoms or Root Causes?

@Synerzip @RichMironov

Page 6: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

@Synerzip @RichMironov

Page 7: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

1. Stable, whole teams tied to customer value streams2. Product manager and team learn directly from end users (not proxies)3. Whole team works on problems as well as solutions4. Automated test suite, everyone writes tests5. Objectives are end user behavioral changes (not delivery dates)6. Frequent process retrospectives and experiments:

team picks tools and processes that fit situation7. Trust

Rich’s Markers for Strong Agile Organizations

@Synerzip @RichMironov

Page 8: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

“Something I’ve noticed about great product teams. They actually talk about the stuff that didn’t work. The misses. The surprises. What they learned. How that informed future decisions...the antithesis of success theater.”

John Cutler, Product Evangelist, Amplitude

@Synerzip @RichMironov

Page 9: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

• “Card” (or Post-It note): a physical token giving tangible and durable form to what would otherwise only be an abstraction

• “Conversation” is largely verbal but usually supplemented by documentation

• “Confirmation” that we’ve met objectives/delivered value/passed acceptance criteria

After Ron Jeffries

Three C’s Are About Team Communication

@Synerzip @RichMironov

Page 10: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

I took my team through a retrospective exercise:• Which stories are too long? Why?

What do they have in common?• Which stories are too short? Why?

What do they have in common?Realization: different kinds of storiesmay need different artifacts

Back To Our User Story Problem…

@Synerzip @RichMironov

Page 11: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

Likely Artifacts

My Team’s Story Piles (Yours Will Vary)

@Synerzip @RichMironov

Story Group

UX/UI-heavy workflow changes

Performance, scalability, infrastructureLightweight bug fixesValidation, experiments,research

Refactoring, tech debt

Artwork, branding

Behavioral goals, story boards, journey maps, unlikely paths, usability testing… my team wanted more detail

Internal metrics, technical hypotheses, team may write most stories… less detailSteps to reproduce… less framing

Clear learning goal, least code (or no code!) to test assumptions… more contextTeam-chosen, internally-focused improvement with no end user impact… less detailImplement pixel-perfect rendering… exact specs

Page 12: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

These Might Look Like...

@Synerzip @RichMironov

Data retrieval bug:àEnter invalid dateàLeave Acct# blankàClick “update”àUI returns 404

Concierge validation test• Add “rebalance your

stock portfolio” button• When clicked, show “Will

be rebalanced tonight”• Route via email to Ops

for manual rebalancingThreshold: 0.5% of users

4x Faster Bootup:

Series of architect-

led performance ideas

Until fast enough…

• team picks, prototypes

• if big improvement,

push to production

Diminishing returns?

Page 13: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

• No universal agile process: user stories are (just) a tool• Dig deep for root issues within superficial complaints• “Do what I tell you” wastes half of team’s talent

and most of their enthusiasm• Focus on outcomes and concrete value, not velocity • Start and finish what’s really most important (WIP)• Whole team engagement, retrospectives, experiments

Agile Product / User Story Takeaways

@Synerzip @RichMironov

Page 14: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

Rich Mironov

Mironov ConsultingSan Francisco, CA, [email protected]@richmironov

Page 15: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

Your Agile Software Co-development Partner 1. Accelerate delivery of your

product/technology roadmap2. Address technology skills gap in

your inhouse team3. Save >50% with India based

software development talent4. Leverage US based professionals

to make it easy for your inhouseteam to collaborate

15

Page 16: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

Representative Clients - 14+ Years

…150+ more

Page 17: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

Upcoming WebinarAgile2019 Conference Top 10 Takeaways

Thursday August 29, 2019@ 11am ET | 10am CT | 8am PT

Presenters:

Vinayak Joglekar, CTOFlorence Lowe, COO

Mike Watson, VP Engineering@ Synerzip

Page 18: My Stories Aren’t Long Enough… · 2019-07-28 · 1.Stable, whole teams tied to customer value streams 2.Product manager and team learn directly from end users (not proxies) 3.Whole

TEXAS | SILICON VALLEY | INDIA