Talk:The Sprint Methodology in Agile Project Management

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 12: Line 12:
  
 
'''General'''          Good and clear structure. I would be cautious about including two big topics, risk management and agile project management, in one article. Remember that the article needs to be address a knowledge are in enough depth to be relevant and interesting for a project practitioner. I would clearly then frame it as risk management within the context of agile project management in the abstract and throughout the article - I can see you briefly did so, but try to make it crystal clear for the reader
 
'''General'''          Good and clear structure. I would be cautious about including two big topics, risk management and agile project management, in one article. Remember that the article needs to be address a knowledge are in enough depth to be relevant and interesting for a project practitioner. I would clearly then frame it as risk management within the context of agile project management in the abstract and throughout the article - I can see you briefly did so, but try to make it crystal clear for the reader
 +
 +
==Feedback 1 | Reviewer name: ''Oliver Adam Mølskov Bech''==
 +
===Question 1 · TEXT===
 +
'''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===
 +
''Answer here''
 +
 +
===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===
 +
''Answer here''
 +
 +
===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===
 +
''Answer here''
 +
 +
===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===
 +
''Answer here''
 +
 +
===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===
 +
''Answer here''
 +
 +
===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===
 +
''Answer here''
 +
 +
===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===
 +
''Answer here''
 +
 +
==Feedback 2 | Reviewer name: ''Place your name here''==
 +
===Question 1 · TEXT===
 +
'''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===
 +
''Answer here''
 +
 +
===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===
 +
''Answer here''
 +
 +
===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===
 +
''Answer here''
 +
 +
===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===
 +
''Answer here''
 +
 +
===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===
 +
''Answer here''
 +
 +
===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===
 +
''Answer here''
 +
 +
===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===
 +
''Answer here''

Revision as of 17:32, 19 February 2018

Text clarity The text sounds coherent

Language Good, but can be improved - e.g. what do you mean by "..ensures that the project continues being rentable?"

Description of the tool/theory/concept Good, but consider adding a brief one liner explaining what exactly agile project management is. Also, see my comment about risk management and how it fits in Agile Project Management under "General"

Purpose explanation Well addressed and the article structure is outlined, but who is your reader? Is it the project manager? Does this apply article apply to a specific industry?

Title of the Wiki Good title

References References seem valid, but research how you can appropriately reference the mandatory reference list suggested in the course. You don't have to reference all them, only the appropriate ones

General Good and clear structure. I would be cautious about including two big topics, risk management and agile project management, in one article. Remember that the article needs to be address a knowledge are in enough depth to be relevant and interesting for a project practitioner. I would clearly then frame it as risk management within the context of agile project management in the abstract and throughout the article - I can see you briefly did so, but try to make it crystal clear for the reader

Contents

Feedback 1 | Reviewer name: Oliver Adam Mølskov Bech

Question 1 · TEXT

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

Answer here

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

Answer here

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

Answer here

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

Answer here

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

Answer here

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

Answer here

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

Answer here

Feedback 2 | Reviewer name: Place your name here

Question 1 · TEXT

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

Answer here

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

Answer here

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

Answer here

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

Answer here

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

Answer here

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

Answer here

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

Answer here

Retrieved from "http://wiki.doing-projects.org/index.php?title=Talk:The_Sprint_Methodology_in_Agile_Project_Management&oldid=51566"
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox