Talk:The Extreme Project Management approach
(→Some comments about the part below:) |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| 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 64: | Line 65: | ||
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. '''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. '''Done.''' | ||
| + | |||
| + | === 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." '''Done.''' | ||
| + | |||
| + | *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. | ||
| + | |||
| + | === 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. '''See notes below''' | ||
| + | |||
| + | *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. '''Fixed.''' | ||
| + | |||
| + | === Conclusion === | ||
| + | |||
| + | 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 === | ||
| + | |||
| + | 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: == | ||
| + | |||
| + | |||
| + | 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! | ||
Latest revision as of 18:34, 30 November 2014
Contents |
[edit] Review by Huhe
The contains and struture of your article is good, it covers the topics very well. It has a customized size. Below is some suggestions for improving your article.
[edit] Abstract
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.
[edit] Use bullet points
In your article you write:
"In order to implement XPM in a successful way, several criteria has to be taken into account such as: -Project and iteration’s scopes. -Measures to ensure quality. -Business team members decide what to deliver and technical team members how to deliver so. -Corporate culture, which is ‘the ways a company's owners and employees think, feel and act’ must support XPM approach. -Trust and communication established between all members of the project team are the key." 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. Done. 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:
- Project and iteration’s scopes
- Measures to ensure quality.
- Business team members decide what to deliver and technical team members how to deliver so.
- Corporate culture, which is ‘the ways a company's owners and employees think, feel and act’ must support XPM approach.
- Trust and communication established between all members of the project.
[edit] Small Detail about your headlines
all your headlines ends with : or .
ex: ABSTRACT: , INTRODUCTION TO EXTREME PROJECT MANAGEMENT:...... CONCLUSION. , REFERENCES.
it will look better if you remove the unnecessary: and. Done.
[edit] 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? 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.
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’)
[edit] 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. Done.
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. 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. Done.
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."
[edit] 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.
[edit] 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.
[edit] 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. 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. Done.
[edit] 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." Done.
- 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.
[edit] 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. See notes below
- Discussion of the XPM Methodology is strong again. Consistent with the previous section of the report and is clear and comprehensive.
[edit] 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. Fixed.
[edit] Conclusion
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.
[edit] 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. Done. Also, again, the article could benefit from a little more argumentation. Overall though, great read.
[edit] 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!
