Talk:Lean 6 Sigma in project management
From apppm
(Difference between revisions)
(→Feedback) |
|||
Line 32: | Line 32: | ||
==Reviewer 3, DI2009== | ==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 | + | *Summary; I like 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. | *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. |
Revision as of 20:33, 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
Jejenji - REVIEW 1
- Clear introduction. You highlighted the poit —>waste reduction and high quality control <—
- Background gives a perfect idea of how the topic is correlated with nowadays firms.
- Great connection with Toyata (JIT philosophy)
- A paragraph regarding WIND INDUSTRY EXAMPLE could be done
- Detailed explanation of the tool but lack of illustrations (from my point of view imagines of the tools could help a straight forward understanding)
- The Chapter (Example: The multi-objective case) suits perfectly for the description of big scale (portfolio).
- Conclusions are a bit confused and don’t really conclude the article. Maybe a more detailed discussion is needed to increase the score of the article.
- Overall the article is well implemented and the topic is totally interesting.
FORMAL ASPECTS
- Overall the article follows the case method structure
- Grammar wise is correct
- Lack of figures and visual illustrations for the tool part
- Formatted Properly
CONTENT ASPECTS
- The article is totally interesting
- It does relate to PPPM
- Appropriate length
- Flow is great
- Reference materials are great but absence of annotated bibliography
- It seems well elaborated and it’s definitely not a copy paste
Reviewer 3, DI2009
- Summary; I like 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.