Talk:The Failure Mode and effects analysis (FMEA) in product development projects

From apppm
(Difference between revisions)
Jump to: navigation, search
(Created page with "==Reviewer 3, s145170:== '''Overall:''' * The article clearly follows the “methods” structure, is very clear, comprehensive, to the point and covers different aspects of...")
 
Line 1: Line 1:
 +
==Reviewer 1, s142911:==
 +
 +
*It seems to me that you are properly following the “methods” structure.
 +
 +
* Nice use of the typical WIKI features as well as the writing style with short sentences.
 +
 +
*Even thought the article seems unfinished, you already provide many references. Remember to add a brief summary and to link them properly.
 +
 +
*Regarding the figures, remember to add the source if you have taken from the internet/book
 +
 +
*I found the introduction quite confusing. I cannot quickly understand what the article is about, but it seems you are on it.
 +
 +
* The two figures in the section “FMEA worksheet” are missing the description.
 +
 +
*I would elaborate more the section about the application of FMEA in projects. Your main topic is applied to product development, however I would add content to that section.
 +
 +
*As you have some sections to be completed I am looking forward to read the full article.
 +
 
==Reviewer 3, s145170:==
 
==Reviewer 3, s145170:==
  

Revision as of 22:55, 22 September 2015

Reviewer 1, s142911:

  • It seems to me that you are properly following the “methods” structure.
  • Nice use of the typical WIKI features as well as the writing style with short sentences.
  • Even thought the article seems unfinished, you already provide many references. Remember to add a brief summary and to link them properly.
  • Regarding the figures, remember to add the source if you have taken from the internet/book
  • I found the introduction quite confusing. I cannot quickly understand what the article is about, but it seems you are on it.
  • The two figures in the section “FMEA worksheet” are missing the description.
  • I would elaborate more the section about the application of FMEA in projects. Your main topic is applied to product development, however I would add content to that section.
  • As you have some sections to be completed I am looking forward to read the full article.

Reviewer 3, s145170:

Overall:

  • The article clearly follows the “methods” structure, is very clear, comprehensive, to the point and covers different aspects of the methodology described.
  • The topic is related to a project, program or portfolio topic
  • Good and qualified academic language
  • The text can be followed and understood, even for someone that does not posses the topic/methodology
  • Nice figures that accompany the description of the methodology. Good that you have the references as well

Abstract:

  • Good introduction (uncertainties and the necessity of risk management), however you could mention that FMEA will be analyzed as a tool for solving these uncertainties
  • The last paragraph seems a bit separated from the rest of the abstract.

Model description and procedure:

  • Important that you start by introducing the general methodology and describe the different aspects and types of the methodology.
  • Maybe an introductory description could be added in the “FMEA worksheet”, which explains the general philosophy of this method before analyzing the various steps.
  • The figure of “FMEA worksheet” is very representative and contributes to the visualization and understanding of this part of the method.

FMEA in product development projects:

  • I liked that you include the project lifecycle and risk management part, so that you inform the reader about these two main topics that you are going to include in the part of the application of FMEA.
  • Maybe you could include a bid more description of the application of FMEA in projects (in case you are about to add it, I just mention that), as it is the main topic of your article.

Recommendations:

  • A practical example of the implementation of this methodology could be added to support the comprehensive description of the methodology.

Very comprehensive analysis of a crucial problem–solving method which identifies problems before they occur (planning before materializing) with an easy-to-read text. I wish you good luck with the rest!

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox