Talk:Lean 6 Sigma in project management
From apppm
(Difference between revisions)
(Created page with "Anna: I like your topic and the direction it is headed with the focus on the tool within program management. Remember to follow to requirements for the structure once you cont...") |
|||
Line 1: | Line 1: | ||
Anna: I like your topic and the direction it is headed with the focus on the tool within program management. Remember to follow to requirements for the structure once you continue with your article. | Anna: I like your topic and the direction it is headed with the focus on the tool within program management. Remember to follow to requirements for the structure once you continue with your article. | ||
+ | |||
+ | =Feedback= | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ==Reviewer 3, DI2009== | ||
+ | *Summary; I the beginning of your article however I see it more as an introduction than a summary of the article. A summary should give the reader an overview and make it easy for the reader to know what he should expect when reading the article | ||
+ | |||
+ | *Formatted: I think the text get a bit “heavy” maybe with a better use of the Wiki-features such as sub-headings, proper bullet-point will help giving a better overview. | ||
+ | |||
+ | *Structure: | ||
+ | **I like the structure and I think it is nice to wrap up the article with a discussion of the drawbacks/”cons”. | ||
+ | **As well I think you introduce every section well (very short and precise) | ||
+ | |||
+ | *Figures: | ||
+ | **Nice with many relevant figures that match the content of the text. | ||
+ | **Remember to refer to the figures in the text | ||
+ | **Some figures are unnecessary big (e.g. Pareto boundaries), some are very small and hard to read (e.g. Simplified Value Mapping Tool. [7]) | ||
+ | **As well I believe you have copied the figures from some textbooks of websites, remember the reference and make sure you are allowed to use it (no copyright) | ||
+ | |||
+ | *References: | ||
+ | **Remember we are supposed to make an annotated biography, meaning a reference list with a short description. |
Revision as of 15:50, 22 September 2015
Anna: I like your topic and the direction it is headed with the focus on the tool within program management. Remember to follow to requirements for the structure once you continue with your article.
Feedback
Reviewer 3, DI2009
- Summary; I the beginning of your article however I see it more as an introduction than a summary of the article. A summary should give the reader an overview and make it easy for the reader to know what he should expect when reading the article
- Formatted: I think the text get a bit “heavy” maybe with a better use of the Wiki-features such as sub-headings, proper bullet-point will help giving a better overview.
- Structure:
- I like the structure and I think it is nice to wrap up the article with a discussion of the drawbacks/”cons”.
- As well I think you introduce every section well (very short and precise)
- Figures:
- Nice with many relevant figures that match the content of the text.
- Remember to refer to the figures in the text
- Some figures are unnecessary big (e.g. Pareto boundaries), some are very small and hard to read (e.g. Simplified Value Mapping Tool. [7])
- As well I believe you have copied the figures from some textbooks of websites, remember the reference and make sure you are allowed to use it (no copyright)
- References:
- Remember we are supposed to make an annotated biography, meaning a reference list with a short description.