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

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 was about doing it, but thank you for remembering

• I found the introduction quite confusing. I cannot quickly understand what the article is about, but it seems you are on it.

Since I changed the topic, I still have to work on the final introduction

• The two figures in the section “FMEA worksheet” are missing the description.

The figures and their layouts are still "under development"

• 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.

I agree with you since it's the core part of my article

• As you have some sections to be completed I am looking forward to read the full article.

Reviewer 2, s112960

Overall

• It’s very interesting that you have chosen to scope your article to product development project and nice choice of method.
• You follow the ‘method’ structure

Formal:

• I like your overall format and style
• Read through the article with focus on consistency with big or small letters. For example, in the title you write ‘The Failure Mode and effects analysis’ but further down you write ‘The Failure Modes and Effects Analysis’.
• Good use of visuals
• I like how you write very clear and to the point

Abstract

• It looks as if there are missing some lines e.g. after ‘This article aims to show how…’ but I am guessing you just haven’t completed the abstract yet ☺

As explained in the previous review comment, I still have to work on the introduction

• I feel like there is missing a mentioning of your scope: product development projects, before the actual model is descripted.

I decided to follow the method structure, which starts with the introduction of the method/model, because the FMEA can be used in various context. Relations to project development are at the end of the article as achievements of the discussion

• I would love to get an introduction or written in the abstract overall what you are going to do in this article.

Model description and procedure

• Good use of bullet points
• It might be an idea to explain the concept of a ‘failure mode’ a bit earlier in the model description

I think you're right, since there are many references to failure modes in the text

FMEA in product development projects

• I really liked the section on product life cycle
• Good illustrations however, the three pictures a very small so I can’t read them which is a shame

I still have to make figure references in the text and add the description. I'll take care of that

• It might be an idea to have the sections ‘Project life cycle’ and ‘Project risk management’ in the top. I that way you explain the context of FMEA and why it’s important first. But then again, it might just be because you have not finished the article yet that it seems that way.

see previous comment: I feel like there is missing a mentioning of your scope: product development projects, before the actual model is descripted. I decided to follow the method structure, which starts with the introduction of the method/model, because the FMEA can be used in various context. Relations to project development are at the end of the article as achievements of the discussion

I’m looking forward to reading your finished article. Good luck!

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.

The article is still under development :) , but I will take care of it

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.

I agree!!

• 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.

"Agree again,already explained in previous comments"

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!