Talk:Work Breakdown Structure in Construction Management
From apppm
(Difference between revisions)
(→Abstract Feedback) |
(→Abstract Feedback) |
||
| Line 7: | Line 7: | ||
'''Description of the tool/theory/concept''' Well addressed, but try to use the word "scope" in the abstract - as in a work breakdown structure is a tool used breakdown the scope of a project | '''Description of the tool/theory/concept''' Well addressed, but try to use the word "scope" in the abstract - as in a work breakdown structure is a tool used breakdown the scope of a project | ||
| − | '''Purpose explanation''' | + | '''Purpose explanation''' Well explained, but consider: |
<ol> | <ol> | ||
Revision as of 13:54, 16 February 2018
Abstract Feedback
Text clarity Text is good, but avoid writing bullet points in the abstract - the text should flow
Language Good
Description of the tool/theory/concept Well addressed, but try to use the word "scope" in the abstract - as in a work breakdown structure is a tool used breakdown the scope of a project
Purpose explanation Well explained, but consider:
- Who is the reader? Project Manager or team etc?
References Missing references to the list of mandatory references/standards
Relevance of article Consider the following:
- It is okay to use examples from the Metro Cityring project, but remember it is not allowed to write the article as a case study. The course requirements have changed
- Ensure depth of the article so it contributes to the project management community more than a normal web search
