Talk:Dealing with conflict in project management
From apppm
(Difference between revisions)
(Created page with "==Abstract Feedback== '''Text clarity''' Good '''Language''' Good '''Description of the tool/theory/concept''' Relatively easy to grasp, but work still needs to be ...") |
(→Abstract Feedback) |
||
| Line 7: | Line 7: | ||
'''Description of the tool/theory/concept''' Relatively easy to grasp, but work still needs to be done to explain conflict in the context of project management to ensure reader understanding | '''Description of the tool/theory/concept''' Relatively easy to grasp, but work still needs to be done to explain conflict in the context of project management to ensure reader understanding | ||
| − | '''Purpose explanation''' Abstract is too short and | + | '''Purpose explanation''' Abstract is too short and can be improved: |
<ol> | <ol> | ||
<li> Who is the reader? Project manager or any project team member? | <li> Who is the reader? Project manager or any project team member? | ||
Revision as of 09:16, 14 February 2018
Abstract Feedback
Text clarity Good
Language Good
Description of the tool/theory/concept Relatively easy to grasp, but work still needs to be done to explain conflict in the context of project management to ensure reader understanding
Purpose explanation Abstract is too short and can be improved:
- Who is the reader? Project manager or any project team member?
- What will the reader learn/get out of reading the article?
- Briefly describe the structure of the article in the abstract to set reader expectations once there is a clearer picture of the article content
References Missing appropriate references to mandatory list of references
Relevance of article It is relevant. Consider the following:
- Try to link it to a knowledge area of project management (if that is the direction) e.g. Project Human Resource Management
- Ensure depth of the article so it contributes to the project/program/portfolio management community more than a normal web search
