Talk:Agile Project Management
Username111 (Talk | contribs) (→Review by Dunseiz) |
|||
| Line 12: | Line 12: | ||
== Review by Dunseiz == | == Review by Dunseiz == | ||
| + | '''''Answers to review by author (Username111) is written in bold/italic''''' | ||
This article is very well disposed and well argued. Good job! I have therefore focused my review on technical and formal stuff that in my opinion could lift the article. Enjoy :) | This article is very well disposed and well argued. Good job! I have therefore focused my review on technical and formal stuff that in my opinion could lift the article. Enjoy :) | ||
| Line 18: | Line 19: | ||
The references are done manually as far as I can see. I have taken the liberty and made reference 1 to 4 "linked" for you. No. 4 differs slightly in coding due to the multiple usage. They can be copied/pasted and modified to fit the rest of the references. | The references are done manually as far as I can see. I have taken the liberty and made reference 1 to 4 "linked" for you. No. 4 differs slightly in coding due to the multiple usage. They can be copied/pasted and modified to fit the rest of the references. | ||
| + | |||
| + | '''''Thank you for the example. I have corrected the referencing to be linked.''''' | ||
| Line 30: | Line 33: | ||
"...agile methodologies often don’t separate between..." should be "...agile methodologies often do not separate between..." | "...agile methodologies often don’t separate between..." should be "...agile methodologies often do not separate between..." | ||
"In many cases agile methodologies doesn’t even use..." should be "In many cases agile methodologies do not even use..." | "In many cases agile methodologies doesn’t even use..." should be "In many cases agile methodologies do not even use..." | ||
| + | |||
| + | '''''I have corrected all the word contractions to be separate words now''''' | ||
Revision as of 11:53, 27 November 2014
Review by secna
Overall a good article, which gives a good overview into what agile PM is and relevant within the topics of PM.
- It would improve the understanding of agile if you start out with a very short intro to what is agile PM is before you start the history of the method it will make it easier to follow.
- The amount of references that you have found is good, and when you read the article it really shows that it have been carefully investigated. But when you just write “it can be found in [x], then atleast I thought it was ruining the reading flow, I think it would help if you also added the name of the article that your referring to in the text.
- Is there any related methods/standards that can be used together with agile PM?
- Its nice figure which gives a good overview of the APM model, remember to refer to the figure in the text.
Review by Dunseiz
Answers to review by author (Username111) is written in bold/italic
This article is very well disposed and well argued. Good job! I have therefore focused my review on technical and formal stuff that in my opinion could lift the article. Enjoy :)
REFERENCES
The references are done manually as far as I can see. I have taken the liberty and made reference 1 to 4 "linked" for you. No. 4 differs slightly in coding due to the multiple usage. They can be copied/pasted and modified to fit the rest of the references.
Thank you for the example. I have corrected the referencing to be linked.
LAYOUT
There are many short sections in the introduction which can be a bit difficult to separate. This is mainly due to the line spacing when jumping to next line. Maybe you could use more sub-sub titles to separate these short sections or maybe just make an extra space between them?
GRAMMAR
word contractions are usually not used in written language. "...agile methodologies often don’t separate between..." should be "...agile methodologies often do not separate between..." "In many cases agile methodologies doesn’t even use..." should be "In many cases agile methodologies do not even use..."
I have corrected all the word contractions to be separate words now
