Talk:The Sprint Methodology in Agile Project Management
(→Answer 3) |
|||
| Line 148: | Line 148: | ||
===Answer 3=== | ===Answer 3=== | ||
| − | ''Overall impression is really good. Text is consistent and transparent. I would recommend to avoid too long sentences. Reader may looses the context and get confused. Example : | + | ''Overall impression is really good. Text is consistent and transparent. I would recommend to avoid too long sentences. Reader may looses the context and get confused. Example : |
* Secondly, the feedback loop created by these short iterations facilitates the direct communication with partners during the development process avoiding unnecessary documentation and bureaucracy. | * Secondly, the feedback loop created by these short iterations facilitates the direct communication with partners during the development process avoiding unnecessary documentation and bureaucracy. | ||
* The meetings are short and informal leaving no room for problem solving or thorough explanations, hence the importance of standing up during these meetings, which can help the team being focused and removing obstacles to progress. | * The meetings are short and informal leaving no room for problem solving or thorough explanations, hence the importance of standing up during these meetings, which can help the team being focused and removing obstacles to progress. | ||
| − | + | Secendly, punctuation should be carefully used : | |
*...maximum four weeks, is, that no external...'' | *...maximum four weeks, is, that no external...'' | ||
| + | |||
| + | You need watch out also for the repetition, especially :...scope,time... | ||
| + | |||
| + | When you use abbreviations, they should be introduced first : DSLC | ||
===Question 4 · TEXT=== | ===Question 4 · TEXT=== | ||
Latest revision as of 21:39, 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 |
[edit] Feedback 1 | Reviewer name: Oliver Adam Mølskov Bech
[edit] 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?
[edit] Answer 1
The abstract introduces the reader to the key topic of this article, the "Sprint Methodology", proceeding to discuss its importance and relevance within agile project management. The last two sentences of the abstract clearly define the scope and aim of the article. Overall, a good abstract/summary, however the language could be improved (discussed further in question 3).
[edit] 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?
[edit] Answer 2
Overall, the argument is clear and the structure of the article is logical to follow. The article introduces agile project management and then digs deeper into scrum and sprint management. This allows one part to build upon the next. However, I would consider moving the "Motivation" section before the "Agile Project Management" section. Additionally, I would consider inserting more sub-topics to guide the reader and categorise the article into different elements. For example, "Scrum and Sprint Management" is one heading, I as a reader, would personally have preferred two headings clearly introducing me to the "Scrum Process" and subsequently the "Sprint Methodology" as this would have made it more clear that the sprint activity is a part of the scrum process. Furthermore, adding more headings to your article will also make it easier for the reader to navigate through the table of contents to immediately locate sections relevant to him/her.
[edit] 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?
[edit] Answer 3
The writing is to a high quality, however there is room for improvement in terms and grammar and language. Some suggestions of improvement are:
- Under "Abstract": using the word "evident" in the sentence, "which makes agile project management an evident way", does not make sense. Perhaps the word you are looking for is "appropriate" or "suitable"?
- Revise the first sentence under "Abstract". This sentence is fairly unclear and it is important to not confuse the reader from the off-set.
- Good syntax and consistency in terms of referencing, however there is one small error in reference [5] under "Motivation".
- Change the word generically to generally under "Motivation". Generically means "not specifically".
- Be consistent with using capital case throughout the text, for example, "Scrum" is sometimes capital and other times not.
- These are minor issues but worth noting nonetheless.
[edit] 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?
[edit] Answer 4
Figures are very clear and of a high quality. They effectively summarise and support the article discussion. I would however suggest placing the pictures in a more systematic manner, some appear on the right side while other figures appear on the left side.
[edit] 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?
[edit] Answer 5
The article is very interesting and has both practical and academic relevance. The motivation and abstract make it clear why the sprint methodology process is relevant in agile project management. Also discussing additional benefits of the procedure. I do not have any suggestions of improvement in terms of interest and relevance as I was highly engaged while reading your first draft.
[edit] 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?
[edit] Answer 6
The article is interesting for both practitioners in industry and academics alike. It makes a detailed contribution beyond a web search, using highly academic references. I would suggest researching whether there is any mention of agile project management in the ISO guidelines.
[edit] 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?
[edit] Answer 7
The article uses proper citation and syntax throughout. However, there is no annotated bibliography and it is thus hard for the reader to understand the relevance and topics associated with each citation.
[edit] Feedback 2 | Reviewer name: Radoslaw Tyczynski
[edit] 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?
[edit] Answer 1
The Abstract provides clear insights of the article and explains the concept. Nicely introduces area of focus and defines its contribution in management.
[edit] 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?
[edit] Answer 2
The article has a logical flow and while reading the sequence of the paragraphs is understandable. Previous chapters are the fundamentals for the following ones. As far as the article was written there are no contradictions. It is clearly stated what will be the focus on.
Suggestion : Dividing the article into more chapters could improve transparency.However, keeping in as it is will not decrease the value.
[edit] 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?
[edit] Answer 3
Overall impression is really good. Text is consistent and transparent. I would recommend to avoid too long sentences. Reader may looses the context and get confused. Example :
- Secondly, the feedback loop created by these short iterations facilitates the direct communication with partners during the development process avoiding unnecessary documentation and bureaucracy.
- The meetings are short and informal leaving no room for problem solving or thorough explanations, hence the importance of standing up during these meetings, which can help the team being focused and removing obstacles to progress.
Secendly, punctuation should be carefully used :
- ...maximum four weeks, is, that no external...
You need watch out also for the repetition, especially :...scope,time...
When you use abbreviations, they should be introduced first : DSLC
[edit] 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?
[edit] Answer 4
Presented figures find their reflection in the text, supporting arguments and enriching the article. They are helpful in understanding the topic and do not overwhelm the written part. '
Unstructured way of having figures add dynamic to the article, but some may find it differently.
[edit] Question 5 · TEXT
Interest and relevance:
Is the article of high practical and / or academic relevance?
The article is of high practical and academic relevance
Is it made clear in the article why / how it is relevant?
What would you suggest to improve?
[edit] Answer 5
The article is of high practical and academic relevance regarding IT and software related projects. In the early stage of the article the importance of this topic is shown and through the rest of the text it is well proven
[edit] 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?
[edit] Answer 6
The article is interesting to read and provides proper insight the project regarding IT and software. Author uses different sources and make a contribution beyond a cursory web search.
Suggestion: would be nice to see reference from the real life case of application the tool :)
[edit] 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?
[edit] Answer 7
Annotated bibliography does not exist yet. What has been prepared so far is based on knowledgeable sources, which clearly support the topic.
