Ultimate Quality Development System - DonationCoder.com
Welcome Guest.   Make a donation to an author on the site July 31, 2015, 02:30:01 PM  *

Please login or register.
Or did you miss your validation email?

Login with username and password (forgot your password?)
Why not become a lifetime supporting member of the site with a one-time donation of any amount? Your donation entitles you to a ton of additional benefits, including access to exclusive discounts and downloads, the ability to enter monthly free software drawings, and a single non-expiring license key for all of our programs.

You must sign up here before you can post and access some areas of the site. Registration is totally free and confidential.
Your Support Funds this Site: View the Supporter Yearbook.
   Forum Home   Thread Marks Chat! Downloads Search Login Register  
Pages: [1]   Go Down
  Reply  |  New Topic  |  Print  
Author Topic: Ultimate Quality Development System  (Read 1806 times)
Charter Honorary Member
Posts: 1,321

see users location on a map View Profile Give some DonationCredits to this forum member
« on: August 23, 2008, 07:14:18 AM »

I don't recall exactly how I found this (somehow via more feeds, pythonic, twisted, ...). It describes a development method that relies on tickets and branches. For each ticket there is (was) a branch, dealing with this ticket.

The briefest summary of the requirements for UQDS is that every task has 3 absolutely required steps.

  • A task is created in an issue tracker and assigned to a worker.
  • The worker does work, and creates a change-set to be applied to the mainline revision control system. (This can be represented as either a branch or a patch file.)
  • A reviewer reviews the completed work, and provides feedback: at least one good thing about the work, at least one area that needs improvement, and a judgement as to whether the good qualities ultimately outweigh the bad, i.e. whether the branch should be merged.

It seems like a very formal way. But I have seen worse, involving paper forms, weekly meetings and such. For me this UQDS sounds very intriguing and I want to try it in our company. This kind of development system goes very well with my personality.

As far as the overhead goes, I'd rather have overhead that results in better code than have an "afterhead" when having to deal with the results of bad code.
Pages: [1]   Go Up
  Reply  |  New Topic  |  Print  
Jump to:  
   Forum Home   Thread Marks Chat! Downloads Search Login Register  

DonationCoder.com | About Us
DonationCoder.com Forum | Powered by SMF
[ Page time: 0.031s | Server load: 0.53 ]

Share on Facebook
submit to reddit