Talk:Work Breakdown Structure (WBS)
From apppm
(Difference between revisions)
| Line 43: | Line 43: | ||
* The introduction to the topic is really good | * The introduction to the topic is really good | ||
* The language and grammar of the article are fine but with some formulation mistakes. You have to read the article a few more times to correct the last of the grammar. For example ” no matter is the scope project, program or portfolio” | * The language and grammar of the article are fine but with some formulation mistakes. You have to read the article a few more times to correct the last of the grammar. For example ” no matter is the scope project, program or portfolio” | ||
| − | * | + | * Remember to put pictures that you mention into the article. That would make the article more reader-friendly |
* I think that the history section is to long. Maybe you could write the same information with fewer sentences | * I think that the history section is to long. Maybe you could write the same information with fewer sentences | ||
| + | * It is important that there aren o errors in your headlines. There are for example spelling errors in the headline ”Potential misunderstand, Disadventage and adventage” | ||
* You need to link your Wiki article to other Wiki articles | * You need to link your Wiki article to other Wiki articles | ||
* The article meets the requirement of the 3000 words | * The article meets the requirement of the 3000 words | ||
* It is good that you have different types of references | * It is good that you have different types of references | ||
Revision as of 22:14, 22 September 2015
Mette: I like your idea for a topic. I seems like you have a clear idea of what to write the article about and have remembered the structure for a "method article". Maybe you could short mention the Goal Breakdown Structure (GBS) in the article and outline the different.
Reviewer 1: s142581
- The topic was a wise choice, very relevant for practitioners and related to the course.
- Another positive aspect is that it follows the method structure.
- In addition, it has a good structure of sections and you did a good job with the references.
- I would suggest to separate the text into more paragraphs, especially in sections like History and Value breakdown structure. This way, you could improve the reading flow.
- Also, I recommend you to be careful with “,” and “.”. You should separate some sentences, for example:
- Moreover, during the project executions the percentage of steps completed must be included. This ensure better control and guidance in case of any changes during the project development.
- During 1962, United State Airforce released “STUDY OF METHODS FOR EVALUATION OF THE PERT/COST MANAGEMENT SYSTEM”. In this document WBS was mention as a useful tool for controlling and planning large acquisition projects.
- WBS could be considered a general tool that can be use in most of projects and program, due to this reason a WBS to another may vary to best adapts the project manager needs.
- Also, you should revise the grammar carefully. For example:
- must includes = must include
- since this tool is use = since this tool is used
- I would suggest that you transform the questions in the Main characteristics section into indirect questions.
- In addition, be careful with the paragraph spacing.
- You should introduce with a sentence the bullet points at the end of the Main characteristics section.
- I think you should rephrase the sentence “The most common method for decomposing a WBS are the following methods”. In addition, I recommend that you continue the explanation to every concept in the same line.
- Although you have noted “Picture under construction”, do not forget to numerate them and align them properly in the text. I would also suggest that you mention the figures in the text.
- I think you should use “:” after Nothing extra and Nothing Missing.
- Finally, correct the spelling of the words advantages and disadvantages in the last section title.
Reviewer 2: S102935
- Pros
- Highly relevant topic
- Follows the outlines for the course neatly
- Good overall structure of the article
- Good references
- I can see you intend to Include more figures and pictures to illustrate some of the main points of the article, which is good
- Missing formalities
- The annotated bibliography seem like an important part of the article, so remember to include annotations in your final article.
- A few grammatical errors, which unfortunately makes the article difficult to understand. These should be thinned out before the final hand-in, such as missing words and punctuation.
- Suggestions
- Try to link your subject to other articles, where work break down structure is used, such as scheduling, time and cost estimation etc.
- Remember to focus on keeping a logical flow between the chapters, so one part leads to the next.
- Reread your article to thin out grammatical errors.
- Remember to include the figures and mention them in the text with their associated number
Reviewer 3: AndreasAndersen
- The introduction to the topic is really good
- The language and grammar of the article are fine but with some formulation mistakes. You have to read the article a few more times to correct the last of the grammar. For example ” no matter is the scope project, program or portfolio”
- Remember to put pictures that you mention into the article. That would make the article more reader-friendly
- I think that the history section is to long. Maybe you could write the same information with fewer sentences
- It is important that there aren o errors in your headlines. There are for example spelling errors in the headline ”Potential misunderstand, Disadventage and adventage”
- You need to link your Wiki article to other Wiki articles
- The article meets the requirement of the 3000 words
- It is good that you have different types of references
