Talk:Critical chain project management (CCPM) - Revision history

Mathilso: /* Review made by s152093, reviewer 2 */

2015-09-28T06:41:06Z

Review made by s152093, reviewer 2

← Older revision		Revision as of 06:41, 28 September 2015
Line 115:		Line 115:
	==Review made by s152093, reviewer 2==		==Review made by s152093, reviewer 2==
	*A really good article. I learned a lot from it, and the specific comments I have to the article are details.		*A really good article. I learned a lot from it, and the specific comments I have to the article are details.
			** Answer: Thank you for this review, and this very nice words.

	*The language is clear, and there is a natural flow of the language. Good references. It does say in the description of the project though that we have to “Summarize and outline the relevance of each reference to the topic”. This I can’t see anywhere.		*The language is clear, and there is a natural flow of the language. Good references. It does say in the description of the project though that we have to “Summarize and outline the relevance of each reference to the topic”. This I can’t see anywhere.
			** Answer: Have made a bibliography for the four most important references.

	*There are a few typos here and there.		*There are a few typos here and there.
	*A little too long History section for my taste.		*A little too long History section for my taste.
			** Answer: Tried to shorten the biography-part up.

	*Good introduction to the methodological basis, so that all the important tools and concepts are ready to be used for the explanation.		*Good introduction to the methodological basis, so that all the important tools and concepts are ready to be used for the explanation.
	*The drawing in “Core principles” could be included in the explanation to make it even more clear.		*The drawing in “Core principles” could be included in the explanation to make it even more clear.
			** Answer: Thank you, tried to use the drawing more efficient.

	*The example in “Creating a CCPM schedule” is good, but it is confusing that one example is described in text and another is shown in figure. It would be nice to have nice two aligned.		*The example in “Creating a CCPM schedule” is good, but it is confusing that one example is described in text and another is shown in figure. It would be nice to have nice two aligned.
	*Nice example with Japan, that really shows the strength of the method.		*Nice example with Japan, that really shows the strength of the method.
	*Where it makes sense, it would be nice with some links to other Wiki-articles.		*Where it makes sense, it would be nice with some links to other Wiki-articles.
	*It is a little hard to tell your opinion apart from statements from literature, even with the various references that you have.		*It is a little hard to tell your opinion apart from statements from literature, even with the various references that you have.
			** Answer: Tried to make this more clear.

	*Are there really not any limitations to the theory? You point out that a critical path is needed for the CCPM to be made, and that the success is measured compared to previous very unstructured projects, and therefore its success is a little skewed. But isn’t there any more limitations to it than that?		*Are there really not any limitations to the theory? You point out that a critical path is needed for the CCPM to be made, and that the success is measured compared to previous very unstructured projects, and therefore its success is a little skewed. But isn’t there any more limitations to it than that?
			** Answer: Tried to add some more limitations, thank you.

	*So as mentioned, all in all a very good article, and the comments I have made are almost all of them details :-)		*So as mentioned, all in all a very good article, and the comments I have made are almost all of them details :-)
			** Answer: Thank you very much!

Mathilso: /* Review of the content */

2015-09-28T06:32:48Z

Review of the content

← Older revision		Revision as of 06:32, 28 September 2015
Line 109:		Line 109:
	* It provides a good understanding of the tool and real life examples (Japan section)		* It provides a good understanding of the tool and real life examples (Japan section)
	* Sometimes it is a bit difficult to differentiate between statements from literature and own opinion		* Sometimes it is a bit difficult to differentiate between statements from literature and own opinion
	** Tried to make this more clear, however I don´t use subjectives like "I think..." in the text because I don´t think that fits into a wiki-article.		** Answer: Tried to make this more clear, however I don´t use subjectives like "I think..." in the text because I don´t think that fits into a wiki-article.
	* Good summary of advantages and disadvantages with . However, I would add some more limitations and/or how to overcome them. I would also suggest to add some bullet points or bold format to differentiate the sub-parts.		* Good summary of advantages and disadvantages with . However, I would add some more limitations and/or how to overcome them. I would also suggest to add some bullet points or bold format to differentiate the sub-parts.
	** Thank you for the tip, tried to add some more limitations. I also split up the benefits, limitations and conclusion.		** Answer: Thank you for the tip, tried to add some more limitations. I also split up the benefits, limitations and conclusion.

	==Review made by s152093, reviewer 2==		==Review made by s152093, reviewer 2==

Mathilso: /* Review of S141926, Reviewer 3 */

2015-09-28T06:32:18Z

Review of S141926, Reviewer 3

← Older revision		Revision as of 06:32, 28 September 2015
Line 82:		Line 82:
	== Review of S141926, Reviewer 3 ==		== Review of S141926, Reviewer 3 ==
	I think it is a good and well written article about Critical Chain Project Management, providing a good understanding of the method in a clear and well-structured way.		I think it is a good and well written article about Critical Chain Project Management, providing a good understanding of the method in a clear and well-structured way.

			Answer: Thank you, and thanks for the good review.


	=== General formal aspects ===		=== General formal aspects ===
Line 88:		Line 91:
	* Good reference notation and format.		* Good reference notation and format.
	* When mentioning methods/concepts that have a Wikipedia article it might be a good idea to link them.		* When mentioning methods/concepts that have a Wikipedia article it might be a good idea to link them.
			** Answer: Thank you for the tip, have made two links.

	* Grammatically correct with good punctuation and use of technical vocabulary. However, I could read some informal contractions that under my point of view should be avoided in this sort of writing.		* Grammatically correct with good punctuation and use of technical vocabulary. However, I could read some informal contractions that under my point of view should be avoided in this sort of writing.

Line 94:		Line 99:
	* The article covers successfully the course requirements for a method article. Good description, application and limitations by giving a number of reliable references well notated throughout the whole article.		* The article covers successfully the course requirements for a method article. Good description, application and limitations by giving a number of reliable references well notated throughout the whole article.
	* Under my point of view, the history part is too long and maybe irrelevant here. I think there is too much personal information about Eliyahu M. Goldratt that might not be much relevant for the purpose of the article. Personally, I would not add his portrait :)		* Under my point of view, the history part is too long and maybe irrelevant here. I think there is too much personal information about Eliyahu M. Goldratt that might not be much relevant for the purpose of the article. Personally, I would not add his portrait :)
			** Answer: Tried to shorten up the biography.

	* The core principles are very well defined, using technical and precise language. Without too long and unnecessary sentences. If I had to suggest something it would be adding text formatting before starting the description of each factor (like bold titles).		* The core principles are very well defined, using technical and precise language. Without too long and unnecessary sentences. If I had to suggest something it would be adding text formatting before starting the description of each factor (like bold titles).
			** Answer: Thank you for this tip, have tried to make some more subtitles and space through the text.

	* Nice and useful illustrations that make more understandable the process and the article more attractive to the reader		* Nice and useful illustrations that make more understandable the process and the article more attractive to the reader
	* The length of the article seems appropriate and covers all the requirements of the method-article under my point of view. There is a good continuity throughout the article and under my point of view not unnecessary long sentences.		* The length of the article seems appropriate and covers all the requirements of the method-article under my point of view. There is a good continuity throughout the article and under my point of view not unnecessary long sentences.
Line 100:		Line 109:
	* It provides a good understanding of the tool and real life examples (Japan section)		* It provides a good understanding of the tool and real life examples (Japan section)
	* Sometimes it is a bit difficult to differentiate between statements from literature and own opinion		* Sometimes it is a bit difficult to differentiate between statements from literature and own opinion
			** Tried to make this more clear, however I don´t use subjectives like "I think..." in the text because I don´t think that fits into a wiki-article.
	* Good summary of advantages and disadvantages with . However, I would add some more limitations and/or how to overcome them. I would also suggest to add some bullet points or bold format to differentiate the sub-parts.		* Good summary of advantages and disadvantages with . However, I would add some more limitations and/or how to overcome them. I would also suggest to add some bullet points or bold format to differentiate the sub-parts.
			** Thank you for the tip, tried to add some more limitations. I also split up the benefits, limitations and conclusion.

	==Review made by s152093, reviewer 2==		==Review made by s152093, reviewer 2==

Mathilso: /* Review of Sorth90 (Rasmus Sorth-Olsen s117422), Reviewer 1 */

2015-09-28T06:21:54Z