Talk:Project Life Cycle in Industrial Engineering - Revision history

Habib at 22:30, 19 February 2018

2018-02-19T22:30:00Z

← Older revision		Revision as of 22:30, 19 February 2018
Line 113:		Line 113:

	===Answer 1===		===Answer 1===
	~~''Answer here''~~		The summary is ok. The topic that the article discusses has a good and relevant focus on project/program/portfolio. However, it may be a bit too wide/generic topic.

			Personally, I would like to have a clear overview of what the article discusses, which is not explained. As a reader I miss phrases like "This article discusses..." or "firstly bla bla bla is considered, secondly bla bla is considered" and so on, so the reader knows what to expect from the article.

	===Question 2 · TEXT===		===Question 2 · TEXT===
Line 129:		Line 131:

	===Answer 2===		===Answer 2===
	~~''Answer here''~~		The argument of the article is clear, but there is not a good flow. Again, as a reader I become confused when it is not clearly defined what the following section is about - the article suddenly jumps into theory, before explaining that it wats to do that.

			I like however the fact that theory and examples are separated.

			Furthermore, I suggest that the bullet-points in the "Initiation" and "Planning" sections are expanded into a whole text. This will help to keep the structure of the article concise and it binds the single pieces of the text together.

	===Question 3 · TEXT===		===Question 3 · TEXT===
Line 141:		Line 147:

	===Answer 3===		===Answer 3===
	~~''Answer here''~~		I did not find any major grammatical and spelling errors. The language is ok and does not contain unnecessary fill words.

	===Question 4 · TEXT===		===Question 4 · TEXT===
Line 153:		Line 159:

	===Answer 4===		===Answer 4===
	~~''Answer here''~~		Figures should generally be self-explanatory. The two figures used in the article are good, but the article does not refer to the figures in the text. Thus the reader will never be referred to the figures and they may be neglected.

	===Question 5 · TEXT===		===Question 5 · TEXT===
Line 165:		Line 171:

	===Answer 5===		===Answer 5===
	~~''Answer here''~~		The topic that the article discusses is highly relevant for any project manager. The project life cycle is a topic that has a high practical relevance, and it is stated several times in the article why it is relevant.

	===Question 6 · TEXT===		===Question 6 · TEXT===
Line 177:		Line 183:

	===Answer 6===		===Answer 6===
	~~''Answer here''~~		The article is very interesting and a project management-practitioner or -academic will inevitably work with the topic "Project Life Cycle". But since the topic is so generic this article/deliverable is not a [[significant]] contribution beyond a cursory web search - The topic of "Project Life Cycle" is discussed thoroughly in many project management textbooks and webpages. However, dealing with the Project Life Cycle is a relevant practice for all project managers.

	===Question 7 · TEXT===		===Question 7 · TEXT===
Line 191:		Line 197:

	===Answer 7===		===Answer 7===
	'~~'Answer here''~~		The article cites and acknowledges previous work, and refers even to other APPPM wiki pages which I liked. In Annotated Bibliography there has been referred to the PMBOK as a book that explains in details the Life Cycle Model, but it doesn't say where (which chapter/page(s)). Remember to put references in the figures as well.

Ugur: /* Feedback 1 | Reviewer name: Ugur Erman */

2018-02-19T20:56:34Z

Feedback 1 | Reviewer name: Ugur Erman

← Older revision		Revision as of 20:56, 19 February 2018
Line 20:		Line 20:

	===Answer 1===		===Answer 1===
	''The different points of the abstract are clear and there is a reference to one of the mandatory references (PMBOK guide). My main concern with the abstract is that it might sound a bit generic and it can be difficult to see how it is relevant for a project manager (the topic itself is relevant).''		''The different points of the abstract are clear and there is a reference to one of the mandatory references (PMBOK guide). My main concern with the abstract is that it might sound a bit generic and it can be difficult to see how it is relevant for a project manager (the topic itself is relevant and the rest of the article shows relevance).''

	===Question 2 · TEXT===		===Question 2 · TEXT===
Line 36:		Line 36:

	===Answer 2===		===Answer 2===
	''The argument is clear and I like the flow of the article, especially in the Big Idea section where the author splits the article into theory, example, theory, example etc. ''		''The argument is clear and I like the flow of the article, especially in the Big Idea section where the author splits the article into theory, example, theory, example etc. The flow also makes sure that one part builds upon the other. I find the article consistent in its argument and free of contradictions.''

			''One suggestion I will make is that a more is written and discussed in the '''Applications''' and '''Limitations''' sections.''

	===Question 3 · TEXT===		===Question 3 · TEXT===
Line 48:		Line 50:

	===Answer 3===		===Answer 3===
	''~~Answer here~~''		''I find the language precise and without unnecessary fill words. I did not really find grammatical and spelling error. The only thing I will suggest is that more commas are inserted in the text as it will make it easier to read.''

			''I did however notice in the section about '''Planning: Organizing and preparing''' that something can be changed. The author lists several points and in point 3 where several planning softwares are mentioned, there are three dots (...) just after OpenProj. I am not certain whether the dots are written as a way of saying etc. but if they are, I will suggest that etc. or among others (or something like that) is written.''

	===Question 4 · TEXT===		===Question 4 · TEXT===
Line 60:		Line 64:

	===Answer 4===		===Answer 4===
	''~~Answer here~~''		''There are no tables but 2 figures. Both figures have decent sizes and while the text in figure 1 can be read, the text in figure 2 is blurry. I will suggest that both figures (especially figure 2) are self-explanatory, meaning that the figures should be described a bit more in depth in the text just under the figure.''

	===Question 5 · TEXT===		===Question 5 · TEXT===
Line 72:		Line 76:

	===Answer 5===		===Answer 5===
	''~~Answer here~~''		''The article is definitely relevant and it is made clear multiple times that a project manager can make use of the tools described in the article.''

	===Question 6 · TEXT===		===Question 6 · TEXT===
Line 84:		Line 88:

	===Answer 6===		===Answer 6===
	''~~Answer here~~''		''The article is interesting for a practitioner or academic and I think it makes several points about several things. The author has also shown critical thinking e.g. in the section where the planning software has been discussed.''

	===Question 7 · TEXT===		===Question 7 · TEXT===
Line 98:		Line 102:

	===Answer 7===		===Answer 7===
	''~~Answer here~~''		''The article does properly cite and acknowledge previous work and key references are summarized at the end. One thing I will suggest is that a little more is written about the references listed in the '''Annotated Bibliography''' section.''

	==Feedback 2 \| Reviewer name: ''Seyed (Habib) Bahrami''==		==Feedback 2 \| Reviewer name: ''Seyed (Habib) Bahrami''==

Ugur: /* Feedback 1 | Reviewer name: Ugur Erman */

2018-02-19T18:11:25Z

Feedback 1 | Reviewer name: Ugur Erman

← Older revision		Revision as of 18:11, 19 February 2018
Line 20:		Line 20:

	===Answer 1===		===Answer 1===
	''~~Answer here~~''		''The different points of the abstract are clear and there is a reference to one of the mandatory references (PMBOK guide). My main concern with the abstract is that it might sound a bit generic and it can be difficult to see how it is relevant for a project manager (the topic itself is relevant).''

	===Question 2 · TEXT===		===Question 2 · TEXT===
Line 36:		Line 36:

	===Answer 2===		===Answer 2===
	''~~Answer here~~''		''The argument is clear and I like the flow of the article, especially in the Big Idea section where the author splits the article into theory, example, theory, example etc. ''

	===Question 3 · TEXT===		===Question 3 · TEXT===

BaptisteH: /* Feedback 1 | Reviewer name: Ugur Eman */

2018-02-19T15:06:10Z

Feedback 1 | Reviewer name: Ugur Eman

← Older revision		Revision as of 15:06, 19 February 2018
Line 11:		Line 11:


	==Feedback 1 \| Reviewer name: ''Ugur ~~Eman~~''==		==Feedback 1 \| Reviewer name: ''Ugur Erman''==
	===Question 1 · TEXT===		===Question 1 · TEXT===
	'''Quality of the summary:'''		'''Quality of the summary:'''

BaptisteH: /* Abstract Feedback */

2018-02-19T15:03:50Z

Abstract Feedback

Show changes

S122906: Created page with "==Abstract Feedback== Text Clarity; Ok. Language; Ok. References; Ok. In general the abstract is ok, but try avoid a too generic article, when developing the article don't ..."

2018-02-12T07:42:43Z

Created page with "==Abstract Feedback== Text Clarity; Ok. Language; Ok. References; Ok. In general the abstract is ok, but try avoid a too generic article, when developing the article don't ..."

New page

==Abstract Feedback==
Text Clarity; Ok.

Language; Ok.

References; Ok.

In general the abstract is ok, but try avoid a too generic article, when developing the article don't forget to elaborate and describe the relevance for a Project Manager.

Try to find other relevant references and see if there are new approaches.