Prd là gì

What is a Product Requirements Document?

A hàng hóa requirements document (PRD) is an artifact used in the sản phẩm development process to communicate what capabilities must be included in a sản phẩm release to the development and testing teams. This document is typically used more in waterfall environments where sản phẩm definition, thiết kế, & delivery happen sequentially, but may be used in an agile setting as well.quý khách đang xem: Prd là gì

The PRD will contain everything that must be included in a release khổng lồ be considered complete, serving as a guide for subsequent documents in the release process. While PRDs may hint at a potential implementation to lớn illustrate a use case, they may not dictate a specific implementation.

Bạn đang xem: Prd là gì

See also: Market Requirements Document (MRD)

What’s the Difference Between a PRD & an MRD?

For decades, a hàng hóa requirements document (PRD) was the most important artifact hàng hóa managers would create. It painstakingly lists out everything required for a given hàng hóa release và serves as the document of record that the entire release is based on. In short, if it isn’t included in the PRD, it won’t be included in the release.

The PRD may follow on the heels of a sale requirements document (MRD)—created by sản phẩm marketing, sale, or hàng hóa management as well—that describes customer dem&, market opportunity, & a business case for the overall sản phẩm or a particular hàng hóa release.

The PRD itself does not touch on market opportunity or revenue but is instead firmly rooted in use cases và desired functionality. Each feature or capability is usually described as a separate thành tích, & a use case is typically included for every vật phẩm as well.

Based on the PRD, a number of other artifacts will be created by others in the organization. Engineering will create a functional specification, which describes how each thành tích in the PRD will be implemented, and they may also create (or update) an architectural design document. UX will create wireframes and mockups as needed, và chất lượng assurance will write a demo plan ensuring every single use case in the PRD can be successfully executed during testing.


What Should a Product Requirements Document Contain?

A PRD must include every explicit capability required for the release. To support each desired capability, there should be an accompanying use case illustrating how a user would utilize this functionality & to inform the thử nghiệm plan.

If a feature is complex, sub-items may be used lớn provide more detail và granularity for the technical teams. Each of these sub-items should include their own use case when relevant.

In addition to the specific features and capabilities, the PRD should include an overview/purpose for the release. While this shouldn’t try lớn replicate what is in the MRD, it should detail exactly what the product team is trying lớn achieve with this specific release (as an MRD may be used for multiple releases of the same product/suite of products).

In addition to the functional requirements, the PRD should also spell out any other requirements. These include any system or environmental requirements (i.e., this sản phẩm should run on Windows 10 or later, or it should run in Firefox, Chrome & Safari browsers), as well as any usability requirements (i.e. one-handed navigation for thiết bị di động apps).

The final batch of ingredients for a PRD is the Assumptions, Constraints, and Dependencies.

Assumptions are anything you expect to be in place (yet isn’t guaranteed), such as assuming that all users will have Internet connectivity.Constraints dictate something the eventual implementation can’t require, be it a budgetary constraint or a technical one.

Xem thêm: Cách Kiếm Bùa Trong Âm Dương Sư, Hæ°Á»›Ng DẫN Chæ¡I ÂM Dæ°Æ¡Ng Sæ°

Dependencies are any known condition or sản phẩm the hàng hóa will rely on, such as depending on Google Maps lớn add directions for a dog walking tiện ích.


What’s an Example of Product Requirements Document?

The following is a basic outline of what should be included in a PRD. There are no hard-and-fast rules for this, but these items are typically present:

Objective/Goal: Explain why are you building this and what vị you hope khổng lồ accomplish.Features: For each feature, you should include a description, goal và use case at a minimum. Additional details may be helpful or necessary depending on the complexity of the feature, such as out-of-scope items.UX Flow và Design Notes: Most organizations complete the UX thiết kế of features after the PRD has been reviewed & accepted. However, there may be some general guidance required at this stage khổng lồ ensure the release objectives are met. This is not the place for pixel-perfect mockups or wireframes that bản đồ out every possible scenario; instead, it can be used to lớn describe the overall user workflow.System và Environment Requirements: Which end-user environments will be supported (such as browsers, operating systems, memory, and processing power, etc.).Assumptions, Constraints và Dependencies: List out what is expected of users, any limits for the implementation to lớn be aware of and any outside elements required for the final solution khổng lồ be functional.

What are Steps in Creating a PRD?

Assuming an MRD already exists, product management should first consult with sản phẩm sale lớn ensure there’s a full understanding of the business drivers for the specific release being described in the PRD. From there, whichever sản phẩm prioritization methods are already being used should be tapped to lớn identify what is in scope for the release.

It’s then time to author the document, utilizing notes and user feedbachồng captured for each feature being included in the release. The document should go through several rounds of đánh giá with others in the hàng hóa team if possible khổng lồ ensure as many potential questions have sầu been answered và the document is as thorough as possible.

With a fully complete PRD, it should next be circulated aước ao the business side stakeholders khổng lồ confirm they’re aligned with the objective sầu of the release and the features included khổng lồ meet that objective. When consensus is reached, it’s time to lớn hvà the PRD over to engineering.

At this stage, there will be questions, clarifications, & challenges from the technical team that should be addressed verbally và updated in the PRD if necessary. The goal is to have sầu a PRD thorough và comprehensive sầu enough so there are no surprises later on. Once there is an agreement that the PRD has reached that stage, it is then passed onto lớn other teams for UX thiết kế, functional specifications and demo plan definition.

By including all these teams in the PRD creation & nhận xét process, it gets everyone onboard with the desired outcome và contents of the release. There should be little question as to what will be shipped, how it will benefit the business & its impact on users at the kết thúc of the process.

Leave a Reply

Your email address will not be published. Required fields are marked *

  • Aniki là gì

  • #4621: cream pie là gì vậy mấy thím?

  • Soft swing là gì

  • Grammar nazi là gì

  • x

    Welcome Back!

    Login to your account below

    Retrieve your password

    Please enter your username or email address to reset your password.