Project Management Documents: Business Case, Requirements, Epics, Stories, and Sprints - P, Cheat Sheet of Computer Science

A basic overview of key project management documents, including the business case, business requirement document (brd), functional requirement document (frd), epics, stories, and sprint planning. It outlines the purpose, importance, and key sections of each document, offering a foundational understanding of their roles in project management. The document also includes examples of how to write user stories and acceptance criteria, providing practical insights into agile methodologies.

Typology: Cheat Sheet

2021/2022

Uploaded on 02/17/2025

umer-khan-4
umer-khan-4 🇵🇰

1 document

1 / 5

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Project Business Case:
Business case is the economic feasibility study to determine whether this
project will gain benefits after investment or not?
Written By: Project Manager
What we Have to focus in Project Business Case:
It Includes:
1. Business Owner:
2. Project Scope
3. Project Cost
4. Project Durations
5. Project Risk
6. Return of Investment
7. Minimum Vibal Product
8. Stakeholders
Stakeholder are further divide into
1. Tech Team
2. Finance Team
3. Users
4. Business Owner
Significance of Project Business Case?
1. It determines whether the business or project is beneficial or not?
2. It Identify the stakeholders.
3. It Reduce the Risks
4. It Tells whether there is any need of project?
BRD (Business Requirement Document):
It is the start of any project or Business. It focuses on customer voice,
pf3
pf4
pf5

Partial preview of the text

Download Project Management Documents: Business Case, Requirements, Epics, Stories, and Sprints - P and more Cheat Sheet Computer Science in PDF only on Docsity!

Project Business Case:

Business case is the economic feasibility study to determine whether this project will gain benefits after investment or not? Written By: Project Manager

What we Have to focus in Project Business Case:

It Includes:

  1. Business Owner:
  2. Project Scope
  3. Project Cost
  4. Project Durations
  5. Project Risk
  6. Return of Investment
  7. Minimum Vibal Product
  8. Stakeholders Stakeholder are further divide into
  9. Tech Team
  10. Finance Team
  11. Users
  12. Business Owner Significance of Project Business Case?
  13. It determines whether the business or project is beneficial or not?
  14. It Identify the stakeholders.
  15. It Reduce the Risks
  16. It Tells whether there is any need of project?

BRD (Business Requirement Document):

It is the start of any project or Business. It focuses on customer voice,

whether it is internal customers inside the organization or it Is external customers outside the organization.

Why it is important:

Writing a Business Requirement Document is important because it keeps the whole project team on a single reference point.

Key Sections:

  1. Project Owner
  2. Executive Summary
  3. Glossary
  4. Business Goals
  5. Project Overview & Objectives
  6. Project Scope
  7. Success Criteria
  8. Current State
  9. Target State
  10. Risk, Assumptions, Issues and Dependencies
  11. List of requirements & priorities
  12. Business Rules
  13. Reference Document
  14. Project Budget and Schedule

Stories:

It is the small piece of functional requirement in which we explain what end user wants.

Key Components:

1) Who When Then: Pattern: As …………. […………], I want …….. [………..], So that …... [……..] For example: As an ecommerce shopper, I want filter option in search field, So, that I can find better product quickly 2) Acceptance Criteria: Pattern: Given …………. […………], When ..……….. […………], Then …………... [….………], For example: Given that I am a project page, When I select the price range, Then I find the products in between selected price range. 3) Supporting Models: Screen Mockups, Data Models etc.

Sprint Planning:

It is an event in which we decide what will be delivered in upcoming events and how these tasks will be achieved. In Sprint Planning, we have a Product Backlog which was created by Product Owner, in which we have multiple Epics

Which Story or Epic should be select First?

Based of its Complexity, Team Size, Priority we will decide what will go to sprint cycles in next task.

How Sprint Planning will do?

  1. First, we start to get the Epic from Product Backlog
  2. Do Meeting about that epic
  3. Set the Sprint Goal
  4. Break Down it into stories
  5. Create a Sprint Backlog
  6. Divide each task among dev team along with the completion time
  7. After Completion all the tasks, we again go to First Point and repeat all the steps for Second Epic and so on.