Scribd
Upload
3 views2 pages

PM KeyWord Definations

The statement of work (SOW) defines the project requirements, deliverables, objectives, timelines, and scope. The project manager studies the SOW to derive user stories, which describe the type of user, what they want, and why. User stories are discussed with the team and client during requirement grooming to refine the project backlog. Resources are then allocated, time estimates are assigned to create a weighted backlog, and high priority user stories are planned for each sprint from the product backlog.

Uploaded by

SkillBuild Pro
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
3 views2 pages

PM KeyWord Definations

The statement of work (SOW) defines the project requirements, deliverables, objectives, timelines, and scope. The project manager studies the SOW to derive user stories, which describe the type of user, what they want, and why. User stories are discussed with the team and client during requirement grooming to refine the project backlog. Resources are then allocated, time estimates are assigned to create a weighted backlog, and high priority user stories are planned for each sprint from the product backlog.

Uploaded by

SkillBuild Pro
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

1.

SOW:
The statement of work (SOW) is a document that provides a description of a given projects
requirements. It defines the scope of work, project deliverables and milestones, objectives,
timelines and scope creeps. It generally acts as a framework drafted at the contracting
phase of the project.
SOW can be framed/drafted by either the client or the product owner or by business
analyst.

2. Brainstorming -> User Stories


After receiving the SOW, the project manager is required to thoroughly go through the
document and extensively study it to derive user stories based on the scope of work,
objectives, milestones and deliverables highlighted in the SOW.
A user story helps to create a simplified description of the projects requirements. Each user
story describes the type of the user, what they want and why (goal). They are composed so
that the project requirements can be broken down into tasks.

A user story generally follows the following format:


As a user, I want to _____ so that _____

3. Requirement Grooming -> Refined Backlog


User stories are mainly what you, as a project manager, derive from the requirements and
scope of the project. To verify and mitigate any ambiguity discussions are held within the
team internally and cross verified with the client to ensure both the client and the team are
on the same page. This is known as requirement grooming.

The groomed requirement document constitutes to refined project backlog. Project backlog
is a roadmap that consists of structured list of deliverables. It often contains a broken down
list of task waiting to be assigned to the allocated team (development/QA/UIUX

Requirement
Project/Product
Grooming Sprint Backlog
Backlog
Document
4. Resource Allocation -> Refined Backlog with Resource
Resources from within the internal team are allocated/assigned to a particular project,
depending on the nature of the project. As a project manager you need to ensure you have
the required recourses before initiating the project in order to avoid any unwanted delays.

5. Time Estimation -> Weighted Backlog


It is essential to know the project timeframe, once that is clear you can assign expected
time taken for each task in the project/product backlog to get a high level time estimation
and a weighted backlog. Time is a key constraint since you need an understanding how
many hours will be required for each task and if the recourse aligned on the task is available
for that time frame or if they are being overburdened.

6. Sprint Backlog -> Sprint Planning


User stories from project backlog that are prioritized are then moved onto sprint backlog. At
this stage you need to plan the number of sprints, a short time-boxed period constituting
between 1-4 weeks, in accordance with the projects timeline and move tasks from
product/project backlog into your sprint backlog based on priority.

You might also like