Comments on: eXtreme Programming Versus Scrum

By: wic

wic — Fri, 19 Mar 2010 10:50:01 +0000

I don't think it is fair to say that XP is more an engineering practice than Scrum. Scrum is more like a subset of XP, which means that XP contains at least the same amount of project management practices as Scrum. More info here:

http://www.objectmentor.com/omSolutions/agile_xp_differences.html

By: isak.swahn

isak.swahn — Tue, 16 Jun 2009 06:12:39 +0000

The boldness works fine with me - it gives a sense of the writer "speaking" directly to me, putting her emphasis on the words that are important, just like an inspiring lecturer would do.

The taste is different, and it's not possible to accommodate everyone. The first person who complained said he didn't even read the article, so I guess he went on to find a different article on the subject. This means he didn't suffer from this style either. :-)

By: Anonymous

Anonymous — Thu, 21 May 2009 14:31:47 +0000

i think its dumb that people commented on the formatting structure.. frankly who cares its the information that counts ..

u really broke up the meaning of the words in simple terms for me, I found it easier to comprehend the meaning behind both methods

By: Jude

Jude — Fri, 15 May 2009 08:16:00 +0000

Scrum + XP is a good combination. I am looking at adopting it for my company. How does scrum address product release process. I see it as more focussed toward delivery rather than on release and maintenance

By: DatNt

DatNt — Thu, 02 Apr 2009 06:16:00 +0000

I like the way you apply Bold to the font in the document. Very useful.

DatNT

By: Anonymous

Anonymous — Tue, 29 Apr 2008 13:34:00 +0000

Bold helps stress the points and I like that.

By: Anonymous

Anonymous — Fri, 25 Apr 2008 08:51:00 +0000

I like the highlighting. :)

By: Kelly Waters

Kelly Waters — Thu, 24 Apr 2008 14:00:00 +0000

Thanks to Dantelope for the feedback. Despite the criticism, I'm really pleased to hear it and it will help me to improve my blog.

More please :-)

Many thanks

Kelly.

By: Dantelope

Dantelope — Thu, 24 Apr 2008 13:21:00 +0000

I have read two blog entries now and both invited the same reaction sequence:

1) "Whaaa?" -- Your titles/intros are often the inverse of what you are trying to say and serve to incite. While that may make for "exciting reading" to you, it infuriates your readers (me at least).

2) "Ohhhh" -- It comes out that you are trying to say something other than what your title/intro suggests.

3) "I agree" -- I typically agree with your main argument. Especially in this post. XP vs. Scrum is moronic comparison by people who haven't bothered to understand what either is before they try to compare them.

4) "That sucked" -- Because of the shortness of your articles, the ubiquitous and annoying use of bold/blue (not a link... very troubling), and the inverted argument, I am left both times feeling negative about the article even though I agreed with it.

So in response to "Does it help or does it hinder?" -- it definitely hinders, but it's not the only thing holding you back.

LOVE the content, but HATE the format.

By: Kelly Waters

Kelly Waters — Thu, 24 Apr 2008 07:20:00 +0000

Thanks to Anonymous for the feedback above.

I started doing the bold thing a while back, in order to make it quicker for people to skim read my entries and still get the key points. Perhaps I have over-done it.

I would be grateful for any other feedback on this, so I can make my blog better for everyone going forward.

Does it help or does it hinder?

Kelly.

By: Anonymous

Anonymous — Thu, 24 Apr 2008 06:59:00 +0000

Your article is very hard to read with the ubiquitous use of bold, underlines and blue-but-it-isn’t-a-link.
At a glance, it looks more like a tag cloud than a blog post.
I diddn’t bother reading i for that reason, so I cannot comment on the contents of the article.

By: Franck

Franck — Thu, 24 Apr 2008 06:52:00 +0000

We could also ask the opposite question: “how we can do good agile only with agile engineering without agile management ?” ;o)

By: axe

axe — Wed, 23 Apr 2008 11:11:00 +0000

Oh, sorry, my previous comment wasn't enough applicable :(

You are right.

By: Kelly Waters

Kelly Waters — Wed, 23 Apr 2008 10:59:00 +0000

Hi Axe

In my post, I suggested that ideally you need to do both, because they address different aspects of software development, i.e. Scrum for management, XP for engineering.

It is possible to achieve acceptable product quality without XP, although XP I believe would raise the quality.

Therefore, if quality is not an problem area, you can achieve very good benefits from Scrum (i.e. agile management) or other agile management methods. XP, whilst very good, is optional and not a pre-requisite for good agile performance.

Regards
Kelly.

By: axe

axe — Wed, 23 Apr 2008 10:25:00 +0000

Kelly,

but how we can do good agile only with agile management without agile engineering?

It's seems dubiously :(