Talk:Project Schedule development - Revision history

Sarah at 20:22, 19 February 2018

2018-02-19T20:22:12Z

← Older revision		Revision as of 20:22, 19 February 2018
Line 97:		Line 97:
	''The article uses appropriate referencing, perhaps some references are missing in the "Motivation" section? The key references have not been summarized in a bibliography yet. I suggest expanding your research to include a wider range of academic perspectives on the topic. Also, researching ISO guidelines in terms of time management and schedule development may be interesting.''		''The article uses appropriate referencing, perhaps some references are missing in the "Motivation" section? The key references have not been summarized in a bibliography yet. I suggest expanding your research to include a wider range of academic perspectives on the topic. Also, researching ISO guidelines in terms of time management and schedule development may be interesting.''

	==Feedback 2 \| Reviewer name: ''~~Place your name here~~''==		==Feedback 2 \| Reviewer name: ''Sarah Romane Bourdiaux Terp''==
	===Question 1 · TEXT===		===Question 1 · TEXT===
	'''Quality of the summary:'''		'''Quality of the summary:'''
Line 106:		Line 106:

	===Answer 1===		===Answer 1===
	''~~Answer here~~''		''As the summary has not been written yet, I will review the motivation section. The motivation section contains some of the main reasons for applying PSD, which is good when catching the reader's attention, however, it would be nice if you could also specify who the intended reader is and what the purpose of the article is. This could however also be done in the abstract. I would also finish the motivation section in a more "open" way leading up to the next section about Project Time Management. It seems a bit abrupt as the latter has not yet been introduced in your article. This would give a nice and natural flow, guiding the reader through the "story" you are telling.''

	===Question 2 · TEXT===		===Question 2 · TEXT===
Line 122:		Line 122:

	===Answer 2===		===Answer 2===
	''~~Answer here~~''		''So far there is a good flow in the article and it is a very good idea starting by defining Project Time Management, which is the overall area within which PSD is relevant. As a reader, I am however lacking the purpose of why I am reading the article and where it is heading to. I would try to concretize the article in the beginning, as I mentioned, and then ensure the red thread is held throughout the article. It can also be a help when writing to have a clear idea of who this article is addressing. Then, I would ensure to break down the article even more, both for the reader's sake but also because it is much easier to break it down in smaller parts and writing them one by one. Having a visual idea of your article's "skeleton" can be very helpful.''

	===Question 3 · TEXT===		===Question 3 · TEXT===
Line 134:		Line 134:

	===Answer 3===		===Answer 3===
	''~~Answer~~ here''		''The language is clear, however regarding the grammar and style there is room for improvement. Much of it can be improved by proof reading thoroughly and several times in the end, however there are some repetitive errors.
			A main concern is the use of determiners (a, an, the etc.). Sometimes you forget to write them and sometimes you use "the" instead of "a", for example when you mention projects. As you are not writing about a specific project, remember to use "the" as determiner. In the abstract, you write "First of all, it provides in structure way...", where you forget a determiner before "structured way". It would thus be "First of all, it provides in a structured way...". I would spend some time checking for this type of error, because even if it seems like a little mistake here and there, it adds up in the end and it makes the overall flow of the article a bit uneven. Also, be careful to not forget a space after using a comma or a dot.''

	===Question 4 · TEXT===		===Question 4 · TEXT===
Line 146:		Line 147:

	===Answer 4===		===Answer 4===
	''~~Answer here~~''		''It is very nice with a visual overview of Project Time Management. You use the figure well and refer to it. However, I would maybe look into the grey box as it contains a lot of information in small letters and it can be a bit hard to read. It would be nice with more figures as it really helps the reader with a visual overview of what is written.''

	===Question 5 · TEXT===		===Question 5 · TEXT===
Line 158:		Line 159:

	===Answer 5===		===Answer 5===
	''~~Answer here~~''		''The article is of very high practical relevance as it provides clear and hands-on details to why and how PSD is relevant in project management. I would suggest using one or two more standards as references as well, as they often differ a bit and it can be very interesting from an academical point of view to see different takes on the same subject. It would also support your article's practical relevance even more.''

	===Question 6 · TEXT===		===Question 6 · TEXT===
Line 170:		Line 171:

	===Answer 6===		===Answer 6===
	''~~Answer here~~''		''It is very relevant for a practitioner but I would add a few more and different references to make it more relevant academically as well. It surely has the potential to make more contribution beyond a cursory web search and I look forward to reading it again when it is finished. My main suggestion would be to ensure that there is red thread throughout the article and make sure that the reader is onboard the whole way through.''

	===Question 7 · TEXT===		===Question 7 · TEXT===
Line 184:		Line 185:

	===Answer 7===		===Answer 7===
	''~~Answer here~~''		''For now there is no annotated bibliography, but the PMBOK® Guide is used appropriately and diligently. It is thus very much based on empirical data and not just on opinion but I would suggest, as mentioned, to investigate other relevant references and standards further.The article cites properly but remember that if you use web pages, you have to discuss the credibility of these as well.''

Oliver.amb: /* Answer 7 */

2018-02-19T19:07:49Z

Answer 7

← Older revision		Revision as of 19:07, 19 February 2018
Line 95:		Line 95:

	===Answer 7===		===Answer 7===
	''The article uses appropriate referencing, perhaps some references are missing in the "Motivation" section? The key references have not been summarized in a bibliography yet. I suggest expanding your research to include ~~various~~ academic perspectives on the topic. Also, researching ISO guidelines in terms of time management and schedule development may be interesting.''		''The article uses appropriate referencing, perhaps some references are missing in the "Motivation" section? The key references have not been summarized in a bibliography yet. I suggest expanding your research to include a wider range of academic perspectives on the topic. Also, researching ISO guidelines in terms of time management and schedule development may be interesting.''

	==Feedback 2 \| Reviewer name: ''Place your name here''==		==Feedback 2 \| Reviewer name: ''Place your name here''==

Oliver.amb: /* Answer 4 */

2018-02-19T18:17:42Z

Answer 4

← Older revision		Revision as of 18:17, 19 February 2018
Line 57:		Line 57:

	===Answer 4===		===Answer 4===
	''The use of figures and tables are relatively clear. Figure 1 provides a good overview of the project time management concept and its link to schedule development. Under section 3.2 I ~~am unsure whether~~ the sub-topics: "1. Inputs, 2. Tools and Techniques, etc" could be formalised in a more concise manner. When reading on a MAC the "2. Tools and Techniques" table contents extend beyond the boundaries of the frame. I am expecting more figures to support your discussion of project schedule development as so far there is one figure.''		''The use of figures and tables are relatively clear. Figure 1 provides a good overview of the project time management concept and its link to schedule development. Under section 3.2 I think the sub-topics: "1. Inputs, 2. Tools and Techniques, etc" could be formalised in a more concise manner. When reading on a MAC the "2. Tools and Techniques" table contents extend beyond the boundaries of the frame. I am expecting more figures to support your discussion of project schedule development as so far there is one figure.''

	===Question 5 · TEXT===		===Question 5 · TEXT===

Oliver.amb: /* Answer 4 */

2018-02-19T18:17:12Z

Answer 4

← Older revision		Revision as of 18:17, 19 February 2018
Line 57:		Line 57:

	===Answer 4===		===Answer 4===
	''The use of figures and tables are relatively clear. Figure 1 provides a ~~goodover view~~ of the project time management concept and its link to schedule development. Under section 3.2 I am unsure whether the sub-topics: "1. Inputs, 2. Tools and Techniques, etc" could be formalised in a more concise manner. When reading on a MAC the "2. Tools and Techniques" table contents extend beyond the boundaries of the frame. I am expecting more figures to support your discussion of project schedule development as so far there is one figure.''		''The use of figures and tables are relatively clear. Figure 1 provides a good overview of the project time management concept and its link to schedule development. Under section 3.2 I am unsure whether the sub-topics: "1. Inputs, 2. Tools and Techniques, etc" could be formalised in a more concise manner. When reading on a MAC the "2. Tools and Techniques" table contents extend beyond the boundaries of the frame. I am expecting more figures to support your discussion of project schedule development as so far there is one figure.''

	===Question 5 · TEXT===		===Question 5 · TEXT===

Oliver.amb: /* Answer 4 */

2018-02-19T18:16:56Z

Answer 4

← Older revision		Revision as of 18:16, 19 February 2018
Line 57:		Line 57:

	===Answer 4===		===Answer 4===
	''The use of figures and tables are relatively clear. Figure 1 provides a ~~good over~~ view of the project time management concept and its link to schedule development. Under section 3.2 I am unsure whether the sub-topics: "1. Inputs, 2. Tools and Techniques, etc" could be formalised in a more concise manner. When reading on a MAC the "2. Tools and Techniques" table contents extend beyond the boundaries of the frame. I am expecting more figures to support your discussion of project schedule development as so far there is one figure.''		''The use of figures and tables are relatively clear. Figure 1 provides a goodover view of the project time management concept and its link to schedule development. Under section 3.2 I am unsure whether the sub-topics: "1. Inputs, 2. Tools and Techniques, etc" could be formalised in a more concise manner. When reading on a MAC the "2. Tools and Techniques" table contents extend beyond the boundaries of the frame. I am expecting more figures to support your discussion of project schedule development as so far there is one figure.''

	===Question 5 · TEXT===		===Question 5 · TEXT===

Oliver.amb: /* Feedback 1 | Reviewer name: Oliver Adam Mølskov Bech */

2018-02-19T18:05:41Z

Feedback 1 | Reviewer name: Oliver Adam Mølskov Bech

← Older revision		Revision as of 18:05, 19 February 2018
Line 39:		Line 39:
	*Refer to "projects" or "a project" rather than "the project". E.g. Under 2. Motivation, the last sentence says "potential costs of the project", what project is this you are referring to?		*Refer to "projects" or "a project" rather than "the project". E.g. Under 2. Motivation, the last sentence says "potential costs of the project", what project is this you are referring to?
	*Example of a sentence containing grammatical errors: "At last but not the least,PSD implemented correctly...."		*Example of a sentence containing grammatical errors: "At last but not the least,PSD implemented correctly...."
	*The title is Project Schedule development, I would suggest making the "d" in development a capital D.
	*Be consistent in your syntax, are you going to insert a reference immediately after a word or after a symbol (.,). Refer to your first reference and compare to second reference for an example. Consistency in your syntax will make your article appear more professional.		*Be consistent in your syntax, are you going to insert a reference immediately after a word or after a symbol (.,). Refer to your first reference and compare to second reference for an example. Consistency in your syntax will make your article appear more professional.
	*Again, there is no consistency in your tables under section 3.2, some bullet point sentences end with a full stop "." while others don't.		*Again, there is no consistency in your tables under section 3.2, some bullet point sentences end with a full stop "." while others don't.
Line 70:		Line 69:

	===Answer 5===		===Answer 5===
	''Yes, the article has high practical relevance to individuals with a vested interest in the time management and scheduling developments of projects. The motivation section discusses the importance of the topic and the benefits to developing a successful project schedule.''		''Yes, the article has high practical relevance to individuals with a vested interest in the time management and scheduling developments of projects. The motivation section discusses the importance of the topic and the benefits to developing a successful project schedule. Perhaps it would be more academically relevant if a wider body of references were used, such as for example ISO standards.''

	===Question 6 · TEXT===		===Question 6 · TEXT===
Line 96:		Line 95:

	===Answer 7===		===Answer 7===
	''~~Answer here~~''		''The article uses appropriate referencing, perhaps some references are missing in the "Motivation" section? The key references have not been summarized in a bibliography yet. I suggest expanding your research to include various academic perspectives on the topic. Also, researching ISO guidelines in terms of time management and schedule development may be interesting.''

	==Feedback 2 \| Reviewer name: ''Place your name here''==		==Feedback 2 \| Reviewer name: ''Place your name here''==

Oliver.amb: /* Answer 4 */

2018-02-19T17:58:52Z

Answer 4

← Older revision		Revision as of 17:58, 19 February 2018
Line 58:		Line 58:

	===Answer 4===		===Answer 4===
	''The use of figures and tables are relatively clear. Figure 1 provides a good over view of the project time management concept and its link to schedule development. Under section 3.2 I am unsure whether the sub-topics: "1. Inputs, 2. Tools and Techniques, etc" could be formalised in a more concise manner. When reading of a MAC the "2. Tools and Techniques" table contents extend beyond the boundaries of the frame. I am expecting more figures to support your discussion of project schedule development as so far there is one figure.''		''The use of figures and tables are relatively clear. Figure 1 provides a good over view of the project time management concept and its link to schedule development. Under section 3.2 I am unsure whether the sub-topics: "1. Inputs, 2. Tools and Techniques, etc" could be formalised in a more concise manner. When reading on a MAC the "2. Tools and Techniques" table contents extend beyond the boundaries of the frame. I am expecting more figures to support your discussion of project schedule development as so far there is one figure.''

	===Question 5 · TEXT===		===Question 5 · TEXT===

Oliver.amb: /* Feedback 1 | Reviewer name: Oliver Adam Mølskov Bech */

2018-02-19T17:57:32Z

Feedback 1 | Reviewer name: Oliver Adam Mølskov Bech

← Older revision		Revision as of 17:57, 19 February 2018
Line 58:		Line 58:

	===Answer 4===		===Answer 4===
	''~~Answer here~~''		''The use of figures and tables are relatively clear. Figure 1 provides a good over view of the project time management concept and its link to schedule development. Under section 3.2 I am unsure whether the sub-topics: "1. Inputs, 2. Tools and Techniques, etc" could be formalised in a more concise manner. When reading of a MAC the "2. Tools and Techniques" table contents extend beyond the boundaries of the frame. I am expecting more figures to support your discussion of project schedule development as so far there is one figure.''

	===Question 5 · TEXT===		===Question 5 · TEXT===
Line 70:		Line 70:

	===Answer 5===		===Answer 5===
	''~~Answer here~~''		''Yes, the article has high practical relevance to individuals with a vested interest in the time management and scheduling developments of projects. The motivation section discusses the importance of the topic and the benefits to developing a successful project schedule.''

	===Question 6 · TEXT===		===Question 6 · TEXT===
Line 82:		Line 82:

	===Answer 6===		===Answer 6===
	''~~Answer here~~''		''The article is mostly relevant to a practitioner.It does contribute beyond a cursory web search using relevant references to the PMBOK guide. I would suggest delving deeper into some of the complexities of project schedule development to make the article useful to both practitioners and academics.''

	===Question 7 · TEXT===		===Question 7 · TEXT===

Oliver.amb: /* Answer 3 */

2018-02-19T17:48:58Z

Answer 3

← Older revision		Revision as of 17:48, 19 February 2018
Line 40:		Line 40:
	*Example of a sentence containing grammatical errors: "At last but not the least,PSD implemented correctly...."		*Example of a sentence containing grammatical errors: "At last but not the least,PSD implemented correctly...."
	*The title is Project Schedule development, I would suggest making the "d" in development a capital D.		*The title is Project Schedule development, I would suggest making the "d" in development a capital D.
	*Be consistent in your syntax, are you going to insert a reference immediately after a word or after a ".~~" or ","~~, Refer to your first reference and compare to second reference for an example.		*Be consistent in your syntax, are you going to insert a reference immediately after a word or after a symbol (.,). Refer to your first reference and compare to second reference for an example. Consistency in your syntax will make your article appear more professional.
	*Again, there is no consistency in your tables under section 3.2, some bullet point sentences end with a full stop "." while others don't.		*Again, there is no consistency in your tables under section 3.2, some bullet point sentences end with a full stop "." while others don't.
	*Also, the term "Schedule Development" always uses Title Case syntax within your text, I would recommend moving away from this as it is not good formatting.		*Also, the term "Schedule Development" always uses Title Case syntax within your text, I would recommend moving away from this as it is not good formatting.

Oliver.amb: /* Feedback 1 | Reviewer name: Oliver Adam Mølskov Bech */

2018-02-19T17:46:27Z

Feedback 1 | Reviewer name: Oliver Adam Mølskov Bech

← Older revision		Revision as of 17:46, 19 February 2018
Line 36:		Line 36:

	===Answer 3===		===Answer 3===
	''The writing contains several grammatical errors. Grammatical errors lead to an inconsistent reading flow for the reader. Here is a list of some possible errors and suggestions for improvement:		''The writing contains several grammatical errors. Grammatical errors lead to an inconsistent reading flow for the reader. The language is fairly precise however be careful with the use of unnecessary adjectives. Here is a list of some possible errors and suggestions for improvement:
			*Refer to "projects" or "a project" rather than "the project". E.g. Under 2. Motivation, the last sentence says "potential costs of the project", what project is this you are referring to?
			*Example of a sentence containing grammatical errors: "At last but not the least,PSD implemented correctly...."
	*The title is Project Schedule development, I would suggest making the "d" in development a capital D.		*The title is Project Schedule development, I would suggest making the "d" in development a capital D.
	*Be consistent in your syntax, are you going to insert a reference immediately after a word or after a "." or ",", Refer to your first reference and compare to second reference for an example.		*Be consistent in your syntax, are you going to insert a reference immediately after a word or after a "." or ",", Refer to your first reference and compare to second reference for an example.
Line 43:		Line 45:
	*"1. Inputs" is inserted within the framed box while "2. Tools and Techniques" and "3. Outputs" is framed outside their respective boxes.		*"1. Inputs" is inserted within the framed box while "2. Tools and Techniques" and "3. Outputs" is framed outside their respective boxes.
	*Consider using italic font for your points to allow the reader to more easily distinguish between "terms" and "term descriptions".		*Consider using italic font for your points to allow the reader to more easily distinguish between "terms" and "term descriptions".
	*Under 3.2 Schedule Development, 1. Inputs, 1.6. Constrains - do you mean "Constraints"? The word constrains is used again later on, please double check this.''		*Under 3.2 Schedule Development, 1. Inputs, 1.6. Constrains - do you mean "Constraints"? The word constrains is used again later on, please double check this.
			*Consider using bullet points using the asterix symbol, such as for parts like the limitations section where you have used a numbering system.''

	===Question 4 · TEXT===		===Question 4 · TEXT===