Jump to content

Functional brief

From Wikipedia, the free encyclopedia

This is the current revision of this page, as edited by Citation bot (talk | contribs) at 11:45, 23 August 2022 (Alter: title. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | #UCB_webform 2990/3806). The present address (URL) is a permanent link to this version.

(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

A functional brief, in project management, is a document that talks about the functional specifications of the product that is being developed. A well-defined functional brief allows for all stakeholders to be aware of the scope of the product, the intended functionality and when finalized ensures that there is no feature creep. Once the document is created it is used to conduct a feasibility study and can be used to develop costs and time estimates of the final product.

The document should highlight:[1]

  • The major functional aspects of the product,
  • How they are intended to interact and their inter-dependencies,
  • How the product being developed matches the organization's goals and policies,
  • How the user would interact with the product and
  • What output they intend to obtain from the product.

The functional brief can also contain information about the future plans for the product so that developers can ensure that while designing the product these considerations are included.

References

[edit]
  1. ^ "Functional Brief". Archived from the original on 2014-02-14. Retrieved 2014-04-29.