Talk:PRINCE2 - For successful Project Management

From apppm
Revision as of 22:30, 22 September 2015 by S142899 (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

[[(S142899_I am not aware of whether I am reviewer ½ or 3) In general this is a good article with minor improvements needed. A) 1. Introduction: Clear description of the prince2 method. The word “right” is purposely mentioned 3 times in the same sentence. Is this acceptable? Grammatically I could not identify any obvious error at the introduction. 2.Probably, the use of commas (,) will help the reader to read the text easier. In the PRINCIPLES paragraph, in the last sentence capitals after commas could be changed into small letters. 3.In the CONTINUED BUSINESS JUSTIFICATION paragraph the words: Business Case, start with capital letters. I would recommend to switch in small letters. In the same paragraph, check if reference is missing. 4.In the paragraph LEARN FROMEXPERIENCE, overlapping of the “ lessons learned” meaning exists.(probably reform it in a more concrete way) 5.References for tables are missing 6.In paragraph “Manage by exception” : Refer the references for the four managing levels 7.Focus on Products paragraph according to prince 2 ( reference missing). 8.In the themes paragraph, I would firstly introduce the themes and then I would explain the strength of Prince2. 9.In the PROCESSES Paragraph, when referring to processes use “…” instead of capital letter in each word. 10.Also reference for the figure 2 and table 3 are missing. 11.At the last paragraph, the expression “That is,…” Could be changed in order to ensure a more scientific way of expression.

B. The paragraph PROJECTS IN A PROGRAMME ENVIRONMENT might be evaluated again if it should be fitted in this order on not. Perhaps, it seems too generic and does not follow the flow of the other paragraphs.

c. The article seems convincing enough. Changes are mentioned above in order to create a more solid outcome. Extra information in the THEMES paragraphs could probably be added. (not necessary though)]]

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox