Talk:Gantt Chart
| Line 1: | Line 1: | ||
Kristine: | Kristine: | ||
Great to see you have found a relevant tool to describe. Good to see you have the structure of the article all figured out. | Great to see you have found a relevant tool to describe. Good to see you have the structure of the article all figured out. | ||
| + | |||
| + | '''Reviewer 1, 150477''' | ||
| + | |||
| + | The article has been accessed the 22/09/2015 at 21 p.m. | ||
| + | |||
| + | Overall overview. | ||
| + | |||
| + | The presentation and the overall writing are very clear and clean. The article is well organised and structured with the big idea, tools used in Gantt chart, one simple example and the limitations. It is also completed, with 3000 words. Even without any knowledge of the subject, it becomes accessible through the article. | ||
| + | |||
| + | Formal aspect. | ||
| + | |||
| + | No mistakes noticed, the vocabulary is very precise and the formal aspect of the Wiki seems to me perfectly mastered. The references and the links inside the article are well used in order to explain technical aspect through other pages. However, the parts could be more balanced between a really big first part “Use” and the others which are smaller, especially “Application”. | ||
| + | |||
| + | Schemas and photos | ||
| + | |||
| + | They are clearly identified and used in harmony within the text. Maybe a picture for illustrate easily what is a critical path can improve the comprehension of this technical notion. Maybe a picture of a Gantt on MS Project can improve the part “Application”. | ||
| + | |||
| + | Links, connections and comprehension. | ||
| + | |||
| + | The article describes the subject in a logical way with description, application, example and limitation. It is a method description so the structure choice makes perfect sense to me. Maybe you can describe farther the software used for Gantt chart to ensure people who will read your article that is a really useful tool. | ||
| + | |||
| + | Bibliography | ||
| + | |||
| + | The references seem to be very serious one. The explanations for each reference are developed. Maybe one or two more can be better. | ||
| + | |||
| + | Conclusion and advices: | ||
| + | |||
| + | From my very own point of view the subject is perfectly explained and presented. It is easy to understand and it is important with this topic so basic in Project Management. If the part “Application is more developed with descriptions of software used and one picture, it will become more interesting. The use of examples really simple is perfect to understand Gantt chart in Project Management. | ||
| + | The actual formal presentation is perfectly acceptable and describes the Gantt chart in a logical way. | ||
Revision as of 20:24, 22 September 2015
Kristine: Great to see you have found a relevant tool to describe. Good to see you have the structure of the article all figured out.
Reviewer 1, 150477
The article has been accessed the 22/09/2015 at 21 p.m.
Overall overview.
The presentation and the overall writing are very clear and clean. The article is well organised and structured with the big idea, tools used in Gantt chart, one simple example and the limitations. It is also completed, with 3000 words. Even without any knowledge of the subject, it becomes accessible through the article.
Formal aspect.
No mistakes noticed, the vocabulary is very precise and the formal aspect of the Wiki seems to me perfectly mastered. The references and the links inside the article are well used in order to explain technical aspect through other pages. However, the parts could be more balanced between a really big first part “Use” and the others which are smaller, especially “Application”.
Schemas and photos
They are clearly identified and used in harmony within the text. Maybe a picture for illustrate easily what is a critical path can improve the comprehension of this technical notion. Maybe a picture of a Gantt on MS Project can improve the part “Application”.
Links, connections and comprehension.
The article describes the subject in a logical way with description, application, example and limitation. It is a method description so the structure choice makes perfect sense to me. Maybe you can describe farther the software used for Gantt chart to ensure people who will read your article that is a really useful tool.
Bibliography
The references seem to be very serious one. The explanations for each reference are developed. Maybe one or two more can be better.
Conclusion and advices:
From my very own point of view the subject is perfectly explained and presented. It is easy to understand and it is important with this topic so basic in Project Management. If the part “Application is more developed with descriptions of software used and one picture, it will become more interesting. The use of examples really simple is perfect to understand Gantt chart in Project Management. The actual formal presentation is perfectly acceptable and describes the Gantt chart in a logical way.
Wiki feedback from s117318
- Nice figures, great references
- Be more specific for your topics. Fx. USE? Use of what? Edit the topic/headlines.
- Could you make even more topic? 1. Use 1.1 Dependencies... 1.2 Critical Path.. 1.3 Ects...
- Need discussion, maybe you could add more to the last topic "limitations"
- Be more specific: For instance, Here is an example of how to use. Could you be more concrete? Avoid words like "here"
- Great example, simple and easy to understand
- I think you can add some more text!
- Nice you are using the figures in your article.
- Your language is easy to understand, great work.
Wiki feedback from s142823
- Globally a nice article,well structured.
- Layout pleasant
- Some minor Grammatical mistakes
- Good idea to illustrate what is written with some GANTT pictures. However, maybe you should choose pictures easier to understand quickly.
- About the “Example of Managing a project with Gantt Charts”, it would be interesting to describe the all process more in detail with more illustrations such as one for the WBS
- Good presentation of references
