Talk:Managing start-ups in Unregulated Markets - Revision history

Iga: /* Abstract Feedback */

2018-02-20T08:33:25Z

Abstract Feedback

← Older revision		Revision as of 08:33, 20 February 2018
Line 22:		Line 22:
	<li> Ensure depth of the article so it contributes to the project management community more than a normal web search		<li> Ensure depth of the article so it contributes to the project management community more than a normal web search
	</ol>		</ol>



			==Feedback 1 \| Reviewer name: ''Iga''==
			===Question 1 · TEXT===
			'''Quality of the summary:'''

			Does the summary make the key focus, insights and/or contribution of the article clear?
			Yes, it gives a good background and introduction to the topic.

			What would you suggest to improve?

			===Answer 1===
			''Yes, it gives a good background and introduction to the topic. However it does not clearly state what the article will focus on. Maybe the methods described later on, e.g. SWOT analysis should be mentioned in the introduction. The theme is clearly introduce however it is not clear on which aspect of it the article is going to focus on.''

			===Question 2 · TEXT===
			'''Structure and logic of the article:'''

			Is the argument clear?

			Is there a logical flow to the article?

			Does one part build upon the other?

			Is the article consistent in its argument and free of contradictions?

			What would you suggest to improve?

			===Answer 2===
			''The topic is clear, although it may be a little more precise. The flow between the topics is fluent. In my opinion, the article lacks clear structure. After reading an introduction I am not sure what to expect. To make it a little more scientific maybe introduction of some examples, e.g. what are those risk factors for new start-ups, how can they be categorised, etc. would make it more clear.''

			===Question 3 · TEXT===
			'''Grammar and style:'''

			Is the writing free of grammatical and spelling errors?

			Is the language precise without unnecessary fill words?

			What would you suggest to improve?

			===Answer 3===
			''In general it is very good. Try being a little bit more specific. Some small mistakes (e.g. using 'what' instead of 'which').''

			===Question 4 · TEXT===
			'''Figures and tables:'''

			Are figures and tables clear?

			Do they summarize the key points of the article in a meaningful way?

			What would you suggest to improve?

			===Answer 4===
			''No figures yet.''

			===Question 5 · TEXT===
			'''Interest and relevance:'''

			Is the article of high practical and / or academic relevance?

			Is it made clear in the article why / how it is relevant?

			What would you suggest to improve?

			===Answer 5===
			''The article is very practical and it describes very up-to-date problem, which many young engineers face. The relevance of the article is obvious.''

			===Question 6 · TEXT===
			'''Depth of treatment:'''

			Is the article interesting for a practitioner or academic to read?

			Does it make a significant contribution beyond a cursory web search?

			What would you suggest to improve?

			===Answer 6===
			''It is very interesting and difficult topic since there are no clear answers and patterns. Maybe try being more specific to make it look more scientific.''

			===Question 7 · TEXT===
			'''Annotated bibliography:'''

			Does the article properly cite and acknowledge previous work?

			Does it briefly summarize the key references at the end of the article?

			Is it based on empirical data instead of opinion?

			What would you suggest to improve?

			===Answer 7===
			''It is ok.''

Hani Mike Rae Selim: /* Abstract Feedback */

2018-02-14T08:18:27Z

Abstract Feedback

← Older revision		Revision as of 08:18, 14 February 2018
Line 7:		Line 7:
	'''Description of the tool/theory/concept''' Difficult to follow - what concept/theory/tool is exactly being described here? Project management is too generic		'''Description of the tool/theory/concept''' Difficult to follow - what concept/theory/tool is exactly being described here? Project management is too generic

	'''Purpose explanation''' Notes: Avoid using a case study (~~concurrency~~) - the course requirements changed - do not use a case study		'''Purpose explanation''' Notes: Avoid using a case study (cryptocurrency) - the course requirements changed - do not use a case study
	<ol>		<ol>
	<li> Avoid using a case study (concurrency) - the course requirements changed - do not use a case study		<li> Avoid using a case study (concurrency) - the course requirements changed - do not use a case study

Hani Mike Rae Selim: /* Abstract Feedback */

2018-02-14T08:17:50Z

Abstract Feedback

← Older revision		Revision as of 08:17, 14 February 2018
Line 11:		Line 11:
	<li> Avoid using a case study (concurrency) - the course requirements changed - do not use a case study		<li> Avoid using a case study (concurrency) - the course requirements changed - do not use a case study
	<li> Avoid creating a new concept to project management without consulting/agreeing with Josef		<li> Avoid creating a new concept to project management without consulting/agreeing with Josef
	<li> Who is the reader? Project Manager or ~~Sponsor~~ etc?		<li> Who is the reader? Project Manager or team etc?
	</ol>		</ol>

Hani Mike Rae Selim: Created page with "==Abstract Feedback== '''Text clarity''' Good '''Language''' Minor errors e.g. writing "is fits" when "fits" is required '''Description of the tool/theory/concept''..."

2018-02-14T08:17:38Z

Created page with "==Abstract Feedback== '''Text clarity''' Good '''Language''' Minor errors e.g. writing "is fits" when "fits" is required '''Description of the tool/theory/concept''..."

New page

==Abstract Feedback==

'''Text clarity''' Good

'''Language''' Minor errors e.g. writing "is fits" when "fits" is required

'''Description of the tool/theory/concept''' Difficult to follow - what concept/theory/tool is exactly being described here? Project management is too generic

'''Purpose explanation''' Notes: Avoid using a case study (concurrency) - the course requirements changed - do not use a case study
<ol>
<li> Avoid using a case study (concurrency) - the course requirements changed - do not use a case study
<li> Avoid creating a new concept to project management without consulting/agreeing with Josef
<li> Who is the reader? Project Manager or Sponsor etc?
</ol>

'''References''' Missing appropriate references to mandatory list of references

'''Relevance of article''' Consider the following:

<ol>
<li> Try linking to a knowledge area e.g. "Project Human Resource Management"
<li> Ensure depth of the article so it contributes to the project management community more than a normal web search
</ol>