Talk:Different sides of Project Management Scheduling
From apppm
(Difference between revisions)
(Created page with "==Abstract Feedback== '''Text clarity''' Text is coherent '''Language''' Minor errors e.g. writing "need" when "needed" is required. Do not use first person narrativ...") |
(→Abstract Feedback) |
||
| Line 12: | Line 12: | ||
<li> What will the reader get out of reading this? | <li> What will the reader get out of reading this? | ||
</ol> | </ol> | ||
| − | |||
'''References''' Missing appropriate references to mandatory list of references | '''References''' Missing appropriate references to mandatory list of references | ||
Revision as of 09:58, 14 February 2018
Abstract Feedback
Text clarity Text is coherent
Language Minor errors e.g. writing "need" when "needed" is required. Do not use first person narrative e.g. "we"
Description of the tool/theory/concept Okay, but go back to basics. Define what scheduling is and make references to appropriate standards. The abstract needs expansion
Purpose explanation Good, but can be improved:
- Consider explaining the structure and content of the article to align reader expectations
- What will the reader get out of reading this?
References Missing appropriate references to mandatory list of references
Relevance of article Consider the following:
- Who is the reader? Project Manager or Sponsor etc?
- Try linking to a knowledge area e.g. "Project Time Management"
- Ensure depth of the article so it contributes to the project management community more than a normal web search
