Talk:Scrum Methodology in Agile Software Development - Revision history

S150821: /* Answer to reviwer 2 */

2015-09-28T21:21:38Z

Answer to reviwer 2

← Older revision		Revision as of 21:21, 28 September 2015
Line 222:		Line 222:

	*I wrote some more explanation of Sprint in the Application section. Now I think it is simpler to follow the article flow.		*I wrote some more explanation of Sprint in the Application section. Now I think it is simpler to follow the article flow.
	*In the references there ~~are~~ a link to the “official” site of Scrum reference Card, here you can download it.		*In the references there is a link to the “official” site of Scrum reference Card, here you can download it.

S150821: /* Answer to reviewer 1 */

2015-09-28T21:00:56Z

Answer to reviewer 1

@@ Line 108: / Line 108: @@
 Best Regards Jane
 ----
@@ Line 177: / Line 191: @@
 Dimitris

S150821: /* 113129's comments: */

2015-09-28T20:55:58Z

113129's comments:

@@ Line 45: / Line 45: @@
 // This concludes 113129's comments! :)
 ----
 Reviewer 3, S997303

Dimak: /* 113129's comments: */

2015-09-22T20:23:40Z

113129's comments:

← Older revision		Revision as of 20:23, 22 September 2015
Line 69:		Line 69:

	'''Reviewer 2, Dimak'''		'''Reviewer 2, Dimak'''

	Hi,		Hi,

S997303 at 20:19, 22 September 2015

2015-09-22T20:19:57Z

← Older revision		Revision as of 20:19, 22 September 2015
Line 65:		Line 65:
	Good luck with the completion of your article.		Good luck with the completion of your article.
	Best Regards Jane		Best Regards Jane
			----


	'''Reviewer 2, Dimak'''		'''Reviewer 2, Dimak'''

S997303 at 20:19, 22 September 2015

2015-09-22T20:19:02Z

← Older revision		Revision as of 20:19, 22 September 2015
Line 51:		Line 51:
	Formal aspects		Formal aspects

	• Interesting methodology and your writing style is clear and fluent.		• Interesting methodology and your writing style is clear and fluent to me

	• You use appropriate figures, but consider making them larger, so they become less blurred. Especially I suggest making the Scrum Framework figure larger in scale, because this is the visual overview of the Scrum Methodology in your article.		• You use appropriate figures, but consider making them larger, so they become less blurred. Especially I suggest making the Scrum Framework figure larger in scale, because this is the visual overview of the Scrum Methodology in your article.
Line 67:		Line 67:

	'''Reviewer 2, Dimak'''		'''Reviewer 2, Dimak'''

	Hi,		Hi,

Dimak: /* 113129's comments: */

2015-09-22T20:18:47Z

113129's comments:

← Older revision		Revision as of 20:18, 22 September 2015
Line 67:		Line 67:

	'''Reviewer 2, Dimak'''		'''Reviewer 2, Dimak'''

	Hi,		Hi,

Dimak: /* 113129's comments: */

2015-09-22T20:18:07Z

113129's comments:

← Older revision		Revision as of 20:18, 22 September 2015
Line 65:		Line 65:
	Good luck with the completion of your article.		Good luck with the completion of your article.
	Best Regards Jane		Best Regards Jane

			'''Reviewer 2, Dimak'''
			Hi,

			I found your article very interesting with a lot of information about Scrum methodology and a lot of illustrations. Expect from some points the referencing was good. As far as the structure and the language are concerned, I believe that there are some improvements that can be made and thus I will give some examples by commenting each section of your article.

			'''Abstract'''

			You have a nice abstract and you nicely analyze what is the purpose of your article but there are some points that in my opinion you should focus on improving. More specifically:

			• Customer’s and market’s needs can be reformulated to customers' and markets' needs.
			• When you first mention Agile Software Development, you can write (ASD) in brackets so that you will not have to use it as a whole again
			• In general I believe that you can revise a bit your syntax in some sentences. Also you can try to keep them a bit shorter. I always use big sentences myself so I definitely cannot judge you for that!
			• You can use http://www.thesaurus.com/ to find some expressions or synonyms for your article. Personally it helped me a lot ;)

			'''Scrum Methodology'''

			• In the point you say about rugby -which by the way find very interesting as a connection, you can maybe use a reference.
			• Not only in this section, but also in the whole article, it will be more easier for someone to follow if you use connectors (e.g. Furthermore, Moreover etc.)

			'''Agile Software Development'''

			There are some really nice points here but again a bit of reformulation is needed. I like that you use bullet-points.

			'''Manifesto for the Agile Software development'''

			Just a small suggestion. You can write seventeen instead of 17 to make your article a bit more formal

			'''Application'''

			Again I believe that there are some points that you can reformulate to make it easier for a practitioner to follow. I like the contents you have in this section.

			• You can write a few words as a small introduction and as a connection to the previous section.
			• Maybe you can connect the illustration about scrum framework to the text because for me, the connection is a bit unclear.
			• Just a small suggestion. Maybe you can write actors instead of figures.

			'''Main figures in Scrum'''

			I got a little confused in this section because I thought that you talked about the figures earlier. Maybe you can consider a way to connect these two sections. For instance, when you mention them for the first time you can write : "these figures will be further analyzed in a following section" or something like that.

			• Maybe you can use a bit more references when you talk about the Product Owner, the Development team and the Scrum Master.
			• Here you mention some artefacts that are used in Scrum methodology. Maybe it will be better to analyze them here and not on another part because I believe it can be more difficult for a practitioner to follow. For instance, when I first read your article I was not sure on what a product backlog is until I found it below and I went back to make the connection. This bullet point covers the '''Artefacts''' section as well.

			'''Team self-organization'''

			Again I like that you have bullet points. It makes it easier for someone to follow.

			• At some point you say “it is told developer what needs to be done not how to do it”. Maybe you can use a reference on that.
			• You say: "Conversely there are some conditions that can hander self-organization". Maybe you meant harden instead of hander.

			'''Scrum Meetings'''

			Nice points here as well. There are still some grammatical and syntax errors I think you should check.

			• Remember to use a reference for your illustration.

			'''Sprint'''

			This section is cohesive and straight forward but as a minor suggestion I believe that you could have explained it a bit earlier when you talk about Sprints in the Application section.

			'''Limitations'''

			Maybe you can use an image to illustrate the scrum reference card.

			I hoped that I helped you by giving these suggestions and I wish you good luck with your final article.

			Dimitris

S997303 at 20:13, 22 September 2015

2015-09-22T20:13:05Z

← Older revision		Revision as of 20:13, 22 September 2015
Line 56:		Line 56:

	• Also it could be an advantage to enlarge the Product Backlog figure as well as the Sprint Backlog so they can better visualize and support your text.		• Also it could be an advantage to enlarge the Product Backlog figure as well as the Sprint Backlog so they can better visualize and support your text.

	Content aspects		Content aspects

S997303 at 20:10, 22 September 2015

2015-09-22T20:10:42Z

← Older revision		Revision as of 20:10, 22 September 2015
Line 45:		Line 45:
	// This concludes 113129's comments! :)		// This concludes 113129's comments! :)
	----		----
			Reviewer 3, S997303

			Hi Giacomo

			Formal aspects

			• Interesting methodology and your writing style is clear and fluent.

			• You use appropriate figures, but consider making them larger, so they become less blurred. Especially I suggest making the Scrum Framework figure larger in scale, because this is the visual overview of the Scrum Methodology in your article.

			• Also it could be an advantage to enlarge the Product Backlog figure as well as the Sprint Backlog so they can better visualize and support your text.
			Content aspects

			• If I look at the balance of the sections in your article I could suggest to focus more on the limitations section and for example supporting your facts with additional literature about use of Scrum methodology in software development.

			• Your article is very detailed described for a practitioner – and if I was a practitioner I would also be very interested in knowing more about the Scrum Reference Card and how to evaluate when a project belongs in the chaotic field of the Predictability figure and therefore should select a Scrum Methodology.

			Good luck with the completion of your article.
			Best Regards Jane