[openbeos] Re: some points

Hi there,

Wouldn't it be an idea to use the differrent milestones on preferably 
the same scale as the alpha, beta, release candidate, final, mature,
servicepack or whatever...

Because not all milestones WILL be completed sequential (to be efficient
with resources and waiting for some functionality from kernel or
somthing like that/ some milestones will be finished earlier than
others) each milestone will have it's own progressbar.

When this is combined with the overall progressbar per kit, and maybe
even a planning, alpha, beta, mature progressbar, I think people can get
a pretty good idea of the status of the whole project.

And to make it a little more dynamic it can be complementen with a
check-in graph which gives a view on the ammount of attention/check-in's
per kit.

Something like below:

 
+--------------------------------+--------------------------------+-
Status    |            Planning            |            Alpha
|
 
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+-
Milestone | 1| 2| 3| 4| 5| 6| 7| 8| 9|10|11| 1| 2| 3| 4| 5| 6| 7| 8|
9|10|11|
 
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
Kit A     | x| x| x| x| x| x| x| x| x|  -  | x| x| x| x| x| x| x|     -
|
 
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
Kit B     | x| x| x| x| x| x|      -       | x| x| x| x| x| x| x| x| x|
-  |
 
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
Kit C     | x| x| x| x| x| x| x| x| x| x| x| x| x| x| x| x| x| x| x|   -
|   
 
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

Or: 

+=======================================================================
===================+
|                   H A I K U  D E V E L O P M E N T  S T A T U S
|
+=====+========================================+==========+==========+==
========+==========+
| Kit | Milestone incl. brief explanation      | Planning | Alpha    |
Beta     | Mature   |
+=====+========================================+==========+==========+==
========+==========+
|  A  | 1 : Brief explanation
|XXXXXXXXXX|XXXXXXXXXX|XXXXXXXXXX|          |
|
+----------------------------------------+----------+----------+--------
--+----------+
|     | 2 : Brief explanation                  |XXXXXXXXXX|XXXXXXXX  |
|          |
|
+----------------------------------------+----------+----------+--------
--+----------+
|     | n : Brief explanation
|XXXXXXXXXX|XXXXXXXXXX|XXXXXXXXX |          |
|
+========================================+==========+==========+========
==+==========+
|       Overall Kit progress
|XXXXXXXXXX|XXXXXXXXXX|XXXXXXX   |          |
+=====+========================================+==========+==========+==
========+==========+
|  B  | 1 : Brief explanation
|XXXXXXXXXX|XXXXXXXXXX|XXXXXXXX  |          |
|
+----------------------------------------+----------+----------+--------
--+----------+
|     | 2 : Brief explanation
|XXXXXXXXXX|XXXXXXXXXX|XXXXXXX   |          |
|
+----------------------------------------+----------+----------+--------
--+----------+
|     | n : Brief explanation
|XXXXXXXXXX|XXXXXXXXXX|XXXX      |          |
|
+========================================+==========+==========+========
==+==========+
|       Overall Kit progress
|XXXXXXXXXX|XXXXXXXXXX|XXXXXXX   |          |
+=====+========================================+==========+==========+==
========+==========+
|  C  | 1 : Brief explanation
|XXXXXXXXXX|XXXXXXXXXX|XXXXX     |          |
|
+----------------------------------------+----------+----------+--------
--+----------+
|     | 2 : Brief explanation                  |XXXXXXXXXX|XX        |
|          |
|
+----------------------------------------+----------+----------+--------
--+----------+
|     | n : Brief explanation                  |XXXXXXXXXX|XXXXXXX   |
|          |
|
+========================================+==========+==========+========
==+==========+
|       Overall Kit progress                   |XXXXXXXXXX|XXXXXXXXX |
|          |
+=====+========================================+==========+==========+==
========+==========+
|                                              |          |          |
|          |
| H A I K U  O v e r a l l  p r o g r e s s
|XXXXXXXXXX|XXXXXXXXXX|XXXX      |          |
| (This is a rough estimate)                   |          |          |
|          |
+==============================================+==========+==========+==
========+==========+

CVS check-in graph (use different color per kit):

    10  |
C    9  |
H    8  |
E    7  |
C    6  |
K    5  |
     4  |
I    3  |  
N'   2  |
S    1  |  
 
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+------+-
           1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19  -
52   
          Weeknr.

Kit A: Yellow
Kit B: green
Kit C: Red


Hope it's something like a start of showing the stati in a clearer
way?!?!?

Greets, Rob

PS: comment is most welcome ;o)


-----Oorspronkelijk bericht-----
Van: openbeos-bounce@xxxxxxxxxxxxx
[mailto:openbeos-bounce@xxxxxxxxxxxxx] Namens Michael Phipps
Verzonden: dinsdag 29 juni 2004 18:22
Aan: openbeos@xxxxxxxxxxxxx
Onderwerp: [openbeos] Re: some points


Maybe if I explain the problem that we were trying to solve, we can come
up 
with some good solution.

There was a lot of discontent that the status bars never moved. That
they were 
not a good indicator of status because, well, they didn't move. 

Additionally, the point was made that some things that are not
development 
complete are in alpha, so having a simple 1-10 of development followed
by an 
alpha box and a beta box (which was in place when the new website went
live, I 
think) was deceptive, too.

So, the problem, generally is "how do we give an accurate representation
of 
status?". Where status can entail a number of things, including:
- percentage of development complete
- is it in alpha?
- is it in beta? 
- is it mature? 

Finally, there is one other feature that I would love to see, but I
really 
don't know how it would work. That is velocity. How much has been done
in the 
last, say, month. That would show activity (or lack thereof). Maybe CVS 
checkins? That is a feature that could come much later.

So if anyone out there has a solution that fills all of those criteria,
please 
feel free to speak up! :-)

On 2004-06-29 at 07:20:17 [-0400], Waldemar Kornewald wrote:
> Hi Axel,
> 
> > I disagree here :)
> > You can always only believe you might have a good idea about the
> > status
> > - a simple progress bar from 0% to 100% is surely not enough to gain

> > real understanding.
> > The alpha/beta status is an improvement, as would be any other of
the here 
> > mentioned suggestions as well IMO.
> 
> I find this confusing (as many others, too). Why can we not use a
> status bar
> with different coloring meaning "Development, Alpha, Beta, Stable,
Mature"? 
> Choose some five colours and there you go with a twice as wide status
bar for 
> each team.
> 
> Just my $0.02,
> Waldemar

Other related posts: