Infrastructure requirements elicitation and design roadmap Travis Barker, MPA GCPM Innovate Vancouver https://innovatevancouver.org Consulting@innovatevancouver.org

1. Waterfall, Scrum, Agile
Governance, Working
Groups, Reporting
Milestones, Decision
Points, Critical Path
Deadlines
Stakeholders &
Workstream Owners
Waterfall, Scrum, Agile
Reporting Requirements
Decision Owners
Priorities & Concerns
Lessons Learned from
Past Projects
Training & Coaching
Needed
Developers
Designers
Testers
Administrators
File Registry
Help Desk
Business Analysts
Project/ Product
Managers
Cloud vs. Onsite
Database & Storage
Applications
Processor
Server
Security
Integrators
Business Rules &
Processes
Integrators
Network
Protocols/ Code
Requirements &
Specifications
Team
Business Model &
Enterprise
Architecture
Present State & Future
State
Technology & Software
Stacks
Risks & Opportunities
Schedule, Cost, Quality,
Scope
Testing, Pilots, &
Validation Process
Stack current in use
Stack needed for future
Customers
Dashboards & Insights
Needed
Tools for Communication,
Planning, Tracking,
Reporting, & Risk Mgt.
Value Stream & Proposition
Products & Services
Data Requirements
Use Cases
KPI: Operations, Security,
Reliability, Performance, Cost
Type of Integration
Type of Migration
Type of Testing
Type of Pilots
Types of Dependencies
Data Governance
Planning
Approach
Project Culture
Planning &
Coordinating Tools
Paths
Infrastructure
Stack
https://innovatevancouver.org
Using an Agile Scrum framework, requirements are
identified and tested in increments. Each phase or
increment supports the refinement of the product
requirements and the product backlog. The goal is to
identify user requirements, cases, and specifications in
advance and update (or validate) as products and
features are delivered.
Software
Infrastructure
Design Build
Roadmap