RE: [scrumdevelopment] Architecture, Agile Project Management, and essence of Scrum Definition?
- From the fermented grain bucket Mike Speaketh:
That is old school Ron. ;^o The architecture is emerging as the level of
agreement as to what is needed and the level of clarity as how to do it move
toward each other. Scrum, Agile, Xp, all work from the idea that what they
are doing will hang together until the next refactoring. Ergo a good idea
is defined as one that hangs in their until a better one appears.
People who want a roadmap, should stay on the porch. Emergent environments
require people who can figure out how to get there and back.
Michael F. Dwyer
"Planning constantly peers into the future for indications as to where a
solution may emerge."
"A Plan is a complex situation, adapting to an emerging solution."
[mailto:email@example.com] On Behalf Of Ron Jeffries
Sent: Saturday, December 03, 2005 8:38 AM
Subject: Re: [scrumdevelopment] Architecture, Agile Project Management, and
essence of Scrum Definition?
On Saturday, December 3, 2005, at 7:50:49 AM, untzkhan wrote:
> There's been an interesting inquiry at the JavaRanch Big Moose Saloon
> ( http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi ), in which,
> a developer asks when and where in a sprint to spend time for product
> And during the responses to this particular posting,
> someone claimed that Scrum wasn't a software development process , at
> all, but a process / project management approach. I strongly disagreed
> and am seeking your advice / opinions on these two matters.
I think it's a process / project management approach that is
valuable for software development and many other areas. Scrum itself
contains no software-specific practices as I read it.
To be on the wire is life. The rest is waiting. --Karl Wallenda
To Post a message, send it to: scrumdevelopment@...
To Unsubscribe, send a blank message to:
Yahoo! Groups Links