RE: [scrumdevelopment] Who has the last say?
- Good day,Not too long ago I had written a blog entry on debt in software in terms of design, platform experience, configuration management, quality, and technical.Chris SterlingAgile Coach / Certified Scrum Trainer“Experience is easy to provide and quickly put to good use by people with all the other qualities." - Dee Hock
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Ilja Preuss
Sent: Wednesday, August 01, 2007 10:22 AM
Subject: Re: [scrumdevelopment] Who has the last say?
Yes, I like the concept.
Another great explanation of what happens when you compromise quality
for the sake of speed can be found in Ken's google talk. To find it, go
to google video, search vor "Ken Schwaber" and start with minute 40.
(The rest of the video is quite good, too, of course.)
Kurt Smith wrote:
> Hi,velocity. When presented with such cases I always refer back
> I agree as well. I've been in several discussion concerning quality
> and unrealistic expectations to deliver ahead of the "ideal"
> to "CodeDebt". If you are unaware please reference the following
> I would like to know what you all feel about this
> truly opened a new perpective for me and a new way tocommunicate to
> business users the results of their decisions. In theend the
> business typically wants a "quality" product and when explainedin
>> Totally agree. It's the profession of software
>> good quality
>> Heber Ferraz-Leite
>>>up on 700+ emails ...
>>> This has been a while ago, as I'm cathing
> But I'dcomment.
>>> still like to
>>>final say as to what is developed?
>>> <<< Who's jurisdiction is the
> Surelycannot decline Option A for the perceived quality that
>>> the team
>>> Option Bwill provide as it will lose the company business.
>>>PO ... But I think it is
>>> Everybody seems to have named the
> dangerous to putas it may bring the thinking of "cut quality to meet
>>> it that way,
>>> deadline" into scrum. The PO is responsible for the storiesHow things are
>>> but not for the way they are implemented.
> technicallythe team.
>>> implemented is a decision of
>>>functionality is expected, define
>>> The PO should say what exact
> priorities,And then it's the team's job to commit to something that
>>> etc. ...
>>> delivered with good quality. It's the scrummasters role tomake
> sure thatto.
>>> these rules are adhered
>>>option to say "I want
>>> I don't think that the PO should have the
> it deliveredquality", because the customer that the PO is
>>> with poorer
> delivering towill
>>> certainly not expect poorer quality. Reducing quality mayhelp
> you make along term it will create more
>>> short term presentation, but in the
> costsbugfixing, poorer code maintenance, and loss of
>>> because of
>>> your company.requirements cannot be commited to within a certain
>>> If the POs
>>> it's the PO's job to reduce the requirements (orsimplify them)
> so that theyroadmap for the rest.
>>> can be met, and outline a
>>>what will be implemented ... But it's
>>> So ... It's the PO's call
> not anyone'sto reduce quality. The call the PO needs to make is to reduce
>>>complexity, or choose not to reduce complexity and show less
>>> at his demo ... With a roadmap for theimplementation of the rest.
>To Unsubscribe, send a blank message to: scrumdevelopment- unsubscribe@ eGroups.com
> Yahoo! Groups Links