valtech - agile inception : how to start an agile project ?

OBJECTIVES!

By attending this Webinar you will learn: •  Why do we need Inception for Agile projects? •  How to understand stakeholder and user needs •  How to work breadth first •  How to satisfy your organisations needs for budget and scope certainty without sacrificing Agility

SETTING AN AGILE PROJECT UP FOR SUCCESS!

DAVID DRAPER // HEAD OF ENABLEMENT // VALTECH UK

How do you embark on a new project?

Ò  WHAT IS INCEPTION?

Ò  OUR APPROACH

Ò  TOOLBOX

Ò  OUTPUTS

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

FIXED PRICE CONTRACTS DRIVE BEHAVIOUR THROUGH FEAR OF CHANGE!

COLLABORATIVE OR CONTRACTUAL?!

“LET’S FIGURE OUT TOGETHER THE BEST WAY TO MEET YOUR GOALS”

“TELL US PRECISELY WHAT YOU WANT US TO BUILD”

THE PROBLEM WITH REQUIREMENTS …

… MOST OF THEM AREN’T!

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!

EVERY PROJECT IS DIFFERENT!

Ò Usability

Ò Technology Up-lift

Ò Social platform

Ò Commerce

Ò Integration

17

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

TOOLBOX

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

STAKEHOLDERS!

Ò  Who cares?

Ò  Permission giver Ò  Interested party Ò  Information source

Ò  What makes them tick?

23

PERSONAS!

Ò  MARKET SEGMENTATION FOR DUMMIES

25!

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

WIREFRAMES!

Ò  Engage stakeholders with interactive mock ups

Ò  Long term and short term view

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?

OUTPUTS!

Ò SHARED VISION Ò ENGAGED STAKEHOLDERS Ò PERSONA 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