Describe how you would capture requirements and design a SAP enhancement. Obtain business sign off and plan to build
Job spec requirements
Outcome oriented. Able to work with clients,
architects and other IT colleagues to identify
how a solution could bring best business
value. Able to appraise options and make
recommendations.
Able to communicate and explain complex
issues in clear, concise, persuasive
language both verbally and in writing
Engaging others
Clients
Architects
Others
Requirements capture
Planning
Identifying value
Testing assumptions
Mockups #
Documenting
Analysis
Tools e.g. five why's
Prototyping #
Meeting the client #
Workshops
Interviews
User stories
Design
Lotus flower
Process mapping
Service blueprint
Process and journey mapping
Personas
Stakeholder mapping #
Identify priorities
MoScoW
For the individual
Links to strategic objectives
Options appraisal
Technical options #
Delivery options (e.g. feature inclusion)
Requirements catalogue #
Technical (other)
Development
Testers
Training
Assess availability
Roadmap
Project/resource plans
Conversations
Scoring system
Sign-off
Validate requirements
Introduce VOC
Academic cycle / calendar
Student availability
Critical delivery dates
Test assumptions
Alternative mitigating solutions
Costs
Licensing
Resources
Internal
Contractors #
PRINCE2 stage gates
The presentation's delivery
The content
Split slides into core stages
Initiation
Identifying stakeholders
Developing a basic understanding of the problem
Checking against objectives
Summaries
Bullet points
Rationale
Anticipate questions
Developing an understanding
Requirements
Analysis
Technical considerations
Validating requirements
Identifying resource requirements
Helps focus requester's attention on priorities
Planning
click to edit
Technical review
Planning
Based on priorities (value)
Show other options have been considered
Backlog with estimates
Informed by resource requirements
GANTT for durations
Tools
Trello
MS Project
Capabilities of the team and its members