Building Better Products, June 2015

Post on 11-Aug-2015

426 views 4 download

Tags:

Transcript of Building Better Products, June 2015

Building better ProductsJason Fraser jafraser@pivotal.io

@jfraser (twitter)

June, 2015

at Pivotal Labs

@jfraser

@jfraser

@jfraser

Keep in touch!

@jfraser

@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?

@jfraser

@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.

@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

@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

@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

@jfraser

How do you approach a typical project?

Analysis

Plan

Stakeholders

Feedback

Revise

Budget

Approval

Execute

Measure

@jfraser

Why Simplicity?

healthcare.gov

@jfraser

XP at Pivotal Labs

Team Focused

Honest

Predictive rather than Prescriptive

Test Driven

Iterative

@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

@jfraser

XP is Team Focused

@jfraser

Team Size

• Communicative overhead

• Social loafing

• Bystander Effect

@jfraser

Communicative overhead

Shake Hands!

@jfraser

Communicative overhead

Person 1

Person 2 Person 3

@jfraser

Communicative overhead

Person 1

Person 2 Person 3

Person 4

@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

@jfraser

Communicative overhead

n(n-1)/2

@jfraser

Bystander Effect

2014 novemberstudios

@jfraser

Bystander Effect

@jfraser

Social Loafing

Eric Skiff

@jfraser

Team Size

@jfraser

A Pivotal Labs Team

@jfraser

Pair Programming

@jfraser

Benefits of working as a Pair

• Team Continuity

• Reduced Errors

• Faster, more elegant solutions

• No handoff

@jfraser

XP at Pivotal Labs

Team Focused

Honest

Predictive rather than Prescriptive

Test Driven

Iterative

@jfraser

XP is Honest

Team Focused

Honest

Predictive rather than Prescriptive

Test Driven

Iterative

@jfraser

No Rockstars

ego

@jfraser

XP at Pivotal Labs

Team Focused

Honest

Predictive rather than Prescriptive

Test Driven

Iterative

@jfraser

Predicting Progress

Team Focused

Honest

Predictive rather than Prescriptive

Test Driven

Iterative

@jfraser

XP at Pivotal Labs

Team Focused

Honest

Predictive rather than Prescriptive

Test Driven

Iterative

@jfraser

Test Driven Development

Write the test first

Write the code

Test until you pass

Deploy

@jfraser

XP at Pivotal Labs

Team Focused

Honest

Predictive rather than Prescriptive

Test Driven

Iterative

@jfraser

Iterations not Sprints

No sprints

Commitment on Time, not Scope

Focus on Customer Value

Continuous Deployment

@jfraser

Product Management for XP

Team Focused

Honest

Predictive rather than Prescriptive

Test Driven

Iterative

@jfraser

Product Owner

Dev

Dev

Dev

Dev

DevDev

Dev}Business Design

Marketing Etc.

“Traditional” Product Management

@jfraser

UX

& D

esig

nDev & Eng

blah blah blah

PRODUCT IDEAS

Biz/PM

Pivotal Labs Product Management

@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

@jfraser

Using Pivotal Tracker

@jfraser

Units of Customer Value

@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

@jfraser

What does it all mean?

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

@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

Thank you!

@jfraser