Part 1: "Making Agile Work" Webinar Series: Inception

Post on 23-Jan-2015

943 views 1 download

description

David Draper, Head of Enablement at Valtech discusses why inception is important to set up your Agile project for success.

Transcript of Part 1: "Making Agile Work" Webinar Series: Inception

Setting an Agile Project up for Success

David Draper, Head of Enablement, Valtech UK

What is Inception

Our Approach

What do you get

inception takes an idea and elaborates it just enough

Just enough for what?

Rough project “shape” Who benefits? Who is impacted?

Rough costs

resisting analysis paralysis

up-front analysis causes

increased cost and unused

features

our fixed price

contracts drive

behaviour through

fear of change

the problem with requirements …

… most of them aren’t

Collaborative or Contractual?

“Let’s figure out together the best way to meet your goals”

“Tell us precisely what you want us to build”

Agile requirements principles

Focus on the goals of the stakeholders

Bring multiple perspectives together

Do not commit to details until necessary

What do our customers want?

Reduced time-to-market

Outcomes reached

Revenue protection

Revenue generation

Cost saving

Financial diligence

Our Approach

follow the

value

incremental

delivery

THE INCEPTION FRAMEWORK

KICK-OFF

PROBLEM ANALYSIS

SOLUTION DESIGN

SOLUTION DELIVERY PLANNING

CONCLUSION

VISION STATEMENT

PRAGMATIC PERSONAS

STAKEHOLDER ANALYSIS

LIKES & DISLIKES

PAIN POINTS

MINIMUM MARKETABLE FEATURES

MINIMUM VIABLE PRODUCT

USER STORIES

USER STORY MAPPING

UI WIREFRAMES

UI DESIGN

SYSTEM CONTEXT

CRITICAL SUCCESS FACTORS

TRADE-OFF SLIDERS

NON-FUNCTIONAL REQUIREMENTS

RELEASE THEMES

BUSINESS PROCESS ANALYSIS

VISION

For (target customer) Who (statement of the need or opportunity) The (product name) is a (product category) That (key benefit, compelling reason to buy) Unlike (primary competitive alternative) Our product (statement of primary

differentiation) taken from Geoffrey Moore’s book Crossing the Chasm

Personas

Market segmentation for dummies

MMFS

MINIMUM How small can a product be and still deliver benefit to someone? Benefit can be in the form of new information, a marketing demo or a new feature for end users

MARKETABLE Each increment should deliver recognisable value

FEATURES Some features cannot stand alone Others can be split

VISION

CRITICAL SUCCESS FACTORS

STAKEHOLDERS / ACTORS

MMF 1 MMF 2

ELABORATED

STORIES

HIGH LEVEL

STORIES

MMF 3

CANDIDATE ARCHITECTURE / UI WIRE FRAMES

What do you get?

Deliverables for you

Shared vision

Persona & stakeholder analysis

Roadmap

Release strategy

Product backlog

Technical architecture

UX / UI mock-ups

… and the option to have Valtech deliver it

Resource profile

Delivery approach

Adrid Assumptions, decisions, risks, issues, dependencies

Engagement model

Indicative pricing by stage

At what cost

2-3 weeks

Multi-skilled team Engagement manager Busness analyst Technical architect User experience consultant

Thank you