12th Prod.Active Meetup“Building a product within a large

scale organization”Alexis Grizos

The landscape

Internal Stakeholders

External Stakeholders

More Stakeholders

Customers

Business needs

CompetitionRevenue

Goals

Politics

Where to begin?

The product What are we building?

The stakeholders Who should we keep satisfied?

Target audience Who is our client?

Time to market How fast do we want to ship it?

Costs What’s the available budget?

Tools & resources How should we built it?

SCOPE

Analysing the scope Product scope: Features and functions that characterizes the

product (ROADMAP)

Project scope: Work that must be done to deliver the product (DEPENDENCIES)

Project scope

Product scope

The “How”

The “What”

A list called backlog Define your product (self service, sales channel)

Choose a framework to finalize roadmap

Prioritize everything and circulate the list to the right persons

Plan of Opportunity

Plan of Intent

Plan of RecordFinal

Roadmap

Know everyone in the organization Map every single stakeholder

Get the decision makers on your side by serving their needs

Whether you like it or not you job description includes a 40% of your daily work to be consumed by “non productive” activities

Learning to say NO can be miraculous sometimes..

Stakeholder diagrams help

Onion ring style

Matrix style

Know your customer When designing a product work always with profiles/personas

Beware of large volumes, they intent to maximize the tiniest of your defects

Build customer centric products

Leverage brand assets

Plan and plan again Eisenhower once said “Plans are nothing, planning is

everything”

Commit to Plans, they will save you when things will get nasty

Find your MVP and adopt release launching

When is the right time to ship it? Depending on the product usually a soft launch is needed

Work on your promotional plan (include internal/external)

Internal distribution as friendly user testing is not the right way to go

Leverage ATL activities

Budgeting SECURE the budget

Leverage business needs

Learn to negotiate CRs

Use the right tools A task/project management tool is highly needed (e.g IRA,

Easy Redmine, Basecamp, Slack, Trello)

Select a p/m approach and stick to it

A meeting to rule them all

Secure resources

Plan how to deal with technical debt (basically DON’T leave)

Learning to walk“A journey of a thousand miles

begins with a single step”Lao Tzu

The vision

You don’t start from scratch, there is always something to begin with.

Best app in class

From self care to digital sales

Boost adoption and engagement

The plan Working Agile for the first time

2 major releases

Enhance roadmap along the way

3 month time window

Deliver all customer journeys prior to development

Specs – The Holy Grail

Define screens (graphics)

Define functionalities

Define interactions

Define gestures/animations

Define web services (where needed)

Define testing process (CAT-UAT)

Customer journeys

Establish ground rules KPIs is a bomb that keeps us

together

½ Agile framework (daily standups retrospectives) +meetings with major stakeholders

Have internal releases (e2e development) every 3 weeks

What happened during the journey Agile or maybe Fragile Immature

agile teams when not following the framework can cause chaos

Changing scope constantly will lead to destruction

Planning realistically is a weapon

Delegating work can save the day

Operational & day2day involvement is out of the question

Where is the test data?

Take aways

Select a process/approach that everyone is familiar with (especially the technical teams)

Accept politics and adaptA highly talented Project Manager

is a must have Scripta manentDon’t underestimate testing

Thank you

Alexis Grizos