Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
9 views7 pages

Action Description Project Initiation: Basics To Getting Started

The document outlines the process of project initiation, including steps such as defining the vision statement, securing executive approval, and gathering funding. It details various techniques for requirements discovery and analysis, including brainstorming, interviews, and surveys, to ensure comprehensive understanding of user needs. Additionally, it provides a framework for documenting project scope, objectives, and timelines, along with a checklist for tracking approval status and progress.

Uploaded by

Oludare Ajayi-Smith
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
9 views7 pages

Action Description Project Initiation: Basics To Getting Started

The document outlines the process of project initiation, including steps such as defining the vision statement, securing executive approval, and gathering funding. It details various techniques for requirements discovery and analysis, including brainstorming, interviews, and surveys, to ensure comprehensive understanding of user needs. Additionally, it provides a framework for documenting project scope, objectives, and timelines, along with a checklist for tracking approval status and progress.

Uploaded by

Oludare Ajayi-Smith
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 7

ACTION DESCRIPTION

Project Initiation Basics to getting started


Vision Statement Overview of project goals and benefits
Executive Approval Signoff and sponsorship
Funding Secured Financial commitment to pursue
definition
Requirements Discovery & Research How and where to gather
Identify Capture Techniques requirements?
How will you collect the information?
Brainstorming Use to collect a flow of ideas in quantity;
qualify and improve on them later
Data Analysis Review behavioral data on successful
and failed pathways, including product
sale, use, service experiences, etc.
Document Analysis Review existing as-built specifications,
customer documentation, marketing
materials, and similar materials from
competitive products
Feedback Service calls, logs, reports, emails, and
field anecdotes
Focus Groups Use to collect new requirements, or to
respond to proposed requirements, but
beware of groupthink and herd mentality

Interface Analysis For software and hardware products,


review Human-Machine Interface or
Machine-to-Machine Interfaces
Interviews Key technique: ask open-ended
questions to stakeholders to provoke
more than yes or no responses, listen
closely, note non-verbal signals
Observation Watching behaviors in natural
environment
Prototypes Listen to comments and observe
behaviors in response to prototypes
Requirements Workshops Joint design, collaboration with end-
users and other stakeholders on
requirements
Reverse Engineering Good for competitive analysis, but does
not identify specific customer
needs/should-dos
Surveys Best for soliciting opinions, but does not
always represent hidden customer
needs
Identify Sources Who to involve?
Requirements Analysis Break down discovery findings into specific, categ
Use Case Analysis How is the solution used? Paint a picture
of how users experience it.
Summary Plan Document Brief overview of key learnings -- outline
for actionable project plan
Executive Summary
Scope & Context
Situational Analysis General environment; context
Alternatives Existing methods and competition
Need Elements of a differentiated offering
Solution Overview of proposed offering
Opportunity Vision and expectations
Objectives Goals and specific target metrics
Product Description Based on gathered requirements
Design Goals
Feature Overview
Mockups
Pricing & Forecasts
Team and Resources
Summary Timeline
References

CLICK HERE TO C
REQUIREMENTS PRIORITY
% of PROGRESS
STATUS

HIGH 100% Complete


[Copy email or other approval] MED 65% Not Started
LOW 25% In Progress

Complete
On Hold

Overdue

Needs Review

gs into specific, categorized requirements. Edit, remove, and add indented rows as needed to mak
HERE TO CREATE IN SMARTSHEET
APPROVAL STAT
DESIRED DATE
DATE RATIONALE

Approved 00/00/0000
Submit for Approva 00/00/0000
Submitted 00/00/0000

Needs review 00/00/0000


Submit for Approva 00/00/0000

Submitted 00/00/0000

Needs Review 00/00/0000

ndented rows as needed to make requirements clear and actionable.


T
CHECKLIST KEYS – do not delete –
APPROVAL
STATUS PRIORITY
STATUS
Not Started LOW Submit for Approval

In Progress MED Submitted

Complete HIGH Approved

On Hold Needs review

Overdue

Needs Review

You might also like