Product Management for Software-as-a-Service (SaaS) is a series of techniques that you can learn in order to plan more efficiently and develop better software products. Rachelle will tell us about Sage One SaaS.
Seal of Good Local Governance (SGLG) 2024Final.pptx
Product Management for Software-as-a-Service - Rachele Cordier
1. Explorers
Festival
2013
Lisbon
Rachele
Cordier
Product,
Program
and
Project
Management
Director
Rachele.cordier@sage.com
2. Agenda
• The
Product
Development
Lifecyle
Overview:
• What
tends
to
happen
in
real
life
• Product
Development
Lifecycle
• A
li?le
Focus
on
Product
Management:
•
•
•
•
•
What
is
SoDware
Product
Management
?
The
ISPMA
Framework
What
does
the
role
of
Product
Manager
means
?
Product
Requirement
Workflow
Choosing
the
right
Tools
• Most
common
challenges
of
Product
Management
• Golden
Rules
• QuesLons
and
Answers
3.
4. Product
Management
Lifecycle
Services
and
Support
Sales
and
DistribuLon
Strategic
Management
Project
/
Program
/
Release
Management
Product
Strategy
Product
Planning
MarkeLng
Developement
5. What
is
Software
Product
Management
?
• Processes
and
Discipline
which
creates
and
drives
a
Product
from
IncepLon
to
Market
Delivery
• Product
management
was
seen
in
the
nineLes
as
a
“lonely
role”
as
this
was
different
from
Product
MarkeLng
Management
and
Program
Management:
Now,
in
most
organizaLons,
it
is
the
role
which
will
drive
the
delivery
AND
the
commercial
success:
The
roles
now
make
one.
• You
cannot
do
Product
Management
on
its
own:
be
involved
with:
•
•
•
•
•
Strategy
Development
MarkeLng
Services
and
Support
Release
Management
7. What
does
the
role
of
Product
Manager
means
?
X-‐funcLonal
Leadership
Market
Research
and
Requirements
gathering
Market
and
SoDware
Requirement
Documents
creaLon
Managing
Product
Roadmaps
Content
and
Lmelines
Managing
the
release
through
a
thorough
Release
Management
Process
CommunicaLon
with
all
other
businesses
in
order
to
understand
risks,
issues,
constraints…
• …
•
•
•
•
•
•
8. Product
Requirement
WorkIlow
Market
Requirement
Document
MRD
•
•
•
•
•
•
•
•
•
•
Market
info
Business
needs
Customer
needs
CompeLLon
Product
Offer
Metrics
Channel
Pricing
Metrics
Timeline
Ie:
Invoicing
Product
Requirements
REQ
• Skeleton
/
Basis
of
the
Product
Ie:
Invoicing
Features
FEAT
X
Features
=
1
Requirement
Ie:
Invoicing
• Cer=fica=on
• SAF-‐T
• Business
data
• …
SoDware
Requirement
SpecificaLon
Use
Cases
SRS
/
UC
1
Feature
=
X
UC’s
• Feature
Def
• Use
Cases
Ie:
As
a
user
I
want
to
be
able
to
print
an
Invoice
SoDware
TesLng
SpecificaLon
STS
1
UC
=
1
STS
Ie:
As
a
user
I
want
to
be
able
to
print
an
Invoice
Test
case:
Print
an
Invoice
9. Choosing
the
Right
Tools
• Use
a
Planning
Tool
to
track
the
Program
• Choose
the
right
tools
for
Requirement
Management:
• Process
and
workflows:
CreaLon,
descripLon,
allocaLon,
Lme
tracking…
• X-‐funcLonal
use:
PdMs,
Devs,
QA
• Ease
of
Tracking
your
Requirement,
from
IncepLon
to
Release
• Thorough
ReporLng
engine
• Many
good
tools
out
there:
•
•
•
•
•
MicrosoD
Project
Plan
IBM
Requisite
Pro
Atlassian:
JIRA
Atlassian:
Confluence
...
10. Most
common
challenges
of
Product
Management
• Understanding
your
place
!
• Understand
what
is
best
for
the
Product’s
future:
We
need
a
quick
fix
versus
a
longer
term
one
• PrioriLzaLon
• Saying
NO
(to
clients,
to
internal
people,
to
stakeholders…)
• Understanding
technical
constraints
• Being
on
top
of
the
Release
Plan
• X-‐funcLonal
communicaLon
• Agree
to
disagree
!
• Accept
external
Blockers
• …
11. Golden
Rules
• Never
assume
anything.
AssumpLon
is
not
healthy
!
• If
it
ain’t
broken,
don’t
fix
it
!
• DocumentaLon
is
imperaLve
for
construcLve
progress
and
program
conLnuity
• Don’t
be
scared
to
speak
to
«
the
Geeks
»
!
• Know
what
you
don’t
know
• Run
Beta
programs
when
feasible:
Best
way
to
build
up
and
prioriLze
your
pipe
• Correct
esLmaLons
will
be
what
will
make
your
product
get
out
on
Lme.
Challenge
the
R&D
team
!
• …