Product Development

Process
Chapter 5 — From idea to market: frameworks, methodologies, and tools that
drive successful launches

PRODUCT MANAGEMENT CHAPTER 5

Chapter Objectives

What You'll Learn

1 2

Agile Methodologies Goals & Objectives

Apply agile frameworks to real product development Produce clear, actionable product goals
scenarios

3 4

MVP Strategy Prototyping

Develop Minimum Viable Product features Practice iterative design in modern development
What Is the Product
Development Process?
A structured framework guiding products from ideation → market — reducing
risk, optimizing resources, and maximizing launch success.

Ideation
Generate and evaluate concepts

Design & Build

Prototype and develop features

Test & Refine

Validate with real users

Launch
Commercialize the product
 PART 1

Agile Product Development

Flexible, iterative, and customer-driven approaches to building products that meet real market needs
What Makes Agile Different?

Agile methodologies prioritize flexibility,

collaboration, and continuous feedback
over rigid upfront planning.

Iterative Progress Customer Feedback Cross-Team Collaboration

Build in short cycles, learn fast Continuously adapt to user needs Diverse skills working toward one
goal
5 Key Principles of Agile

Iterative Development Customer Collaboration Adaptive Planning

2–4 week sprints: plan, build, test, review Continuous feedback shapes the product Revisit plans as requirements evolve

Cross-Functional Teams Sustainable Pace

Developers, designers, analysts — together Consistent rhythm prevents burnout
Principle 1

Iterative Development

Work is organized into short cycles

(sprints) of 2–4 weeks, each producing a
testable increment of the product.

Plan Build Test Review

Define sprint goals Develop features Validate outcomes Learn and repeat

Example: Voyager Innovations uses sprints to enhance Maya — each cycle targets specific features like transaction security
or new payment options.
Principle 2

Customer Collaboration

Continuous User Engagement

Products evolve based on actual user
needs, not assumptions. Feedback is
gathered at every stage.

Example: Mynt (GCash) regularly

engages users to test new
features, ensuring a more intuitive
payment experience before full
launch.
Principle 3

Flexible & Adaptive Planning

Plans Are Living Documents

Teams revisit and adjust plans based on
real-time data, ensuring alignment with
current market conditions.

Example: Globe Telecom adjusts

network expansion plans based
on live usage data — prioritizing
infrastructure upgrades where
demand spikes.
Principle 4

Cross-Functional Teams
Developers
Technical build

UX Designers
User experience

Data Analysts
Performance insights

Marketers
Go-to-market strategy

Example: Lazada Philippines uses cross-functional teams to address

technical, UX, and market considerations simultaneously.
Principle 5

Sustainable Pace
Consistent Rhythm, No Burnout
High-performing teams require balance —
not endless crunch. Sustainable pace
ensures long-term innovation quality.

Avoid excessive overtime

Regular team-building activities
Consistent output without sacrificing
quality

Example: Jollibee protects its

culinary teams from burnout,
maintaining high standards for
new menu innovation.
Agile in Practice: Three Methodologies

1 2 3

Scrum Kanban Lean

Sprint-based framework with structured Visual workflow management for Eliminate waste, maximize value at
roles and ceremonies continuous delivery every step
Scrum
A time-boxed Agile framework organizing work into 2–4 week sprints with
structured planning, review, and reflection cycles.
Scrum: Key Components
01 02 03

Product Backlog Sprint Planning Daily Stand-ups

Prioritized list of features, enhancements, Team selects backlog items to tackle in the Short daily syncs on progress, plans, and
and bug fixes upcoming sprint blockers

04 05

Sprint Review Sprint Retrospective

Demonstrate completed work to stakeholders Reflect and identify process improvements for next sprint

Example: Voyager Innovations (Maya) uses Scrum to rapidly respond to user requirements — sprint reviews drive continuous
feature delivery.
Kanban
Visualize. Limit. Flow.
Kanban emphasizes continuous delivery
without overwhelming the team — work is
pulled, not pushed.

Kanban Board — visualize workflow

To Do stages

WIP Limits — prevent bottlenecks

In Progress Pull System — team pulls tasks by
capacity
Review Continuous Delivery — ship features
steadily

Done

Example: Mynt (GCash) uses

Kanban to maintain steady
improvements to mobile
payments and financial
transactions.
Lean Product Development
Core idea: Maximize customer value while ruthlessly eliminating waste at
every stage of development.

Value Stream Mapping

Identify value-adding vs. wasteful activities

Just-In-Time
Produce only what's needed, when it's needed

Kaizen
Continuous incremental improvement

Empowered Teams
Authority to decide and improve processes

Example: Globe Telecom streamlined digital service development

using lean principles — reducing development time and maintaining
a competitive edge.
Agile Methodologies at a Glance

Scrum vs. Kanban vs. Lean

Each methodology serves different team needs — many

organizations blend elements of all three for maximum flexibility
and efficiency.

Scrum — best for projects with defined cycles

Kanban — best for continuous improvement
Lean — best for efficiency-focused teams
 PART 2

Minimum Viable Product

Launch fast, learn faster — the MVP strategy for validating ideas with minimal risk
What Is an MVP?
A Minimum Viable Product is the simplest version of a product that delivers
core value — launched early to gather real feedback and guide future
development.
The Four MVP Components

Early Launch
Core Features Release as soon as possible to real users
Only the essentials that solve the main user problem

Iterative Improvement
User Feedback Use feedback to add features and refine the product
Collect insights on needs, pain points, and preferences
Why Use an MVP?

Risk Reduction Customer-Centric

Limits investment in unproven ideas Product evolves based on real user needs

Faster Time-to-Market Resource Efficiency

Start generating revenue sooner Focus only on what matters most
MVP in Action

Philippine Companies: MVP Case Studies

[Link] Angkas Kumu

Launched MVP with basic Bitcoin buy/sell, Tested ride-hailing feasibility in Metro Started with live streaming and basic
bill pay, and load purchases — validated Manila with basic booking and fare social features — iterated based on
crypto adoption before scaling features before nationwide expansion engagement data and creator feedback
Case Study Deep Dive

[Link] MVP Journey

Core Features User

Bitcoin buy/sell, Feedback
bills, load Security, UX,
service gaps

Iterative
Early Launch Improve
Limited audience Cash-out, banks,
test more crypto

This MVP-driven approach allowed [Link] to quickly validate its business model and grow into a leading Philippine digital wallet
provider.
Case Study Deep Dive

Angkas: MVP to Scale

From Pilot to Platform

Core MVP: Basic ride-hailing, driver
registration, fare calculation
Early Launch: Metro Manila pilot only
Feedback: Safety, reliability, pricing
concerns
Improvements: Helmets, driver training,
cashless payments

Result: A popular transport alternative that

navigated regulatory hurdles through
continuous iteration.
Case Study Deep Dive

Kumu: Iterating for Engagement

Content-First Strategy
Core MVP: Live streaming, user
profiles, basic social features
Early Launch: Small user base for
engagement testing
Feedback: UI quality, content types,
feature requests
Improvements: Virtual gifting,
collaborative content, moderation tools

Result: Evolved into a diverse, interactive

platform tailored for Filipino content
culture.
Key Insight

MVP is not about shipping a broken product — it's about shipping the right product, learning fast, and building what users actually
need.

3
PH Companies
2–4
Week Sprints
↓
Risk Reduced
Validated business models via MVP Typical MVP iteration cycle length By launching before full investment
 PART 3

Prototyping & Iterative Design

Turning assumptions into insights — rapidly, cheaply, and continuously
What Is Prototyping?
Creating an early model of a product to explore ideas, validate assumptions,
and gather feedback — before committing to full development.
Low-Fidelity vs. High-Fidelity Prototypes
Low-Fidelity High-Fidelity
Simple, fast, cheap Detailed, interactive, realistic

Paper sketches Pixel-perfect mockups

Wireframes Clickable interactive models
Basic layout models Closely resembles final product
Focus: structure and flow Focus: appearance and functionality
5 Benefits of Prototyping

Early Validation
1
Test concepts before costly full-scale development

Cost Efficiency
2
Fix flaws early — changes are far cheaper before build

Enhanced Communication
3
Tangible models align stakeholders and teams

Risk Reduction
4
Identify technical and UX issues proactively

Iterative Improvement
5
Each version is better than the last
Benefit 1

Early Validation
Test Before You Build
Prototypes let users interact with a
preliminary version, surfacing usability
gaps before full development begins.

Validates core concept assumptions

Identifies interface and functionality
issues
Dramatically reduces launch risk

Example: GCash (Mynt)

prototypes new tools like loan
calculators with real users before
committing engineering
resources.
Benefit 2

Cost Efficiency
Fix Early, Save Big
The cost of change rises exponentially the
later it's discovered. Prototyping catches
errors when they're cheapest to fix.

Allocate resources to confirmed

priorities
Avoid over-engineering unused features
Prevent large-scale production
mistakes

Example: Jollibee tests new

menu prototypes in select
locations — refining recipes
before nationwide rollout saves
significant production costs.
Benefit 3

Enhanced Communication
Tangible prototypes give every stakeholder — developers, designers, investors,
users — a shared reference point, reducing misalignment and accelerating
consensus.

Example: Smart Communications uses prototypes to gather

feedback from marketing, technical, and user teams before any app
is fully built.
Benefit 4 & 5

Risk Reduction & Iterative Improvement

Risk Reduction Iterative Improvement
Uncover technical failures, compliance gaps, and market Each testing round informs the next version, producing a
acceptance issues before launch progressively better product

Example: EdTech startup discovers UI and module glitches in Example: Health tech startup streamlines telemedicine app
prototype testing — avoided a flawed launch. registration after repeated user testing cycles.
The Iterative Design Cycle

User Test

Prototype

Analyze

Refine

This cyclical process repeats until the product achieves the desired level of quality and user satisfaction — each loop producing a
stronger result.
Step 1

Prototype Creation
Build From What You Know
Develop an initial model based on current
requirements and understanding. Include
only the core features needed to gather
meaningful feedback.

Can be low- or high-fidelity

Core user flows must be represented
Sets the stage for user testing

Example: A Philippine e-
commerce startup prototypes
browsing, cart, and checkout
flows first.
Step 2

User Testing
Real Users, Real Insights
Observe real or representative users as
they interact with the prototype. Track task
completion, errors, and satisfaction.

Qualitative: what users like, dislike, find

confusing
Quantitative: completion rates, error
rates
Observe without leading — let behavior
speak

Example: The e-commerce

startup invites potential
customers to complete tasks like
searching for a product or
checking out.
Step 3

Analysis
Find the Patterns
Process feedback data to identify specific
pain points and improvement
opportunities. Prioritize by user impact.

Identify recurring issues across users

Rank by severity and frequency

Document findings for the dev team

Example: Users struggle with a

confusing checkout — the startup
documents this as a top-priority
fix for the next iteration.
Step 4

Refinement
Improve, Incrementally
Modify the prototype based on analysis.
Address the highest-priority issues first,
then test again. Change should be
incremental, not wholesale.

Simplify confusing flows

Add requested features selectively
Ensure each change is testable

Example: The e-commerce team

simplifies checkout steps, adds
clearer instructions, and improves
interface contrast.
Step 5

Repeat
The cycle continues — each round builds on the last, incorporating more
feedback and getting closer to a polished, user-validated product. Repeat until
quality and satisfaction targets are met.
3 Benefits of Iterative Design

User-Centric Flexibility Risk Mitigation

Users shape the product at every stage — Welcome change as a natural part of Detect and fix issues early before they
not just at launch development — not an obstacle become costly failures
Iterative Design: Philippine Examples

User-Centric: Globe Telecom

Designed for Filipino Users

Globe iterated their mobile app by starting
with basic features, then continuously
refining based on usage data and customer
service feedback.

Result: App adoption rates improved as the

experience aligned more closely with the
specific needs of Filipino consumers.
Iterative Design: Philippine Examples

Flexibility: Lazada Philippines

Staying Competitive Through

Iteration
Lazada regularly releases updates based
on user behavior and market trends —
treating the platform as a living product
that never stops improving.

Frequent feature releases

Real-time user feedback loops

Rapid response to competitive shifts
Iterative Design: Philippine Examples

Risk Mitigation: Angkas

Before expanding to new cities, Angkas piloted in Metro Manila — gathering
feedback on app UX, safety protocols, and pricing. Each new city launch
benefited from prior learnings, reducing regulatory and operational risk.
Case Study

Jollibee: Prototyping New Menu Items

Low-Fidelity

Simple recipes and basic plating

concepts

High-Fidelity
Refined dishes with final ingredients
and presentation

User Testing
Taste tests and customer feedback in
select locations

Refinement
Recipes adjusted based on
preferences and standards

Jollibee's iterative approach ensures every new menu item is market-validated before nationwide rollout — protecting brand quality and
reducing waste.
Case Study

Smart Communications: App Development

From Beta to Best-in-Class
01

Low & High-Fidelity Prototypes

Wireframes → interactive app mockups
02

Beta User Testing

Usability tests with real customer
segments

03

Analysis & Refinement

Fix usability issues, incorporate feature
requests

04

Repeat Until Seamless

Cycle continues to meet quality standards
Case Study

MMDA: Traffic Management System

Public-Sector Iterative Design
MMDA applied prototyping to its traffic
management tools — testing with both
traffic enforcers and commuters before
full deployment.

Low-Fi: System maps and interface

sketches
High-Fi: Real-time traffic data
visualizations
Testing: Field trials with enforcers and
the public
Result: Improved flow data accuracy
and commuter UX
Prototyping vs. Iterative Design
Prototyping and iterative design are complementary tools —
prototyping creates the model, while iterative design defines the
process of continuously improving it through user feedback
loops.

Prototyping answers: "Does this work?"

Iterative design answers: "How do we make it better?"
Connecting the Concepts

Agile + MVP + Prototyping: The Full Picture

Agile Methods Prototype & Iterate

Scrum, Kanban, Lean Prototype, test, refine,
practices MVP Development repeat
Build core features,
launch early

These three frameworks are not isolated — they reinforce each other to create a continuous, customer-driven development engine.
Chapter 5 Summary

Key Takeaways
Agile Principles Scrum / Kanban / Lean MVP Strategy
Iterative, collaborative, adaptive Three methodologies, each suited to Launch fast, validate early, invest
development cycles different contexts wisely

Prototyping Iterative Design

Test assumptions cheaply before full development Continuous user feedback drives product excellence