Talk:The Gantt Chart - Revision history

S103183 at 20:04, 28 September 2015

2015-09-28T20:04:59Z

← Older revision		Revision as of 20:04, 28 September 2015
Line 85:		Line 85:
	==Replies to the comments from reviewers==		==Replies to the comments from reviewers==

	===Comments on the feedback from Reviewer 1:===		===Comments on the feedback from Reviewer 1===
	* Thanks for the kind words. I am aware that I use ”spoken language” too much when writing and I have done my best to change it for the final delivery.		* Thanks for the kind words. I am aware that I use ”spoken language” too much when writing and I have done my best to change it for the final delivery.
	* Thank you. I also felt it was a nice touch.		* Thank you. I also felt it was a nice touch.
Line 99:		Line 99:


	===Comments on the feedback from Reviewer 2:===		===Comments on the feedback from Reviewer 2===

	'''History of the Gantt Chart'''		'''History of the Gantt Chart'''
Line 138:		Line 138:


	===Comments on the feedback from Reviewer 3:===		===Comments on the feedback from Reviewer 3===
	* Thank you.		* Thank you.
	* I have added links to other wiki articles but not for Karol Adamiecki		* I have added links to other wiki articles but not for Karol Adamiecki

S103183 at 18:49, 27 September 2015

2015-09-27T18:49:18Z

@@ Line 1: / Line 1: @@
 Anna: I like your topic idea and that it focuses on a single project management tool. It also seem that you have read and understood the structure requirements.
-'''Review 1, Nannats''' <br>
+==Feedback from reviewers==
 Hi s103183 :-)
@@ Line 17: / Line 19: @@
-'''S113815, Review 2. [2206 words]'''
+===S113815, Review 2. [2206 words]===
 Dear S 103183.
@@ Line 65: / Line 67: @@
 All in all a very nice article – and good work. :)
-s140046 review 3
+===s140046 review 3===
 # Great introduction to article
@@ Line 78: / Line 80: @@
 #Fine with the annotated bibliography with descriptions.
 #Note that the reference list does not comply with the wikipedia standard - which is showing small reference numbers.

S140046 at 21:40, 22 September 2015

2015-09-22T21:40:14Z

← Older revision		Revision as of 21:40, 22 September 2015
Line 64:		Line 64:

	All in all a very nice article – and good work. :)		All in all a very nice article – and good work. :)

			s140046 review 3

			# Great introduction to article
			# You could easily add links to internal wiki-articles e.g. on Karol Adamiecki.
			# The history section tend to repeat a lot of the introduction.
			# Interesting quote by the project director [6] – It would be interesting to dig into that topic in a discussion section?
			# The article contains few spelling errors/typos which can easily be corrected
			# It would be interesting to know the process for creating a Gantt-chart. You could include Work-breakdown structures, network diagrams, critical path method etc. from the Project manager book.
			# There exist several types of interdependencies for tasks. It would be great to describe the different types of dependencies introduced.
			#I miss a description of slack/buffer and how it is visualized in the gantt chart.
			#I am not sure I follow the red line in the limitations overview. You argue that gantt chart is a blunt tool and describe how it ignore costs. From my perspective it is a visualization tool and has nothing to do with economics?
			#Fine with the annotated bibliography with descriptions.
			#Note that the reference list does not comply with the wikipedia standard - which is showing small reference numbers.

Nannats at 20:04, 22 September 2015

2015-09-22T20:04:49Z

← Older revision		Revision as of 20:04, 22 September 2015
Line 1:		Line 1:
	Anna: I like your topic idea and that it focuses on a single project management tool. It also seem that you have read and understood the structure requirements.		Anna: I like your topic idea and that it focuses on a single project management tool. It also seem that you have read and understood the structure requirements.

	'''Review 1, Nannats'''		'''Review 1, Nannats''' <br>
			Hi s103183 :-)

	* Generally, the whole article is easy to understand, which is nice. But be aware of the language do not become too much ’spoken’ language, and too long sentences.		* Generally, the whole article is easy to understand, which is nice. But be aware of the language do not become too much ’spoken’ language, and too long sentences.
Line 12:		Line 13:
	* I was a little confused about figure 3, so it might be an idea to explain what a predecessor activity and a successor activity is.		* I was a little confused about figure 3, so it might be an idea to explain what a predecessor activity and a successor activity is.
	* I think the video is god, but as your article is a bit short, you could consider writing the guide on how to create a Gantt Chart yourself.		* I think the video is god, but as your article is a bit short, you could consider writing the guide on how to create a Gantt Chart yourself.

			Keep up the good work :-)

S113815 at 19:47, 22 September 2015

2015-09-22T19:47:33Z

← Older revision		Revision as of 19:47, 22 September 2015
Line 12:		Line 12:
	* I was a little confused about figure 3, so it might be an idea to explain what a predecessor activity and a successor activity is.		* I was a little confused about figure 3, so it might be an idea to explain what a predecessor activity and a successor activity is.
	* I think the video is god, but as your article is a bit short, you could consider writing the guide on how to create a Gantt Chart yourself.		* I think the video is god, but as your article is a bit short, you could consider writing the guide on how to create a Gantt Chart yourself.


	'''S113815, Review 2. [2206 words]'''		'''S113815, Review 2. [2206 words]'''

	Dear S 103183.		Dear S 103183.


	After reviewing your article, I have following comments:		After reviewing your article, I have following comments:
	First of all, I think the article is consistently well-written and explains a tool which is very useful in the field of project management. There structure of the article seems to follow the guidelines from the assignment.		First of all, I think the article is consistently well-written and explains a tool which is very useful in the field of project management. There structure of the article seems to follow the guidelines from the assignment.
Line 55:		Line 58:
	* As you still have 800 words to use, you might consider a longer “Limitations”-part. Or maybe an extra example to strengthen your theory.		* As you still have 800 words to use, you might consider a longer “Limitations”-part. Or maybe an extra example to strengthen your theory.
	* Be careful not to use “spoken language” when you write		* Be careful not to use “spoken language” when you write


	All in all a very nice article – and good work. :)		All in all a very nice article – and good work. :)

S113815 at 19:47, 22 September 2015

2015-09-22T19:47:03Z

← Older revision		Revision as of 19:47, 22 September 2015
Line 12:		Line 12:
	* I was a little confused about figure 3, so it might be an idea to explain what a predecessor activity and a successor activity is.		* I was a little confused about figure 3, so it might be an idea to explain what a predecessor activity and a successor activity is.
	* I think the video is god, but as your article is a bit short, you could consider writing the guide on how to create a Gantt Chart yourself.		* I think the video is god, but as your article is a bit short, you could consider writing the guide on how to create a Gantt Chart yourself.

			'''S113815, Review 2. [2206 words]'''

			Dear S 103183.
			After reviewing your article, I have following comments:
			First of all, I think the article is consistently well-written and explains a tool which is very useful in the field of project management. There structure of the article seems to follow the guidelines from the assignment.

			I have made some comments and tried to make some suggestions to make the article even better, they are as followed:

			'''History of the Gantt Chart'''
			* … “during World War One and is today known as "the Gant Chart"[2]. “ You miss a t in Gantt. :)
			* “"I believe that computer-based project management has set the subject back 20 years". [6] “ You use a quote from a 14 years old article. Is that quote still relevant?

			'''Basic understanding'''

			* ..” The different activities can be dependent on one another which means that one activity may not begin before another activity has finished. This does not mean that multiple activities can not be worked on at the same time it merely means that some activities might be connected.” I guess that there are other dependencies than the “finish-start”. (https://www.google.dk/search?q=cpm+dependencies&rlz=1C1CHWL_da__638DK638&espv=2&biw=1366&bih=637&source=lnms&tbm=isch&sa=X&ved=0CAYQ_AUoAWoVChMIjcCmuKeLyAIVYzJyCh3RFwbl#imgrc=Huejzitp6md9JM%3A) Maybe you should consider explain the different types of dependencies?
			* “… can begin after a certain oercentage of its predecessor activity has been completed.” Typing error: percentage, not oercentage. :)

			'''The Gantt Chart in practice'''
			* I really like the figures. Nice and descriptive.
			* “It is grucial that the duration of each…” .” Typing error: crucial, not grucial. :)
			* Comment to figure 1: Where is the dependencies between the different task showed?
			* The last line in the explanation of figure 2 has dropped down below Figure 1. I think it would look better if it is placed below the rest of the text.
			* Figure 3 is very small compared to the others. Maybe another figure would be better here?
			* I think that it would be nice to add a section on how to use the Gantt Chart as control tool to monitor the projects, in terms of progress, stage reporting etc.

			'''Limitations'''
			* “It can get very complicated for big projects. Especially if it is on a computer where you have multiple pages of tasks etc. The more information the more bars, connecting lines, color codings etc. has to be put into the Gantt Chart. If you use a computer and the Gantt Chart takes up more space than a single screen it is quite easy to lose the overview thus making the Gantt Chart very hard to decipher”. How do you back this statement up? As far as I know, a lot of professional planners are using Gantt Charts to schedule large projects – also with success?
			* Another limitation could be the missing link to the location. The Gantt Chart don’t give an overview of processes and the location they are carried out. This might lead to conflicts. [See location-based scheduling].

			'''Tools for creating a Gantt Chart'''
			* I guess it is hard to make a detailed Gantt Chart schedule in Vison or Excel?
			* I think that the most used Gantt Chart program is Microsoft Project (you miss that on your list). All the construction companies I know uses this program.

			'''Conclusion, Annotated Bibliography, References'''
			* All these sections looks nice – no comments on them. :)

			'''General to the article'''
			* I found a couple of typing errors – I hopefully catch them all.
			* I think that your main points are well illustrated with figures. Thus, Figure 3 is a bit small.
			* I feel it is possible to add some internal links to other Wiki-articles. For example WBS. This is one of the points the teachers will look into (I guess).
			* As you still have 800 words to use, you might consider a longer “Limitations”-part. Or maybe an extra example to strengthen your theory.
			* Be careful not to use “spoken language” when you write

			All in all a very nice article – and good work. :)

Nannats at 18:36, 22 September 2015

2015-09-22T18:36:05Z

← Older revision		Revision as of 18:36, 22 September 2015
Line 1:		Line 1:
	Anna: I like your topic idea and that it focuses on a single project management tool. It also seem that you have read and understood the structure requirements.		Anna: I like your topic idea and that it focuses on a single project management tool. It also seem that you have read and understood the structure requirements.

			'''Review 1, Nannats'''

			* Generally, the whole article is easy to understand, which is nice. But be aware of the language do not become too much ’spoken’ language, and too long sentences.
			* I like the example with the light – also easy to understand :-)
			* I think it is good that you suggest real tools for creating Gantt Charts.
			* You mention The Critical Path Method, which is nice! You could consider to link to the Wiki article about the Critical path method. The same as for the WBS.
			* There are some spelling errors - watch out for these :-)
			* You should consider the layout of the sentence under figure 1 (''"to the Gantt Chart by using arrows as shown in Figure 3.”''), to make it easier for the reader to read.
			* The figure 2 is taking up a lot of space. Maybe you could remove some of the white frame in the figure.
			* I was a little confused about figure 3, so it might be an idea to explain what a predecessor activity and a successor activity is.
			* I think the video is god, but as your article is a bit short, you could consider writing the guide on how to create a Gantt Chart yourself.

AnnaGreve: Created page with "Anna: I like your topic idea and that it focuses on a single project management tool. It also seem that you have read and understood the structure requirements."

2015-09-16T14:28:07Z

Created page with "Anna: I like your topic idea and that it focuses on a single project management tool. It also seem that you have read and understood the structure requirements."

New page

Anna: I like your topic idea and that it focuses on a single project management tool. It also seem that you have read and understood the structure requirements.