Jakob Illeborg Pagter <[EMAIL PROTECTED]> writes: > Jakob Illeborg Pagter skrev: >> Well, whether it is scrum is just a specific way of doing >> lean/incremental development. >> >> If we on monthly basis plan what features to implement for the next >> release and then visualize (e.g. using a burn down chart) >> continually how many features are ready, then we have a joint >> "directional" core which could be helpful. >> >> The monthly planning sessions could then choose from at "product >> backlog", i.e. a list of nifty features that we desire. Everybody >> can put stuff in the backlog, but on a montly basis we decide which >> features to take next.
I Googled this scrum thing a bit, and it sounds interesting. I like the idea of keeping track of the progress via graphs and charts! :-) > I guess the "backlock" could be the features and wish categories > that are "deferred", or maybe we could customize the categories. Certainly -- we can add new categories, or we can add new fields as we see fit. Please let me know if you have any good ideas. For example, I am not entirely happy with the default statuses: * unread * deferred * chatting * need-eg (means "need example") * in-progress * testing * done-cbb (means "done, could-be-better") * resolved I had to look in the manual to find out what need-eg and done-cbb meant... We might not need them, or we could give them better names. >From what I understand, we can still change everything after the tracker is live. > In any case, I think it would be helpful to easily propose, discuss, > prioritise, and list features. Yes, I hope it will be very useful too! -- Martin Geisler _______________________________________________ viff-devel mailing list (http://viff.dk/) [email protected] http://lists.viff.dk/listinfo.cgi/viff-devel-viff.dk
