Re: Why are we still allowing the term "Agile Project Manager"?
- +1 on Ron's pithy statement.
1. A rose by any other name is still a rose.
2. AND...words have meaning to people. If you call a horse a donkey,
some people will think that that animal is perfect for donkey work but
not right for horse work.
So, we have to balance 1 and 2.
AND...we must pick out battles and our battlefields. Not sure that
semantics are the highest impediments to fight about.
--- In email@example.com, Ilja Preuss <it@...> wrote:
> Ron Jeffries wrote:
> > Agile teams often stall not because "Agile doesn't work," or because
> > "Agile doesn't fit our real world," but because they don't recognize
> > that things like "We can't get done in one Sprint because QA needs a
> > whole Sprint to test a Sprint's work" is not a description of the
> > "real world" but a description of an obstacle to be removed.
> I like that wording. Expect to be quoted.
> Cheers, Ilja
- Hello, Robert. On Wednesday, July 2, 2008, at 11:19:55 AM, you
> Your earlier message said:OK. Why do /you/ think Scrum works.
>> Scrum works, in my opinion, because it requires two things:
>> 1. Produce Done-Done software on a regular basis;
>> 2. Remove every obstacle to doing item 1.
> I'm not sure I agree. In particular, it seems to suggest an absolute
> focus on
> software, and it seems to suggest seeing other things as obstacles to that.
> I think an important advantage of scrum, and other agileInteresting. What do you see in the definition of Scrum that leads
> processes, is that they involve software development in a wider
> context, and in that wider context the development of software is
> unlikely to be the priority.
you to believe it is not focused on software? A reference would be
> So the advantage for software development is that the process isSo that whole "Agile Software Development with Scrum" thing was just
> more likely to lead to software that helps in that larger context.
> This means it is important for everyone to realise that software
> development is not the ultimate goal, and that things that might
> seem like obstacles may in fact show aspects of the wider context
> that need to be better understood and may in fact change the
> nature of the software development.
what ... a typo?
I must create a system, or be enslaved by another man's;
I will not reason and compare; my business is to create. --William Blake