[maemo-developers] maemo Bug Jar #7

From: Krischan Keitsch krischan.keitsch at alumni.tu-berlin.de
Date: Fri Jun 6 23:02:18 EEST 2008
Am Freitag, 6. Juni 2008 schrieben Sie:
> Hi,
>
> Krischan Keitsch wrote:
> > Quality first! Releasing shouldn't _only_ be a management decision. When
> > the quality is as expected then the (scrum ?) team should hand over the
> > responsibility to the management. They can then powerpoint the great
> > event ;-)
> > Personally I consider fix release dates as contra productive. Quality it
> > the key to success.
>
> While I still think we've wandered miles off topic here, I have to
> depend good project management practices. Release dates help with
> decision making - features to keep, features to drop.
>
> I agree that quality is a must, of course, but it's not the only
> parameter - last minute feature additions affect quality, or insisting
> on doing every feature on a checklist that is established at the start
> of the planning process. A release date helps you ship a smaller number
> of high quiality components, rather than spending years getting a
> required quality level on an ever-expanding feature list.
>
> Cheers,
> Dave.
>
> PS. As I understand it, the question here is that some bugs are fixed in
> the platform, but the patches aren't made available straight away. Have
> I misunderstood the issue?

Yes this is becomming offtopic ;-) 
I also agree what you mean. That is why I consider scrum as a perfect project 
development philosophy. Release often, get feedback, count on quality, 
comunicate, plan regularily and then release again :-)

(I guess we could go on forever which agile development 'method' is best and 
why waterfall is so 2003 - but this is offtopic.)

Cheers Krischan


More information about the maemo-developers mailing list