Agile Product Planning

Who Are You? - introduce yourself as if you were your product -

DevJam Agility

Agility in Practice

Where is the product planning?

Products Context Community Creating Community (Common Vision) Form Communities Composing Product Create an Eco-System (Chartering) (Personas - Story maps - Sketching) (Iteration 0 - Common Workspace) Discovery (Planning) Product Releases Iterative Delivery (Value - Effort - Dependencies) (Iterations (cycles) - Kanban (flow)) Delivery (Iterating) Staying Connected Tracking Progress Technical Agility Delivering Value (Daily Standup - Common Workspace) (Task Walls - Burncharts Visual Plans) (Continuous Integration - Test Driven) (Acceptance Tests - Continuous Deploy) Learning (Tuning) Validating Progress Reflect and Improve (Iteration Reviews - Users - User Testing) (Retrospective Market Feedback)

Who ( who are the composers? )

The Composers (by skill set) Informed (domain knowledge) Passionate (direction and vision) Decision Makers (product ownership) The Builders (dev test support)

Who are your composers? The informed (end users - domain experts) The passionate (product visionaries - sponsors) The deciders (product owners - investors) Who are they in your community? Sponsors / Investors Business Leads / Analysts UX / Interaction Designers Domain Experts / Users Developers / Testers Architects / Managers Support / Documentation

Products - Users - Use

Composition Tools 1) Why are you building? ( charter ) 2) Who is buying (in)? ( personas ) 3) What do they do? ( story maps ) 4) Which (to build) first? ( planning ) 5) When is there value? ( story tests )

Chartering ( why are you building? )

Chartering (a project story) Meet as a community to discuss: Elevator Pitch Goals - Success Measures Community Mapping Values - Working Agreements Strengths - Challenges Cadence

Telling a Project Story ( charter )

Elevator Pitch What are you building and why? ( keep it short and memorable )

Measurable Goals Project Charter: <name removed > / Time Frame: start of Q3 and end of Q4 Elevator Pitch: Less papers means less manual mistakes; build a new system with a sustainable process Goals Prove proposed technology - Move away from paper process Usable system to pilot - Validate the ability to have dynamic business rules Adapt to business and regulatory environment - Show value of iterative development Build confidence and buy in with business users - Fine tuning estimates (validate sizing) Have fun and learn (new knowledge) Value to Company Build efficiencies in field using technology - Shorter processing time with fewer errors Straight through efficiencies - Increase service level agreements with customer Increase business feedback Success Measures There is continuous feedback from business community Plans are reviewed and updated based on iteration outcome Community is improving on delivering on commitments and learning from each delivery Status of request on-line are viewable Business rules can change to manage work load

What Does Success Looks Like? - the blur is intentional -

Personas ( who is buying / buying in? )

Personas Are More Than Actors Personas represent people & clarify product value

Our Product - New POS ( simple charter ) Create a Point of Sale application 10 local stores Application runs only on registers Technology choices are made ( e.g. Java ) Another system provides item price & description

Who are the POS Personas?

Emergent Personas

Informative Personas

Creating Your Personas Choose a name ( sticky name alliteration helps ) ------------------------------------------------------------------------------------- Add an image ( a conversation starter ) ------------------------------------------------------------------------------------- Add a description Value from product ( who is this person? ) ( what is our sell? ) - time at job - financial benefit? - knowledge of domain - increased productivity? - FT / PT - fewer steps? - incentives - more fun? - level of engagement - easier to use?

Story Maps ( what is the user experience? )

Traditional Story Writing Session

Persona Driven Authoring

Story Mapping

Anatomy of a User Story The What User tasks Story The Completion Measures Tests User satisfaction / business value The How Design and coding work Tasks The Estimates Effort Consensus of effort to complete tasks Someone doing (or getting) something of value

Composition & Decomposition An Idea Someone s scheme / dream VISION A Product Story A way to talk about product value and use VALUE A Planning Story PRIORITY Balances business priorities w/ development costs An Iteration Story VALIDATION A testable unit of work for that can be estimated, built and demonstrated (used) to assess value

Story Jams

Creating Story Maps Name high level activities for persona ( what do you do at work? ) scenarios - business processes Walk a day in the life for each activity ( what are the tasks? ) user stories (user tasks) - sub processes Back up and re-tell the experience ( are there any variations? )

Mile wide - inch deep

Let s Map the Point of Sale Make Sales Open / Close Register Scan Add Item Calc Tax Calc Total Take Payment Print Receipt Take Returns Key In Item Take Cash Print GiftRcpt Take Credit Add Survey Take Coupon Take Check

Maps Guide Discussions

Maps Aid Planning

What are your story maps? Activity Task Task Task Task Task Task Task Task Activity Task Task Task Task Task Task Task Task Task Task Back up and find variations & dead ends

Mapping Variations

Other Delivery Work (backlog items ) Start up costs Environments Work ( nuke and pave ) Architectural Spikes Technical Debt Infrastructure Work Non Story Work Visual design Prototypes (paper and other) - Graphics