



Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
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
1 / 5
This page cannot be seen from the preview
Don't miss anything!




Business case is the economic feasibility study to determine whether this project will gain benefits after investment or not? Written By: Project Manager
It Includes:
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.
Writing a Business Requirement Document is important because it keeps the whole project team on a single reference point.
It is the small piece of functional requirement in which we explain what end user wants.
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.
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
Based of its Complexity, Team Size, Priority we will decide what will go to sprint cycles in next task.