Talk:Requirements management
From apppm
(Difference between revisions)
NobodyKnows (Talk | contribs) (→NobodyKnows Peer Review) |
NobodyKnows (Talk | contribs) (→NobodyKnows Peer Review) |
||
| Line 1: | Line 1: | ||
= NobodyKnows Peer Review= | = 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 ''Overview chapter'' === | ||
| + | * 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 == | ||
Revision as of 16:12, 25 November 2014
Contents |
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.
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 Overview chapter
- 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.
