Talk:The Extreme Project Management approach - Revision history

Madrid at 17:34, 30 November 2014

2014-11-30T17:34:48Z

Madrid: /* Response to reviewers: */ new section

2014-11-30T15:42:21Z

Response to reviewers:: new section

← Older revision		Revision as of 15:42, 30 November 2014
Line 100:		Line 100:

	Article reads very concisely and fluently. Section orders have clearly been thought through and the English of the article is more than satisfactory. The article is lacking in references however, be sure to use these throughout the article. Also, again, the article could benefit from a little more argumentation. Overall though, great read.		Article reads very concisely and fluently. Section orders have clearly been thought through and the English of the article is more than satisfactory. The article is lacking in references however, be sure to use these throughout the article. Also, again, the article could benefit from a little more argumentation. Overall though, great read.

			== Response to reviewers: ==


			Hi,

			first of all, thank you very much for the feedback, it has been really useful and helpful.

			Since I think you both were right with your comments, I've taken all of them into account and made the proper changes.

			Note: with Keyser's feedback about my conclusion, instead of using 'Traditional vs Extreme' for it, I added more information that leads to final comments.
			I decided to keep 'Traditional vs Extreme' into its place because I think it's a key point that should be mentioned in the body of the article since I make references to this difference
			thereafter.

			Greetings!

Keyser-sözer: /* Review by Keyser */

2014-11-25T23:42:58Z

Review by Keyser

← Older revision		Revision as of 23:42, 25 November 2014
Line 67:		Line 67:
	== Review by Keyser ==		== Review by Keyser ==

	I have read through and edited grammar where necessary. Overall, the English of the article is very spot on, there are sporadic mistakes however they are few and far between.		I have read through and edited grammar where necessary. Overall, the English of the article is very spot on, there are sporadic mistakes however, they are few and far between.

	=== Abstract ===		=== Abstract ===

Keyser-sözer: /* = Conclusion */

2014-11-25T23:41:40Z

= Conclusion

← Older revision		Revision as of 23:41, 25 November 2014
Line 93:		Line 93:
	This section is a little unclear to me. Is this a section on how to use the tool, what criteria is needed to be an extreme project manager? Is it advice on how to use the tool? Are the tools that are being described related to the XPM approach? The two subsections should be reviewed to be more linked with XPM and the section could benefit from an introductory sentence or two.		This section is a little unclear to me. Is this a section on how to use the tool, what criteria is needed to be an extreme project manager? Is it advice on how to use the tool? Are the tools that are being described related to the XPM approach? The two subsections should be reviewed to be more linked with XPM and the section could benefit from an introductory sentence or two.

	=== Conclusion ==		=== Conclusion ===

	Conclusion seems a bit short. As mentioned earlier, linking more argumentation about which is better, XPM or traditional, would benefit the article highly.		Conclusion seems a bit short. As mentioned earlier, linking more argumentation about which is better, XPM or traditional, would benefit the article highly.

Keyser-sözer at 23:41, 25 November 2014

2014-11-25T23:41:30Z

← Older revision		Revision as of 23:41, 25 November 2014
Line 69:		Line 69:
	I have read through and edited grammar where necessary. Overall, the English of the article is very spot on, there are sporadic mistakes however they are few and far between.		I have read through and edited grammar where necessary. Overall, the English of the article is very spot on, there are sporadic mistakes however they are few and far between.

	== Abstract ==		=== Abstract ===

	Short and sweet, gets straight to the point. However, I would put the abstract before the contents to be consistent with the style of other Wikipedia articles.		Short and sweet, gets straight to the point. However, I would put the abstract before the contents to be consistent with the style of other Wikipedia articles.
Line 75:		Line 75:
	Introduction- I would rename this section 'what is project Management?' as this is only sentence included before the subsection. Would tidy up the body of the report slightly.		Introduction- I would rename this section 'what is project Management?' as this is only sentence included before the subsection. Would tidy up the body of the report slightly.

	== What is extreme project Management? ==		=== What is extreme project Management? ===

	*Review this section, I am confused by what you are trying to say. "Splitting the project’s functionality can save time and allow to achieve an overall improvement in the testing stage since more focus is put into each part of the project. Moreover, adjustments can be made on the fly without losing control of the overall process, schedule and positive outcome of the project."		*Review this section, I am confused by what you are trying to say. "Splitting the project’s functionality can save time and allow to achieve an overall improvement in the testing stage since more focus is put into each part of the project. Moreover, adjustments can be made on the fly without losing control of the overall process, schedule and positive outcome of the project."
Line 83:		Line 83:
	*Description of the tools and techniques is particularly strong, gives a clear understanding of XPM.		*Description of the tools and techniques is particularly strong, gives a clear understanding of XPM.

	== XPM Methodology ==		=== XPM Methodology ===

	*Traditional Vs Extreme- I like this as an argumentative section but perhaps it could be lengthened or moved. It seems like it would work as a good conclusion to the report.		*Traditional Vs Extreme- I like this as an argumentative section but perhaps it could be lengthened or moved. It seems like it would work as a good conclusion to the report.
Line 89:		Line 89:
	*Discussion of the XPM Methodology is strong again. Consistent with the previous section of the report and is clear and comprehensive.		*Discussion of the XPM Methodology is strong again. Consistent with the previous section of the report and is clear and comprehensive.

	== Extreme Project Managers ==		=== Extreme Project Managers ===

	This section is a little unclear to me. Is this a section on how to use the tool, what criteria is needed to be an extreme project manager? Is it advice on how to use the tool? Are the tools that are being described related to the XPM approach? The two subsections should be reviewed to be more linked with XPM and the section could benefit from an introductory sentence or two.		This section is a little unclear to me. Is this a section on how to use the tool, what criteria is needed to be an extreme project manager? Is it advice on how to use the tool? Are the tools that are being described related to the XPM approach? The two subsections should be reviewed to be more linked with XPM and the section could benefit from an introductory sentence or two.

	== Conclusion =		=== Conclusion ==

	Conclusion seems a bit short. As mentioned earlier, linking more argumentation about which is better, XPM or traditional, would benefit the article highly.		Conclusion seems a bit short. As mentioned earlier, linking more argumentation about which is better, XPM or traditional, would benefit the article highly.

	== Overall ==		=== Overall ===

	Article reads very concisely and fluently. Section orders have clearly been thought through and the English of the article is more than satisfactory. The article is lacking in references however, be sure to use these throughout the article. Also, again, the article could benefit from a little more argumentation. Overall though, great read.		Article reads very concisely and fluently. Section orders have clearly been thought through and the English of the article is more than satisfactory. The article is lacking in references however, be sure to use these throughout the article. Also, again, the article could benefit from a little more argumentation. Overall though, great read.

Keyser-sözer: /* Review by Keyser */ new section

2014-11-25T23:40:44Z

Review by Keyser: new section

← Older revision		Revision as of 23:40, 25 November 2014
Line 64:		Line 64:
	I myself am not an expert in English, I could not give you feedback on grammatical and punctuation errors.		I myself am not an expert in English, I could not give you feedback on grammatical and punctuation errors.
	I think your article is written in a very understandable and simple language. There have been a few places where I have been a little confused about what you meant, but overall it was very nice.		I think your article is written in a very understandable and simple language. There have been a few places where I have been a little confused about what you meant, but overall it was very nice.

			== Review by Keyser ==

			I have read through and edited grammar where necessary. Overall, the English of the article is very spot on, there are sporadic mistakes however they are few and far between.

			== Abstract ==

			Short and sweet, gets straight to the point. However, I would put the abstract before the contents to be consistent with the style of other Wikipedia articles.

			Introduction- I would rename this section 'what is project Management?' as this is only sentence included before the subsection. Would tidy up the body of the report slightly.

			== What is extreme project Management? ==

			*Review this section, I am confused by what you are trying to say. "Splitting the project’s functionality can save time and allow to achieve an overall improvement in the testing stage since more focus is put into each part of the project. Moreover, adjustments can be made on the fly without losing control of the overall process, schedule and positive outcome of the project."

			Their should be bullet points included to the concepts section. Adding an asterisk () will create a bullet point for you.

			*Description of the tools and techniques is particularly strong, gives a clear understanding of XPM.

			== XPM Methodology ==

			*Traditional Vs Extreme- I like this as an argumentative section but perhaps it could be lengthened or moved. It seems like it would work as a good conclusion to the report.

			*Discussion of the XPM Methodology is strong again. Consistent with the previous section of the report and is clear and comprehensive.

			== Extreme Project Managers ==

			This section is a little unclear to me. Is this a section on how to use the tool, what criteria is needed to be an extreme project manager? Is it advice on how to use the tool? Are the tools that are being described related to the XPM approach? The two subsections should be reviewed to be more linked with XPM and the section could benefit from an introductory sentence or two.

			== Conclusion =

			Conclusion seems a bit short. As mentioned earlier, linking more argumentation about which is better, XPM or traditional, would benefit the article highly.

			== Overall ==

			Article reads very concisely and fluently. Section orders have clearly been thought through and the English of the article is more than satisfactory. The article is lacking in references however, be sure to use these throughout the article. Also, again, the article could benefit from a little more argumentation. Overall though, great read.

HuHe: /* Some comments about the part below: */

2014-11-25T20:47:42Z

Some comments about the part below:

← Older revision		Revision as of 20:47, 25 November 2014
Line 43:		Line 43:

	''' avoid using "We", "I" ect.'''		''' avoid using "We", "I" ect.'''
	In order to prevent XPM seeming as though it is just a wrap of well-known techniques, '''we proceed''' to discuss the rules mentioned before (see ‘Description of XPM, tools and techniques’):
			''In order to prevent XPM seeming as though it is just a wrap of well-known techniques, '''we proceed''' to discuss the rules mentioned before (see ‘Description of XPM, tools and techniques’)''

	== Reference list ==		== Reference list ==

HuHe: /* Reference list */

2014-11-25T20:47:02Z

Reference list

← Older revision		Revision as of 20:47, 25 November 2014
Line 47:		Line 47:
	== Reference list ==		== Reference list ==

	You have a reference list, that is good but you have not specified where in the article you have used it up. You have important aspects of XPM in your article, it will be nice to refer it to a specific source by using bibliografy or any other type ~~of source is acknowledged~~		You have a reference list, that is good but you have not specified where in the article you have used it up. You have important aspects of XPM in your article, in order to make your article reliable and trustworthy, it will be nice to refer it to a specific source by using bibliografy, fodnote or any other type.

	you have refer to some books you have used for your article. That is really good and most trustworthy source.		you have refer to some books you have used for your article. That is really good and most trustworthy source.
Line 58:		Line 58:

	I really dont like your references for wikipedia. Personally I don't find information in wikipedia trustworthy		I really dont like your references for wikipedia. Personally I don't find information in wikipedia trustworthy



	==Feedback on grammatical- and punctuation errors==		==Feedback on grammatical- and punctuation errors==

HuHe: /* Some comments about the part below: */

2014-11-25T20:44:40Z

Some comments about the part below:

← Older revision		Revision as of 20:44, 25 November 2014
Line 41:		Line 41:
	''		''


			''' avoid using "We", "I" ect.'''
			In order to prevent XPM seeming as though it is just a wrap of well-known techniques, '''we proceed''' to discuss the rules mentioned before (see ‘Description of XPM, tools and techniques’):

	== Reference list ==		== Reference list ==

HuHe: /* Feedback on grammatical, spelling and punctuation errors */

2014-11-25T19:48:56Z

Feedback on grammatical, spelling and punctuation errors

← Older revision		Revision as of 19:48, 25 November 2014
Line 58:		Line 58:


	==Feedback on grammatical~~, spelling~~ and punctuation errors==		==Feedback on grammatical- and punctuation errors==

	I myself am not an expert in English, I could not give you feedback on grammatical and punctuation errors.		I myself am not an expert in English, I could not give you feedback on grammatical and punctuation errors.
	I think your article is written in a very understandable and simple language. There have been a few places where I have been a little confused about what you meant, but overall it was very nice.		I think your article is written in a very understandable and simple language. There have been a few places where I have been a little confused about what you meant, but overall it was very nice.

← Older revision		Revision as of 17:34, 30 November 2014
Line 6:		Line 6:
	you start your abstract by saying "Nowadays, '''many methodologies and tools''' are available when it comes to project management.......". It would be good if you name some of these methodologies and tools.		you start your abstract by saying "Nowadays, '''many methodologies and tools''' are available when it comes to project management.......". It would be good if you name some of these methodologies and tools.

			'''Done.'''


Line 16:		Line 17:
	'''I think it would give a better overview if you write it in bullet- points maybe like the exampel below?:'''		'''I think it would give a better overview if you write it in bullet- points maybe like the exampel below?:'''

	Extreme Project Management became the main recent approach utilized in project management, especially in the big software industry." To catch the readers attention, it would be nice if you could breifly describe why it become the main recent approach here in your summary.		Extreme Project Management became the main recent approach utilized in project management, especially in the big software industry." To catch the readers attention, it would be nice if you could breifly describe why it become the main recent approach here in your summary. '''Done.'''
	it will give a better overview if you write the following in bullet poiints_		it will give a better overview if you write the following in bullet poiints_ '''Done.'''
	"In order to implement XPM in a successful way, several criteria has to be taken into account such as:		"In order to implement XPM in a successful way, several criteria has to be taken into account such as:
	* Project and iteration’s scopes		* Project and iteration’s scopes
Line 30:		Line 31:
	ex: ABSTRACT: , INTRODUCTION TO EXTREME PROJECT MANAGEMENT:...... CONCLUSION. , REFERENCES.		ex: ABSTRACT: , INTRODUCTION TO EXTREME PROJECT MANAGEMENT:...... CONCLUSION. , REFERENCES.

	'''it will look better if you remove the unnecessary: and.'''		'''it will look better if you remove the unnecessary: and.''' '''Done.'''


Line 36:		Line 37:
	== Some comments about the part below: ==		== Some comments about the part below: ==

	'''I understand the following part as: XPM can only be used in execution phase and change control processes in projects, right? If so, than what about other phases of the project? is there any other project management tools you can use or combine XPM with, to support/ manage the remaining phases/processes?'''		'''I understand the following part as: XPM can only be used in execution phase and change control processes in projects, right? If so, than what about other phases of the project? is there any other project management tools you can use or combine XPM with, to support/ manage the remaining phases/processes?''' '''Done.'''

	''XPM methodology should only be applied during the project’s execution and change control processes instead of using it for vision, overall strategy or project prioritization. It helps including all stakeholders involved in the process in an active way.		''XPM methodology should only be applied during the project’s execution and change control processes instead of using it for vision, overall strategy or project prioritization. It helps including all stakeholders involved in the process in an active way.
Line 42:		Line 43:


	''' avoid using "We", "I" ect.'''		''' avoid using "We", "I" ect.''' '''Done.'''

	''In order to prevent XPM seeming as though it is just a wrap of well-known techniques, '''we proceed''' to discuss the rules mentioned before (see ‘Description of XPM, tools and techniques’)''		''In order to prevent XPM seeming as though it is just a wrap of well-known techniques, '''we proceed''' to discuss the rules mentioned before (see ‘Description of XPM, tools and techniques’)''
Line 48:		Line 49:
	== Reference list ==		== Reference list ==

	You have a reference list, that is good but you have not specified where in the article you have used it up. You have important aspects of XPM in your article, in order to make your article reliable and trustworthy, it will be nice to refer it to a specific source by using bibliografy, fodnote or any other type.		You have a reference list, that is good but you have not specified where in the article you have used it up. You have important aspects of XPM in your article, in order to make your article reliable and trustworthy, it will be nice to refer it to a specific source by using bibliografy, fodnote or any other type. '''Done.'''

	you have refer to some books you have used for your article. That is really good and most trustworthy source.		you have refer to some books you have used for your article. That is really good and most trustworthy source.

	To make it easy for your reader to find the book, I think it would be good if you dirctly refer to the book, insted of using links. So the reader has the opportunity to find the book if the link does not work.		To make it easy for your reader to find the book, I think it would be good if you dirctly refer to the book, insted of using links. So the reader has the opportunity to find the book if the link does not work. '''Done.'''



	you have few references to some websites, I think, it would be a good idea to write when you visited the site last time. Just in case, if the site content changes over time.		you have few references to some websites, I think, it would be a good idea to write when you visited the site last time. Just in case, if the site content changes over time. '''Done.'''

	I really dont like your references for wikipedia. Personally I don't find information in wikipedia trustworthy		I really dont like your references for wikipedia. Personally I don't find information in wikipedia trustworthy "I've deleted them because I didn't really used the information available there. However, it doesn't make sense not to use wikipedia references since what we are writing about it's a wiki article as well."

	==Feedback on grammatical- and punctuation errors==		==Feedback on grammatical- and punctuation errors==
Line 71:		Line 72:
	=== Abstract ===		=== Abstract ===

	Short and sweet, gets straight to the point. However, I would put the abstract before the contents to be consistent with the style of other Wikipedia articles.		Short and sweet, gets straight to the point. However, I would put the abstract before the contents to be consistent with the style of other Wikipedia articles. '''Done.'''

	Introduction- I would rename this section 'what is project Management?' as this is only sentence included before the subsection. Would tidy up the body of the report slightly.		Introduction- I would rename this section 'what is project Management?' as this is only sentence included before the subsection. Would tidy up the body of the report slightly. '''Done.'''

	=== What is extreme project Management? ===		=== What is extreme project Management? ===

	*Review this section, I am confused by what you are trying to say. "Splitting the project’s functionality can save time and allow to achieve an overall improvement in the testing stage since more focus is put into each part of the project. Moreover, adjustments can be made on the fly without losing control of the overall process, schedule and positive outcome of the project."		*Review this section, I am confused by what you are trying to say. "Splitting the project’s functionality can save time and allow to achieve an overall improvement in the testing stage since more focus is put into each part of the project. Moreover, adjustments can be made on the fly without losing control of the overall process, schedule and positive outcome of the project." '''Done.'''

	Their should be bullet points included to the concepts section. Adding an asterisk () will create a bullet point for you.		Their should be bullet points included to the concepts section. Adding an asterisk () will create a bullet point for you. '''Done.'''

	*Description of the tools and techniques is particularly strong, gives a clear understanding of XPM.		*Description of the tools and techniques is particularly strong, gives a clear understanding of XPM.
Line 85:		Line 86:
	=== XPM Methodology ===		=== XPM Methodology ===

	*Traditional Vs Extreme- I like this as an argumentative section but perhaps it could be lengthened or moved. It seems like it would work as a good conclusion to the report.		*Traditional Vs Extreme- I like this as an argumentative section but perhaps it could be lengthened or moved. It seems like it would work as a good conclusion to the report. '''See notes below'''

	*Discussion of the XPM Methodology is strong again. Consistent with the previous section of the report and is clear and comprehensive.		*Discussion of the XPM Methodology is strong again. Consistent with the previous section of the report and is clear and comprehensive.
Line 91:		Line 92:
	=== Extreme Project Managers ===		=== Extreme Project Managers ===

	This section is a little unclear to me. Is this a section on how to use the tool, what criteria is needed to be an extreme project manager? Is it advice on how to use the tool? Are the tools that are being described related to the XPM approach? The two subsections should be reviewed to be more linked with XPM and the section could benefit from an introductory sentence or two.		This section is a little unclear to me. Is this a section on how to use the tool, what criteria is needed to be an extreme project manager? Is it advice on how to use the tool? Are the tools that are being described related to the XPM approach? The two subsections should be reviewed to be more linked with XPM and the section could benefit from an introductory sentence or two. '''Fixed.'''

	=== Conclusion ===		=== Conclusion ===

	Conclusion seems a bit short. As mentioned earlier, linking more argumentation about which is better, XPM or traditional, would benefit the article highly.		Conclusion seems a bit short. As mentioned earlier, linking more argumentation about which is better, XPM or traditional, would benefit the article highly. '''See notes below.'''

	=== Overall ===		=== Overall ===

	Article reads very concisely and fluently. Section orders have clearly been thought through and the English of the article is more than satisfactory. The article is lacking in references however, be sure to use these throughout the article. Also, again, the article could benefit from a little more argumentation. Overall though, great read.		Article reads very concisely and fluently. Section orders have clearly been thought through and the English of the article is more than satisfactory. The article is lacking in references however, be sure to use these throughout the article. '''Done.'''
			Also, again, the article could benefit from a little more argumentation. Overall though, great read.

	== Response to reviewers: ==		== Response to reviewers: ==