REQUIREMENTS

DESIGN PROCESS: Dzmitry Yaltykhau

STARTING FROM A
SCRATCH
AGENDA
 Background Information – AS IS overview
 Why Requirements matter?
 Goals and Principles of the Requirements Design Process
 Focus Areas
 Team Roles and Responsibilities
 Requirement Deliverables
 Tools and Templates
 Key Processes
 Results
 SITUATION ‘AS IS’
 Requirements elicitation and analysis
 Prototyping as a major analysis tool
 Slow design and approval process
 Poor requirements documentation

 2 teams (14 Developers + 5 QAs

+ 4AutoQA + Support Engineer)
 10+ product managers
 No experience with BA
 40+ business stakeholders
 No definition of ‘Done’
 Upset with poor delivery
 Upset with requirements
 Immature product design ambiguity
process  Limited tech and test
 Ambitious financial goals documentation
WHY REQUIREMENTS
MATTER?
WHY REQUIREMENTS
MATTER?
Teams with a mature requirements design process are:
 twice more likely to achieve business goals
 70 % more likely to complete project in time and budget
 spending three times less time and money spend on redoing
and fixing bugs
 avoiding scope creep and gold plating
and have…
 happier customers
 happier delivery team
 better product quality
GOALS
 ensure achieving
business goals set for
product initiatives
 ensure the product
roadmap timely delivery
 reduce the risk and time
spent on redoing features
 reduce the time required
for go-to-market event
PRINCIPLES – SEE THE
WHOLE
 focus on achieving
mid/long-term business
goals
 alignment with product
strategy on all levels of
organization
 solid strategy as the
basis for great
requriements
PRINCIPLES – AGILITY
 Quick and well-coordinated
team over strict process
 Lightweight
documentation
 Dynamic nature of
requirements
 Evolutionary and iterative
approach to requirements
development
 Customer Engagement
PRINCIPLES – FOLLOWING
EMERGING STANDARDS
 Lightweight rules and
procedures
 Unified bare minimum
templates for quick start
 Smart customization
when needed
 Easy to navigate and
support product
requirements structure
 FOCUS AREAS

 Role Clarity  Roadmap Management  AHA (Roadmap, Business

Releases, Personas)
 Assignment Clarity  Business Release
 Confluence (PRDs, Epics, User
 Strategy Sharing Management Stories, Acceptance Criteria)
 Building Trustful  Requirements Deliverables  Jira (backlog grooming and
Relations planning, task-tracking)
 Requirement Lifecycle
 Stakeholder Engagement  Zendesk (VOC, Knowledge
 Backlog Grooming Base)
 Traceability across all tools
TEAM ROLES AND
RESPONSIBILITIES
Project Role Scrum Role Responsibilities
Project Manager Scrum - Facilitates requirements estimation, sprint planning
Master and review
- Reports on product roadmap progress
Product Manager Product - Manages product roadmap (idea generation,
Owner initiatives, priorities, business releases)
- Creates Business Case, Financial projections
- Approves PRD, sprint backlog
Business Analyst Team - Elicits and analyses product requirements, defines
Member goals and scope
- Documents requirements at different level of
granularity (theme, epic, story, AC, etc.), UAT Plan
- Facilitates backlog grooming and roadmap review
UX Designer - Produces UI prototypes with different levels of
granularity
- Creates and maintains user/buyer personas, empathy
boards, storyboards and customer journey maps
Software - Estimates and elaborates the requirements
Developer
PRODUCT TEAM STRUCTURE
Role/ GRC PCS PCS PCS OM GRS
Product S Stand Professio Enterpr
ard nal ise
Product Marty Jennifer Jim Sarah Leslie
Manager
Business Dimitri Kate Dimitri
Analyst
Dev Team Omega Delta
Project Shane Sherry
Manager
ROADMAP MANAGEMENT
 Establish Product streams with PO
 Prioritize Product Initiatives and define Business Releases
 Regular Roadmap Review (PM + BA + PdM + Dev Lead)
BUSINESS RELEASE
MANAGEMENT
 Long-term release scoping: AHA
 Short-term release scoping: Jira
 Traceable to Confluence, HP ALM
REQUIREMENTS DESIGN
HORIZONS
Start Strategy Execution Growth End
Idea Concept Product
Prelaunch Launch Scale Enhance Decline
Generation Development Development
0 1 2 3 4 5 6 7

• Idea • Product • Roadmap • Roadmap • Roadmap

Deliverables

• Roadmap • Roadmap
Description Hierarchy • Price Model • New epics / • New epics / • New epics / • New epics /
• User Personas • Business stories per stories per stories per stories per
• Opportunity Case roadmap roadmap roadmap roadmap
Profile • Story Board • Refine prior • Refine prior • Refine prior • Refine prior
• Glossary • Epics / delivs as delivs as delivs as delivs as
Stories needed needed needed needed
• Product
Reqmts • Launch • Offering
• Non- Planning Dashboard
functional
• Wireframes
REQUIREMENTS DELIVERABLES
– STRATEGY HORIZON
Deliverable / Description Tool
Activity
User Personas Key users and their needs are identified & aggregated into persona descriptions that Aha: Strategy /
describe the sample profile of a typical user. Personas
Opportunity Profile A preliminary view of the product definition described in PPT and a formal financial Aha Business
(Stage 1 Business Case) model Model
Business Case Excel for financial
The fully developed Business Case consists of product definition information
model
described in PPT & a formal financial model
Roadmap A one year+ look ahead of strategic goals, strategic initiatives and business releases Aha: Portfolio
Notebook
Pricing Model Summary level view of the pricing approach for the product with backup detail as Excel stored in
appropriate. Sharepoint
Product Requirements Documents in non-technical terms what the product must provide or do to meet Confluence
market place needs. Can be supported by an Impact Map. template

Non-functional Requirements Requirements that specify the operation of the system rather than specific functional Word stored in
behaviors. Examples are performance, scalability, disaster recovery. Confluence
Glossary Defines key Policy Center platform terminology Excel stored
Confluence
REQUIREMENTS DELIVERABLES
– DELIVERY HORIZON
Deliverable / Description Tool
Activity
Epics / User Stories User stories are simple descriptions of a feature told from the perspective of the Confluence for the complete
person who desires the new capability, usually a user or customer of the system. An definition of the story.
epic captures a large body of work; broken down into stories. Jira for tracking through
sprint cycle
Acceptance Criteria Itemizes the expectations that must be met before the user story can be considered Confluence; contained
complete. The acceptance criteria will be used in later testing within the story definition

Visual Models Comprehensive visualization of the requirements (user story maps, logical data Visio and Confluence
model, state machine diagrams, flowcharts, etc.)
Wireframes First pass, roughly drawn screen and report layouts. (Not needed for standard UI Hand-drawn; scanned into a
dialogs covered in the Visual Style Guide) PDF or Office Suite
Final UX Designs Finalized screen & report designs Axure

Visual Style Guide Describes Policy Center standards surrounding user interface design; states Axure
requirements that apply to all screen / report designs.
Roles Matrix Describes the roles and the allowed permissions in the system. Confluence
UAT plan Describes the list of test scenarios to be verified to approve the working product. HP ALM
PRODUCT REQUIREMENTS
DOCUMENT
EPIC
USER STORY
UAT PLAN
API DOCUMENTATION
TOOLS
AHA
Business
Roadmap Release
Confluence

Jira Fix Version

User Story
Manager
Product

Epic
Theme User Story Subtas
Stream/Edition

k B
User Story Task
A
Product

Epic
User Story Bug C
User Story K
Epic
Theme

User Story L
User vStory O
Epic G
User vStory

Business Analyst Engineering

Team
REQUIREMENT LIFECYCLE
KEY MEETINGS
Meeting Frequency PM Pd BA UX/ Dev Dev/ Suppo SS
M UI Lead QA rt
Requirements As needed P F P P
Workshops
Roadmap Review Bi-weekly P P F P
Backlog Grooming Bi-weekly P P F
Estimation Weekly P F P P P
Release Planning Bi-weekly F P P P
UAT One week F P P P
before each
release
BA/PdM Weekly Weekly P P
UX/BA/PdM Weekly P P P
Weekly
Customer Support Weekly P P P
JIRA PRODUCT PLANNING
BOARDS
JIRA TEAM TASK TRACKING
BOARDS
JIRA PROGRESS REPORTING
DASHBOARD
BACKLOG GROOMING
 Communicate the requirements to the team
 Decompose the requirements (split/merge)
 Identify and fill in the gaps
 Identify and resolve inconsistencies and conflicts
 Identify impediments, dependencies and risks
 Optimize a solution
 Estimate the backlog items
 Prioritize the backlog items
USER COMMUNITY
ENGAGEMENT
 Voice of Customer requests assessment
 Idea Generation Portal setup
 Knowledge Base maintenance
 User Acceptance Testing (by Product Team)
 Sprint Reviews
RESULTS - UX/UI TEAM
PROCESS IMPACT
 Engagement in requirements design
 Focus on Personas
 User Experience Mapping
 Design grooming and review
 User research
RESULTS - ENGINEERING
TEAM IMPACT
 BA as a single point-of-contact for requirements
 Accurate estimates and sprint planning
 Great incentive for QA process change
 Increased velocity
 Better delivery with great sprint reviews
RESULTS – PRODUCT TEAM
IMPACT
 business goals for H1 2018
are mostly met
 product roadmap is fully
completed for Q4 2017 and H1
2018 on time
 fewer cases of redoing
features
 fewer incidents reported by
clients
 decreased delivery times
 increased planning accuracy
SUMMARY
 Starting from a scratch is challenging and rewarding
 Build trustful relationships before making a change
 Focus on process standards, but exceptions are ok
 Be hands-on and demonstrate leadership
 Maintain transparency and traceability
 Pick the right opportunity…

…without tackling too

much