Talk:PRINCE2, A Project Management Methodology - Revision history

S103745 at 13:04, 24 September 2015

2015-09-24T13:04:31Z

← Older revision		Revision as of 13:04, 24 September 2015
Line 59:		Line 59:
	But very nice work otherwise!		But very nice work otherwise!

	<pre style="color: red">These to comments cover the same ~~thing~~, ~~Review~~ 2 had a similar comment,		<pre style="color: red">These to comments cover the same aspect, review 2 had a similar comment about this.
	~~the~~ listing and titling for the article has been changed according to ~~his~~ review.</pre>		The listing and titling for the article has been changed according to review 2.</pre>

	* One small typo : "this element us a core concept		* One small typo : "this element us a core concept

	<pre style="color: red">'''Us''' has been changed to '''As'''</pre>		<pre style="color: red">'''Us''' has been changed to '''As'''</pre>

S103745: /* Reviewer n°1 - s141074 */

2015-09-24T08:38:16Z

Reviewer n°1 - s141074

← Older revision		Revision as of 08:38, 24 September 2015
Line 59:		Line 59:
	But very nice work otherwise!		But very nice work otherwise!

	<pre style="color: red">~~The last~~ to comments cover the same thing, ~~Reviewer~~ 2 had a similar comment, the listing and titling for the article has been changed according to his review.</pre>		<pre style="color: red">These to comments cover the same thing, Review 2 had a similar comment,
			the listing and titling for the article has been changed according to his review.</pre>

	* One small typo : "this element us a core concept		* One small typo : "this element us a core concept

	<pre style="color: red">'''Us''' has been changed to '''As'''</pre>		<pre style="color: red">'''Us''' has been changed to '''As'''</pre>

S103745: /* Reviewer n°1 - s141074 */

2015-09-24T08:37:17Z

Reviewer n°1 - s141074

← Older revision		Revision as of 08:37, 24 September 2015
Line 52:		Line 52:
	* The first picture is blurry (and probably copyrighted)		* The first picture is blurry (and probably copyrighted)

	*<pre style="color: red"> I have fixed the blurry picture, and provided a reference for ~~the~~ copyright reason,		*<pre style="color: red"> I have fixed the blurry picture, and provided a reference for copyright reason.
	the figures 2-5 is made me my self but references for those are also provided</pre>		the figures 2-5 is made me my self but references for those are also provided</pre>

S103745: /* Stucture */

2015-09-24T08:36:36Z

Stucture

← Older revision		Revision as of 08:36, 24 September 2015
Line 32:		Line 32:
	* I also think that it needs conclusion in the end. There is so much information in the article that it is hard to grasp without finalising it all together.		* I also think that it needs conclusion in the end. There is so much information in the article that it is hard to grasp without finalising it all together.

	<pre style="color: red">Same point was mentioned by the first ~~reviewer~~, and this has been changed according to has comment.</pre>		<pre style="color: red">Same point was mentioned by the first review, and this has been changed according to has comment.</pre>

	* Language is good in the article, I didn't find grammar mistakes. But of course it's good to do final checking one more time.		* Language is good in the article, I didn't find grammar mistakes. But of course it's good to do final checking one more time.

S103745 at 08:35, 24 September 2015

2015-09-24T08:35:28Z

← Older revision		Revision as of 08:35, 24 September 2015
Line 9:		Line 9:
	* It is exactly the same remark for the "Overview of Themes". Put this in one big part with small bold titles. It will enable an easier reading.		* It is exactly the same remark for the "Overview of Themes". Put this in one big part with small bold titles. It will enable an easier reading.

	<pre style="color: red">The titles of this article are different, elements as a ~~big title~~ and descriptions as a ~~subtitle~~.		<pre style="color: red">The titles of this article are different, elements as a level 1 titles and descriptions as a subtitles.
	i think it is more structured and shows that there are different subparts in a element,		i think it is more structured and shows that there are different subparts in a element,
	if i had summarized everything under one title, the reader will maybe think that there is only one principle and not 7.		if i had summarized everything under one title, the reader will maybe think that there is only one principle and not 7.

S103745: /* Stucture */

2015-09-24T08:33:35Z

Stucture

← Older revision		Revision as of 08:33, 24 September 2015
Line 31:		Line 31:

	* I also think that it needs conclusion in the end. There is so much information in the article that it is hard to grasp without finalising it all together.		* I also think that it needs conclusion in the end. There is so much information in the article that it is hard to grasp without finalising it all together.

			<pre style="color: red">Same point was mentioned by the first reviewer, and this has been changed according to has comment.</pre>

	* Language is good in the article, I didn't find grammar mistakes. But of course it's good to do final checking one more time.		* Language is good in the article, I didn't find grammar mistakes. But of course it's good to do final checking one more time.

S103745 at 08:31, 24 September 2015

2015-09-24T08:31:57Z

← Older revision		Revision as of 08:31, 24 September 2015
Line 16:		Line 16:

	* For the scalability, I would like to know a bit more or make it more concrete. It is a frustration you have created to me since your article is well written and interesting :)		* For the scalability, I would like to know a bit more or make it more concrete. It is a frustration you have created to me since your article is well written and interesting :)
			* A conclusion is missing. All in all, 3000 words are a lot, so we need to have a kind of summary at the very end. Just bring all we have learnt through the article together and explicit the way you have built it.
			But again, I want to tell you that I appreciated reading your article, it is well written, clear and understandable. You have definitely almost finished ;)


	<pre style="color: red"></pre>		<pre style="color: red">The Scalability section is now more concrete and a conclusion is provided at the end of the article, thank you for the useful feedbacks</pre>

	* A conclusion is missing. All in all, 3000 words are a lot, so we need to have a kind of summary at the very end. Just bring all we have learnt through the article together and explicit the way you have built it.
	~~But again, I want to tell you that I appreciated reading your article, it is well written, clear and understandable. You have definitely almost finished ;)~~


Line 50:		Line 50:
	* The first picture is blurry (and probably copyrighted)		* The first picture is blurry (and probably copyrighted)

	*<pre style="color: red"> I have fixed the blurry picture, and provided a reference</pre>		*<pre style="color: red"> I have fixed the blurry picture, and provided a reference for the copyright reason,
			the figures 2-5 is made me my self but references for those are also provided</pre>

	* You can make a list in the Methods and Applicability part		* You can make a list in the Methods and Applicability part
			* You should rework the hierarchy, it is sometimes hard to follow (you should use "==" for your main titles rather than "=".
			But very nice work otherwise!

			<pre style="color: red">The last to comments cover the same thing, Reviewer 2 had a similar comment, the listing and titling for the article has been changed according to his review.</pre>

	* One small typo : "this element us a core concept		* One small typo : "this element us a core concept

	* You should rework the hierarchy, it is sometimes hard to follow (you should use "==" ~~for your main titles rather than~~ "~~=".~~		<pre style="color: red">'''Us''' has been changed to '''As'''</pre>
	~~But very nice work otherwise!~~

S103745 at 07:21, 24 September 2015

2015-09-24T07:21:07Z

← Older revision		Revision as of 07:21, 24 September 2015
Line 7:		Line 7:
	* In the overview of principles, you should summarize all the paragraphs since the big titles just cut the text so some readers may lose the track. If you use another figure summarizing your elements, and explain it in this part, that would be perfect.		* In the overview of principles, you should summarize all the paragraphs since the big titles just cut the text so some readers may lose the track. If you use another figure summarizing your elements, and explain it in this part, that would be perfect.

	~~<text style=~~"~~color: red~~"~~>The titles of~~ this ~~article is different, elements as a~~ big ~~title and descriptions as a subtitle~~. ~~i think it gives us more structure and shows that there are different subparts in a element, if i had summarized everything in principle overview, the reader~~ will ~~maybe think that there is only one principle</text>~~		* It is exactly the same remark for the "Overview of Themes". Put this in one big part with small bold titles. It will enable an easier reading.

			<pre style="color: red">The titles of this article are different, elements as a big title and descriptions as a subtitle.
			i think it is more structured and shows that there are different subparts in a element,
			if i had summarized everything under one title, the reader will maybe think that there is only one principle and not 7.
			But i have changed all the titles and i hope that my changes can keep the reader on track. </pre>

	* It is exactly the same remark for the "Overview of Themes". Put this in one big part with small bold titles. It will enable an easier reading.

	* For the scalability, I would like to know a bit more or make it more concrete. It is a frustration you have created to me since your article is well written and interesting :)		* For the scalability, I would like to know a bit more or make it more concrete. It is a frustration you have created to me since your article is well written and interesting :)


			<pre style="color: red"></pre>

	* A conclusion is missing. All in all, 3000 words are a lot, so we need to have a kind of summary at the very end. Just bring all we have learnt through the article together and explicit the way you have built it.		* A conclusion is missing. All in all, 3000 words are a lot, so we need to have a kind of summary at the very end. Just bring all we have learnt through the article together and explicit the way you have built it.

S103745 at 06:32, 24 September 2015

2015-09-24T06:32:53Z

S103745 at 21:05, 23 September 2015

2015-09-23T21:05:12Z

← Older revision		Revision as of 21:05, 23 September 2015
Line 1:		Line 1:
	Anna: Nice article choice, and nice to see that you have chosen a specific method. Remember to include the elements listed in the requirements in your structure, such as the limitations of the method for example.		Anna: Nice article choice, and nice to see that you have chosen a specific method. Remember to include the elements listed in the requirements in your structure, such as the limitations of the method for example.

			<pre style="color: red">I will reply to the reviews in red color text</pre>

	<u>Gaetangarnotel - Reviewer n°2</u><br/>		<u>Gaetangarnotel - Reviewer n°2</u><br/>
	First of all, I think that it is a really good work. You met all the main requirements and succeeded in making me understand the method clearly. In particular, I like the fact that you have put a lot of pictures so w can also visually understand what you have written. Yet, I have some advice that I may kindly give you to be even better:		First of all, I think that it is a really good work. You met all the main requirements and succeeded in making me understand the method clearly. In particular, I like the fact that you have put a lot of pictures so w can also visually understand what you have written. Yet, I have some advice that I may kindly give you to be even better:
	* In the overview of principles, you should summarize all the paragraphs since the big titles just cut the text so some readers may lose the track. If you use another figure summarizing your elements, and explain it in this part, that would be perfect.		* In the overview of principles, you should summarize all the paragraphs since the big titles just cut the text so some readers may lose the track. If you use another figure summarizing your elements, and explain it in this part, that would be perfect.

			<pre style="color: red">....</pre>


	* It is exactly the same remark for the "Overview of Themes". Put this in one big part with small bold titles. It will enable an easier reading.		* It is exactly the same remark for the "Overview of Themes". Put this in one big part with small bold titles. It will enable an easier reading.
	* For the scalability, I would like to know a bit more or make it more concrete. It is a frustration you have created to me since your article is well written and interesting :)		* For the scalability, I would like to know a bit more or make it more concrete. It is a frustration you have created to me since your article is well written and interesting :)
Line 25:		Line 31:

	*Very nicely made article about method that I personally didn't have much information about.		*Very nicely made article about method that I personally didn't have much information about.


	=Reviewer n°1 - s141074=		=Reviewer n°1 - s141074=
Line 31:		Line 38:
	And quickly, a very few formal aspects:		And quickly, a very few formal aspects:
	* The first picture is blurry (and probably copyrighted)		* The first picture is blurry (and probably copyrighted)
			*<pre style="color: red"> I have fixed the blurry picture, and provided a reference</pre>
	* You can make a list in the Methods and Applicability part		* You can make a list in the Methods and Applicability part
	* One small typo : "this element us a core concept		* One small typo : "this element us a core concept
	* You should rework the hierarchy, it is sometimes hard to follow (you should use "==" for your main titles rather than "=".		* You should rework the hierarchy, it is sometimes hard to follow (you should use "==" for your main titles rather than "=".
	But very nice work otherwise!		But very nice work otherwise!

← Older revision		Revision as of 06:32, 24 September 2015
Line 7:		Line 7:
	* In the overview of principles, you should summarize all the paragraphs since the big titles just cut the text so some readers may lose the track. If you use another figure summarizing your elements, and explain it in this part, that would be perfect.		* In the overview of principles, you should summarize all the paragraphs since the big titles just cut the text so some readers may lose the track. If you use another figure summarizing your elements, and explain it in this part, that would be perfect.

	<~~pre~~ style="color: red">.~~...~~</~~pre~~>		<text style="color: red">The titles of this article is different, elements as a big title and descriptions as a subtitle. i think it gives us more structure and shows that there are different subparts in a element, if i had summarized everything in principle overview, the reader will maybe think that there is only one principle</text>


	* It is exactly the same remark for the "Overview of Themes". Put this in one big part with small bold titles. It will enable an easier reading.		* It is exactly the same remark for the "Overview of Themes". Put this in one big part with small bold titles. It will enable an easier reading.

	* For the scalability, I would like to know a bit more or make it more concrete. It is a frustration you have created to me since your article is well written and interesting :)		* For the scalability, I would like to know a bit more or make it more concrete. It is a frustration you have created to me since your article is well written and interesting :)

	* A conclusion is missing. All in all, 3000 words are a lot, so we need to have a kind of summary at the very end. Just bring all we have learnt through the article together and explicit the way you have built it.		* A conclusion is missing. All in all, 3000 words are a lot, so we need to have a kind of summary at the very end. Just bring all we have learnt through the article together and explicit the way you have built it.
	But again, I want to tell you that I appreciated reading your article, it is well written, clear and understandable. You have definitely almost finished ;)		But again, I want to tell you that I appreciated reading your article, it is well written, clear and understandable. You have definitely almost finished ;)
Line 21:		Line 23:

	* The article is very nicely made. It starts from the method and progress step by step explaining what the article is about. The reader can easily understand what the article is about.		* The article is very nicely made. It starts from the method and progress step by step explaining what the article is about. The reader can easily understand what the article is about.

	* I also think that it needs conclusion in the end. There is so much information in the article that it is hard to grasp without finalising it all together.		* I also think that it needs conclusion in the end. There is so much information in the article that it is hard to grasp without finalising it all together.

	* Language is good in the article, I didn't find grammar mistakes. But of course it's good to do final checking one more time.		* Language is good in the article, I didn't find grammar mistakes. But of course it's good to do final checking one more time.

Line 37:		Line 41:
	This article is very interesting, I didn't know much about PRINCE2 before, I feel I have learn a lot, but I am a bit frustrated of not understanding how to use it. But that is partly due to the Wiki style. For a Wiki article, the style is excellent, but for a newbie to PRINCE2 like me, I miss an example that could guide me throughout the presentation. Or at least you could say how companies adapt it to their needs or example of successful implementation with external links. The pictures are very good as well, I just have one small concern, are you sure that they are not copyrighted?		This article is very interesting, I didn't know much about PRINCE2 before, I feel I have learn a lot, but I am a bit frustrated of not understanding how to use it. But that is partly due to the Wiki style. For a Wiki article, the style is excellent, but for a newbie to PRINCE2 like me, I miss an example that could guide me throughout the presentation. Or at least you could say how companies adapt it to their needs or example of successful implementation with external links. The pictures are very good as well, I just have one small concern, are you sure that they are not copyrighted?
	And quickly, a very few formal aspects:		And quickly, a very few formal aspects:

	* The first picture is blurry (and probably copyrighted)		* The first picture is blurry (and probably copyrighted)

	*<pre style="color: red"> I have fixed the blurry picture, and provided a reference</pre>		*<pre style="color: red"> I have fixed the blurry picture, and provided a reference</pre>

	* You can make a list in the Methods and Applicability part		* You can make a list in the Methods and Applicability part

	* One small typo : "this element us a core concept		* One small typo : "this element us a core concept

	* You should rework the hierarchy, it is sometimes hard to follow (you should use "==" for your main titles rather than "=".		* You should rework the hierarchy, it is sometimes hard to follow (you should use "==" for your main titles rather than "=".
	But very nice work otherwise!		But very nice work otherwise!