Talk:Agile project management

From apppm
(Difference between revisions)
Jump to: navigation, search
(Answer 3)
(Answer 4)
Line 58: Line 58:
  
 
===Answer 4===
 
===Answer 4===
''I think the pictures are place a good and are related with the arcticule, however you know that you haven't finish yet and should put more pictures. But good choise of picture, they are easy to understand.''
+
''I think the pictures are place a good and are related with the article, however i beleive that there is a lack of picture, the author should introduce more pictures, only 1 picture and the article is to dense in terms of concepts, with pictures and drawings will be easier the concepts of the articule. But good choise of picture, they are easy to understand.''
  
 
===Question 5 · ===
 
===Question 5 · ===

Revision as of 20:41, 18 February 2018

Contents

Abstract Feedback

Text Clarity; Ok.

Language; Ok.

References; missing references related to the standards

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

Feedback 1 | Reviewer name: Daniel Campos Rivera

Question 1 ·

Quality of the summary:

Does the summary make the key focus, insights and/or contribution of the article clear?

What would you suggest to improve?

Answer 1

Good summary. It is very clear what you are going to tell about Agile Project Management, you have developed a good argument discussion related with the summary

Question 2

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

Nice explanation of the Agile Project Managment. Good flow is well organized and synteshised, . The article has a nice flow. Very nice with links and the biography of the references, maybe should be like a small example to illustrate the concept.

Question 3 ·

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

No grammar or spelling mistakes i think so. Good language and I could understand the whole idea, however i am not the best to speak in this topic i am spanish native speaker .

Question 4 ·

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

I think the pictures are place a good and are related with the article, however i beleive that there is a lack of picture, the author should introduce more pictures, only 1 picture and the article is to dense in terms of concepts, with pictures and drawings will be easier the concepts of the articule. But good choise of picture, they are easy to understand.

Question 5 ·

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

It has academic relevance nevertheless practical relevance should be reflected more directly in the text "

Question 6 ·

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

There is a lot about Risk Management on the internet, PMBOOK Project Management Book is a good guide to work in civil engineering project and is to early to think that is significant contribution because the author haven't finished yet

Question 7 ·

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

Yes there is prOperly citing. It is based on data. Nice with the annotated bibliography.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox