3rd Class
-Product Development and Product Rqmts Best Practices
-Product Management and Product Marketing Overview
Bus100: Building Software Products:
From Strategy to Sales
John Gibbon
Product Development and Product
Requirements Best Practices
(-Agile vs. Waterfall)
-Development Processes and Documents
Waterfall
Why
Define
Agile
Design
Develop
Design
Define
Why
Release
Develop
Test
Test
Release
Agile versus Waterfall
Agile / Recent
Waterfall / Traditional
• Less Death Marches
• Demonstrable Intermediate
Milestones; More Predictable
Releases
• Integration Testing Built-in
• Flexible (Agile) During
Development
• More Realistic
• Requires Trust, Negotiations,
& Cooperation
• Document, Feature, and
Process Driven
• Familiar and Understandable
• Scalable: Distributed Teams &
Junior Members
• Long Term Goals Defined
• No Throw Away Code
• Better Suited for Mission
Critical Deliverables
Company or Product Portfolio Strategy
Where should we go?
Why will we be
successful there?
How do we get there?
Development Processes and Documents
1. Where and Why
MRD (Market Requirements Document): Expanded Business Case
2. What
PRD (Product Requirements Document): Uses Cases and More!
3. How
Architectural and Technical Specifications; Test Plan
Where and Why: Business Case
1. Product Mission
2. Value Proposition
For (customer) Who (has problem) The (Product) That
(solves problem) Unlike (competitors) Our Product
(differentiator)
1. Success Metrics
2. Key Requirements / Not Included
3. Market Analysis
4. Build/Buy/Partner
5. Revenue Assumptions and Estimates
6. Other Key Assumptions
7. Workflow and Other Design Aspects
Where and Why: Longer Business Case
or MRD
MRD (Market Requirements Document): Add to or
Expand Any Section of Shorter Business Case
Depending on What is Required by Business or Target
Audience
1. More Market Analysis
2. Platform or Multi-Generational Strategy
3. Non-Functional Platform Requirements:
Scalability, Security, Reliability, Availability,
Installation, etc.
4. Better Revenue Estimates
5. Better Cost Estimates
9
What: Use Case Focused Product Requirements
Photo Sharing Site
upload
member
organize
Use Case Diagram:
Functional Requirements
Describing System from User
Perspective
view
friend
administrator
UML Activity Use Case Diagram
Member
Photo Site
Upload
Photo
Share?
Shares
Photo w/
Group
UML (Unified Modeling Language) provides a variety of
different diagram types to describe a software system: use
case diagram, activity diagram, collaboration diagrams, etc.
UML Activity Use Case Diagram
Use Case Functional Requirements
Documentation
1.
2.
3.
4.
5.
6.
7.
8.
9.
Use Case Name
Goal / Summary
Actors
Preconditions
Triggers
Basic Course of Events
Alternative Paths
Postconditions
Business rules
What: Use Case Focused Product
Requirements
PRD (Product Requirements Document):
Uses Cases and More!
1. Description of Actors or Users
2. Series of Use Cases: General to Specific
3. Non-Functional Product Requirements:
Scalability, Security, Reliability, Availability,
Installation, etc.
How: Technical Specifications
1.
Architecture Diagrams & Technical Specifications
1. Patterns
2. Standards
-Unit Tests - Test Driven Development
-Code Standards – Code Review
2. Test Plan
1. Integration and Use Case Test
2. Release Process and Document
Page 15
CONFIDENTIAL
Describe Overall Architectural Pattern
Struts framework implementing MVC with Java Servlets and JSPs controller:
struts controller servlet and action classes
Especially to Create Rules for What Logic Lives Where
Page 16
CONFIDENTIAL
Describing a New Architectural Pattern
Architectural Next Steps: transform XML to HTML via XSLT
(Collaboration Diagram: Object View with Numbered Sequences)
Architecture Overview
Remend
Manager
• Occupancy
• Cash4Keys
• Eviction
• Process
• Audit
• Approval
•••
•••
•••
• Reports
• Title
• Legal
• HUD
•••
• File
Cabinet
• Counseling
• Workout
• Refinance
Loss Mit
Foreclosur
e
REO
Asset Eval
Security
Auditing
Doc
Mgmt
Messaging
Workflow
Reporting
Search
Forms
Domain
• Inbox
-- Workflow, Forms, Reports --
Integration Modules
Enterprise User
Legacy
Document
Vendor
• Reports
J2EE Application Server
J2EE Foundation
• RDBMS
Data API
Config
••Inbox
&
• Tasks
Admin
• Actions
Data
Application
Services
• Contact
s Vendor
Workspace
• Doc Mgmt
• Proprietary DB
• Servicing
Page
17
Individual
Vendor
Bulk
Vendor
Bulk
Vendor
Overall
Service Topology
Individual
Vendor
User
User
Secure Website
B2B Integration
[SOAP]
“Remend”
Vendor
Workspace
(HTTPS)
“Remend”
Gateway Admin
(HTTPS)
1. Reports
2. Admin
New
Features
B2B Integration
[SOAP]
Other Dept
B2B Integration
[SOAP]
REO
Vendor Gateway
Next Bank
Remend Manager
E-Commerce
Partner
$
B2B Integration
[API]
Third Party
Database
Integration
Asset
Evaluation
Other Dept
REO
Servicer
B2B Integration
[SOAP]
Foundaton
“Outsource”
Remend Manager
Foundaton
Other Dept
B2B Integration
[SOAP]
REO
Foundaton
EMC
Remend Manager
Last Modified: 5/5/2005
Product Management and
Product Marketing Overview
Product Management
Design
Agile
Define
Why
Release
Develop
Design
Test
Define
Develop
Deploy
(Support /
Feedback)
®
Business
Case
Positioning
Marketing
Plan
A market-driven
model for managing
and marketing
technology products
Distinctive
Competence
Market
Sizing
Pricing
Sales
Process
Customer
Acquisition
Market
Research
Product
Performance
Buy, Build
or Partner
Market
Requirements
Customer
Retention
Market
Problems
Operational
Metrics
Product
Portfolio
Product
Roadmap
Launch
Plan
Quantitative
Analysis
Product
Strategy
Product
Planning
Program
Strategy
Sales
Readiness
Channel
Support
Innovation
User
Personas
Buyer
Personas
Channel
Training
Presentation
s & Demos
Use
Scenarios
Success
Stories
Collateral &
Sales Tools
“Special”
Calls
Release
Milestones
Thought
Leaders
White
Papers
Event
Support
Lead
Generation
Competitive
Write-Up
Answer
Desk
Market
Analysis
Technology
Assessment
Competitive
Analysis
Win/Loss
Analysis
©1993-2005 Pragmatic Marketing, Inc. All rights reserved.
Tactical
Strategic
Pragmatic Marketing Framework