Talk:Project Portfolio Management Vs. Programme Management - Revision history

Linus R.V: /* Review of content */

2014-12-02T12:18:02Z

Review of content

← Older revision		Revision as of 12:18, 2 December 2014
Line 89:		Line 89:

	* The length of the article seems appropriate for the subjects mentioned. The text is sufficiently dense without any unneeded extra material. I imagine though that there are a lot of related subjects that could be relevant to present and/or familiarize the reader with along the way. Methods, tools, theories etc.		* The length of the article seems appropriate for the subjects mentioned. The text is sufficiently dense without any unneeded extra material. I imagine though that there are a lot of related subjects that could be relevant to present and/or familiarize the reader with along the way. Methods, tools, theories etc.
	Thank you, and yes indeed		Thank you, and yes indeed. For keeping the attention on the distinction i chose to keep the focus on Programme and Project Portfolio Management

	* I miss referencing to the figures in the text, linking specific areas of interest to the accompanying figure.		* I miss referencing to the figures in the text, linking specific areas of interest to the accompanying figure.

Linus R.V: /* Review of formal aspects */

2014-12-02T02:52:32Z

Review of formal aspects

← Older revision		Revision as of 02:52, 2 December 2014
Line 102:		Line 102:

	* The article is very well referenced throughout. Relies a bit heavily on direct citations of paragraphs. Could be interesting to have the author reflect on the meaning of these citations, compare them etc. in order to hold the reader's hand along the way.		* The article is very well referenced throughout. Relies a bit heavily on direct citations of paragraphs. Could be interesting to have the author reflect on the meaning of these citations, compare them etc. in order to hold the reader's hand along the way.
	as i ~~wrote in the other review~~, ~~my view is that a discussion of definition and standards would increase the complexity of the article~~		i changed some minor parts, i am not sure on which various points.
	* I find the written style structured and very informative, which gives the impression of a solid scientific approach. At various points in the article it could be advised to simplify the style, making it easier to read and less "clunky"/"stiff". Engage the reader a bit more, without losing the content delivery out of sight.		* I find the written style structured and very informative, which gives the impression of a solid scientific approach. At various points in the article it could be advised to simplify the style, making it easier to read and less "clunky"/"stiff". Engage the reader a bit more, without losing the content delivery out of sight.
	Thanks. Various points could be more specific :)		Thanks. Various points could be more specific :)

Linus R.V: /* “Project Portfolio Management” */

2014-12-02T01:31:25Z

“Project Portfolio Management”

← Older revision		Revision as of 01:31, 2 December 2014
Line 57:		Line 57:

	=== “Project Portfolio Management” ===		=== “Project Portfolio Management” ===
	*I think it should be explained where the key factors come from e.g. a simple reference.		*I think it should be explained where the key factors come from e.g. a simple reference.
			see previous answer

	=== “Interface” ===		=== “Interface” ===

Linus R.V: /* “Program Management” */

2014-12-02T01:29:26Z

“Program Management”

← Older revision		Revision as of 01:29, 2 December 2014
Line 49:		Line 49:
	*I find it a bit difficult to understand the following text: “The distinction between a Project and a Program is given by the benefits which a Program provides over and above those that projects can archive on their own, such as exposure, prioritisation, more efficient use of resources and better alignment with other projects”. I think the idea of describing the difference between a project and a programme is great, so if you could just		*I find it a bit difficult to understand the following text: “The distinction between a Project and a Program is given by the benefits which a Program provides over and above those that projects can archive on their own, such as exposure, prioritisation, more efficient use of resources and better alignment with other projects”. I think the idea of describing the difference between a project and a programme is great, so if you could just

	In my opinion it is important to outline the difference between projects and programmes also, since the section seek to define what a programme is. However has the sentence been shortened~~, as i~~ dont fully understand : I think the idea of describing the difference between a project and a programme is great, '''so if you could just '''		In my opinion it is important to outline the difference between projects and programmes also, since the section seek to define what a programme is. However has the sentence been shortened. I dont fully understand : I think the idea of describing the difference between a project and a programme is great, '''so if you could just '''

	*I think it should be explained where the key factors come from e.g. a simple reference.		*I think it should be explained where the key factors come from e.g. a simple reference.

Linus R.V: /* Feedback by Cruijff */

2014-12-02T01:27:43Z

Feedback by Cruijff

← Older revision		Revision as of 01:27, 2 December 2014
Line 70:		Line 70:

	= Feedback by Cruijff =		= Feedback by Cruijff =

			'''Thank you very much for a detailed review of the article, it helped me to improve the article further. '''

	tl;dr: A very solid article, encompassing clear relevant information in a structured manner. The core is there. If extra fluff and material engaging the reader is included it would take it up a level.		tl;dr: A very solid article, encompassing clear relevant information in a structured manner. The core is there. If extra fluff and material engaging the reader is included it would take it up a level.

Linus R.V: /* Feedback for "Project Portfolio Management Vs. Programme Management" by Dbdhl */

2014-12-02T01:26:18Z

Feedback for "Project Portfolio Management Vs. Programme Management" by Dbdhl

← Older revision		Revision as of 01:26, 2 December 2014
Line 1:		Line 1:
	= Feedback for "Project Portfolio Management Vs. Programme Management" by Dbdhl =		= Feedback for "Project Portfolio Management Vs. Programme Management" by Dbdhl =

	'''Thank you very much for a detailed review of the article, it helped me to improve the article further. ~~Even there are some points, were we dont agree :)~~ '''		'''Thank you very much for a detailed review of the article, it helped me to improve the article further. '''

	Overall it’s an interesting topic and article. The flow and read thread is great and meaningful. It’s a nice appetizer for going deeper into the subject.		Overall it’s an interesting topic and article. The flow and read thread is great and meaningful. It’s a nice appetizer for going deeper into the subject.

Linus R.V: /* Feedback for "Project Portfolio Management Vs. Programme Management" by Dbdhl */

2014-12-02T01:25:55Z

Feedback for "Project Portfolio Management Vs. Programme Management" by Dbdhl

← Older revision		Revision as of 01:25, 2 December 2014
Line 1:		Line 1:
	= Feedback for "Project Portfolio Management Vs. Programme Management" by Dbdhl =		= Feedback for "Project Portfolio Management Vs. Programme Management" by Dbdhl =

			'''Thank you very much for a detailed review of the article, it helped me to improve the article further. Even there are some points, were we dont agree :) '''

	Overall it’s an interesting topic and article. The flow and read thread is great and meaningful. It’s a nice appetizer for going deeper into the subject.		Overall it’s an interesting topic and article. The flow and read thread is great and meaningful. It’s a nice appetizer for going deeper into the subject.

Linus R.V: /* Feedback by Cruijff */

2014-12-02T01:23:52Z

Feedback by Cruijff

← Older revision		Revision as of 01:23, 2 December 2014
Line 70:		Line 70:

	tl;dr: A very solid article, encompassing clear relevant information in a structured manner. The core is there. If extra fluff and material engaging the reader is included it would take it up a level.		tl;dr: A very solid article, encompassing clear relevant information in a structured manner. The core is there. If extra fluff and material engaging the reader is included it would take it up a level.

			Thank you very much

	===Review of content===		===Review of content===

Linus R.V: /* “Program Management” */

2014-12-02T01:22:56Z

“Program Management”

← Older revision		Revision as of 01:22, 2 December 2014
Line 50:		Line 50:

	*I think it should be explained where the key factors come from e.g. a simple reference.		*I think it should be explained where the key factors come from e.g. a simple reference.

			First of all, i changed the word key factors to Differentiating factors, as key factors can give the reader a understanding of something that is generally valid.
			I see your point. In the section which i added: What is a standard. I pointed out that the article is based on the definitions of the standard for Programme and Portfolio Management of PMI. Further i pointed out that: The following distinctions are determined throughout the literature and best Practice as being the main differentiating factors of Programme Management Vs Project Portfolio Management.

	=== “Project Portfolio Management” ===		=== “Project Portfolio Management” ===

Linus R.V: /* “Program Management” */

2014-12-02T01:09:28Z

“Program Management”

← Older revision		Revision as of 01:09, 2 December 2014
Line 46:		Line 46:
	=== “Program Management” ===		=== “Program Management” ===
	*I find it a bit difficult to understand the following text: “The distinction between a Project and a Program is given by the benefits which a Program provides over and above those that projects can archive on their own, such as exposure, prioritisation, more efficient use of resources and better alignment with other projects”. I think the idea of describing the difference between a project and a programme is great, so if you could just		*I find it a bit difficult to understand the following text: “The distinction between a Project and a Program is given by the benefits which a Program provides over and above those that projects can archive on their own, such as exposure, prioritisation, more efficient use of resources and better alignment with other projects”. I think the idea of describing the difference between a project and a programme is great, so if you could just
	*I think it should be explained where the key factors come from e.g. a simple reference.
			In my opinion it is important to outline the difference between projects and programmes also, since the section seek to define what a programme is. However has the sentence been shortened, as i dont fully understand : I think the idea of describing the difference between a project and a programme is great, '''so if you could just '''

			*I think it should be explained where the key factors come from e.g. a simple reference.

	=== “Project Portfolio Management” ===		=== “Project Portfolio Management” ===