building better products, june 2015

47
Building better Products Jason Fraser [email protected] @jfraser (twitter) June, 2015 at Pivotal Labs

Upload: jason-fraser

Post on 11-Aug-2015

426 views

Category:

Internet


4 download

TRANSCRIPT

Page 1: Building Better Products, June 2015

Building better ProductsJason Fraser [email protected]

@jfraser (twitter)

June, 2015

at Pivotal Labs

Page 2: Building Better Products, June 2015

@jfraser

Page 3: Building Better Products, June 2015

@jfraser

Page 4: Building Better Products, June 2015

@jfraser

Keep in touch!

@jfraser

Page 5: Building Better Products, June 2015

@jfraser

Innovation at Pivotal

Pivotal Innovation Workshops ask clients to explore and validate fundamental product questions:

Who is the Customer?

What Problem are we solving for them?

Is it a problem that’s Worth Solving?

Is our Solution the right solution?

Is there a Market?

Does market Scalability matter?

Is the Business Model well thought out?

Page 6: Building Better Products, June 2015

@jfraser

Page 7: Building Better Products, June 2015

@jfraser

Why Agile?

“Thinking big is not at odds with starting small.”

Eric Ries, Author - The Lean Startup

“The most successful project leaders from government and

industry alike tend to deliver top-shelf stuff with a skeleton crew,

a shoestring budget, and a cannonball schedule.”

Dan Ward, Author - F.I.R.E.

Page 8: Building Better Products, June 2015

@jfraser

The Agile Manifesto

Individuals and Interactions over Processes and Tools

Working Software over Comprehensive documentation

Customer Collaboration over Contract Negotiation

Responding to Change over Following a Plan

Page 9: Building Better Products, June 2015

@jfraser

Extreme Programming

How little can we do and still build great software?

Increase OPTIONS for business decisions

Recover quickly from missteps

Communication, Simplicity, Feedback, and Courage

Page 10: Building Better Products, June 2015

@jfraser

Why Simplicity?

!In discussing healthcare.gov, Larry Allen, president of Allen Federal Business Partners and a 24-year federal IT professional, called Accenture “a very solid firm” and said that all major contractors have some problems, because large IT projects are so complex. !“I think their error rate is pretty consistent with other large firms,’’ Allen said. “Does that excuse things they did wrong? No, but it does put it into context.’’

Washington Post, Feb 9, 2014

Page 11: Building Better Products, June 2015

@jfraser

How do you approach a typical project?

Analysis

Plan

Stakeholders

Feedback

Revise

Budget

Approval

Execute

Measure

Page 12: Building Better Products, June 2015

@jfraser

Why Simplicity?

healthcare.gov

Page 13: Building Better Products, June 2015

@jfraser

XP at Pivotal Labs

Team Focused

Honest

Predictive rather than Prescriptive

Test Driven

Iterative

Page 14: Building Better Products, June 2015

@jfraser

Obligatory Joke

How many safety directors does it take to change a lightbulb?

Five. One to change it and four to hold the ladder

Page 15: Building Better Products, June 2015

@jfraser

XP is Team Focused

Page 16: Building Better Products, June 2015

@jfraser

Team Size

• Communicative overhead

• Social loafing

• Bystander Effect

Page 17: Building Better Products, June 2015

@jfraser

Communicative overhead

Shake Hands!

Page 18: Building Better Products, June 2015

@jfraser

Communicative overhead

Person 1

Person 2 Person 3

Page 19: Building Better Products, June 2015

@jfraser

Communicative overhead

Person 1

Person 2 Person 3

Person 4

Page 20: Building Better Products, June 2015

@jfraser

Communicative overhead

• Understanding happens between pairs

• People stop talking when they feel understood

• Decisions are made when people agree to stop talking

• Too many pairs slows everything down

Page 21: Building Better Products, June 2015

@jfraser

Communicative overhead

n(n-1)/2

Page 22: Building Better Products, June 2015

@jfraser

Bystander Effect

2014 novemberstudios

Page 23: Building Better Products, June 2015

@jfraser

Bystander Effect

Page 24: Building Better Products, June 2015

@jfraser

Social Loafing

Eric Skiff

Page 25: Building Better Products, June 2015

@jfraser

Team Size

Page 26: Building Better Products, June 2015

@jfraser

A Pivotal Labs Team

Page 27: Building Better Products, June 2015

@jfraser

Pair Programming

Page 28: Building Better Products, June 2015

@jfraser

Benefits of working as a Pair

• Team Continuity

• Reduced Errors

• Faster, more elegant solutions

• No handoff

Page 29: Building Better Products, June 2015

@jfraser

XP at Pivotal Labs

Team Focused

Honest

Predictive rather than Prescriptive

Test Driven

Iterative

Page 30: Building Better Products, June 2015

@jfraser

XP is Honest

Team Focused

Honest

Predictive rather than Prescriptive

Test Driven

Iterative

Page 31: Building Better Products, June 2015

@jfraser

No Rockstars

ego

Page 32: Building Better Products, June 2015

@jfraser

XP at Pivotal Labs

Team Focused

Honest

Predictive rather than Prescriptive

Test Driven

Iterative

Page 33: Building Better Products, June 2015

@jfraser

Predicting Progress

Team Focused

Honest

Predictive rather than Prescriptive

Test Driven

Iterative

Page 34: Building Better Products, June 2015

@jfraser

XP at Pivotal Labs

Team Focused

Honest

Predictive rather than Prescriptive

Test Driven

Iterative

Page 35: Building Better Products, June 2015

@jfraser

Test Driven Development

Write the test first

Write the code

Test until you pass

Deploy

Page 36: Building Better Products, June 2015

@jfraser

XP at Pivotal Labs

Team Focused

Honest

Predictive rather than Prescriptive

Test Driven

Iterative

Page 37: Building Better Products, June 2015

@jfraser

Iterations not Sprints

No sprints

Commitment on Time, not Scope

Focus on Customer Value

Continuous Deployment

Page 38: Building Better Products, June 2015

@jfraser

Product Management for XP

Team Focused

Honest

Predictive rather than Prescriptive

Test Driven

Iterative

Page 39: Building Better Products, June 2015

@jfraser

Product Owner

Dev

Dev

Dev

Dev

DevDev

Dev}Business Design

Marketing Etc.

“Traditional” Product Management

Page 40: Building Better Products, June 2015

@jfraser

UX

& D

esig

nDev & Eng

blah blah blah

PRODUCT IDEAS

Biz/PM

Pivotal Labs Product Management

Page 41: Building Better Products, June 2015

@jfraser

Pivotal Labs Product Managers:

Create the specification as the project moves forward

Prioritize highest customer value first

Work directly with the developers planning iterations based on highest customer value and balanced by predictive workload (velocity and scoring)

Manage both project risk and product risk

Work with the client to refine the product vision on the fly

Page 42: Building Better Products, June 2015

@jfraser

Using Pivotal Tracker

Page 43: Building Better Products, June 2015

@jfraser

Units of Customer Value

Page 44: Building Better Products, June 2015

@jfraser

Pivotal Labs Product Managers:

Create the specification as the project moves forward

Prioritize highest customer value first

Work directly with the developers planning iterations based on highest customer value and balanced by predictive workload (velocity and scoring)

Manage both project risk and product risk

Work with the client to refine the product vision on the fly

Page 45: Building Better Products, June 2015

@jfraser

What does it all mean?

We can build rock-solid software quickly and reliably with very little interpersonal drama.

Page 46: Building Better Products, June 2015

@jfraser

Leveling up

“The courage to speak truths, pleasant or unpleasant, fosters communication and trust. !“The courage to discard failing solutions and seek new ones encourages simplicity. !“The courage to seek real, concrete answers creates feedback.”

—Kent Beck

Page 47: Building Better Products, June 2015

Thank you!

@jfraser