Talk:Requirements management

NobodyKnows Peer Review

I have gone through the wiki article and the review will be based from a chapter overview and finally an overall review.

Overview

• I like the starting definition, but it would be nice with a relevant reference - see below.
  • "According to The Office of Government Commerce in United Kingdom, requirements are “capabilities and objectives to which any product or service must conform and are common to all development and other engineering activities” and requirements management is “the process of eliciting, documenting, organising, and tracking requirements and communicating this information across the various stakeholders and the project team”."

• I would not use acronyms, when writing a "scientific wiki" article
  • A good requirements management is the key to projects success and better business results. A poor requirements management often lead to project failure [2] : delayed projects, budget overruns, or products that don't come out as designed.

• Requirements management can be handled by using different kinds of tools, which can either be manual processes or specialised tools.
  • Bliver dette berørt?

Overall impression of the Overview chapter

• It is a real nice overview of Requirements Management and I want to keep reading!

Definition of project success

• Please add a reference for this. A strong statement needs a reference.
  • "The success of a project can be described in different ways, but the common criteria is the ability of a project manager to deliver a project in respecting time and budget constraints as well as respecting the customer's expectations. The system or product that have been promised must be the one to be delivered; this is only possible when all the requirements are fulfilled."

Overall impression of the project success

• It would be very nice if a definition of "customers" regarding projects could be made and maybe a few examples.
• Please consider if it is only the customers expectations that needs to be satisfied - yes - please state why.

Poor requirement management as a cause for project failure

• LÆS IGEN

Application context

• An idea would be to make a reference to a wiki article regarding "System Engineering"

System engineering processes

• It feels like the section just ends, without a "wrap-up".

Product development projects

• Please assign reference
  • Product development projects are becoming more and more complex, especially because of the increasing variety of demands from customers

• Please assign reference
  • A way to keep track of the customer’s requirements in new product development is Quality Function Development, which is a tool used for defining the characteristics of a product as targets to be achieved for the engineering characteristics of the product in a way that customer’s requirements are satisfied.

• Good informative chapter!

Construction projects

• A reference is needed for this.
  • Because construction projects are usually experiencing delays and budget overruns, requirements have to be tracked in a satisfactory way

Overall impression of the Application context

• Very good idea to present different aspects, where Requirement management is relevant!
• Overall a very good chapter, but there is a lack of references.

Requirements elicitation

• Very good chapter, easy to understand.

Overall feedback

• Please read the article through for grammatical errors (not many, but a few)
• I would properly introduce the section "Main steps of requirements management" earlier so when reading the different areas, where this approach is relevant the reader will already have an idea.