[openbeos] Re: Suggestion for the team status page
- From: "Matt McMinn" <melfinadev@xxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Mon, 04 Mar 2002 21:16:10 GMT
I'm not sure if this would work for us, but here's what I just
implemented for my little team at work.
We've each got an XML file on our machine that looks something like
this:
<root>
<task percentDone="50">
<description>task #1 info</description>
<issues>any issues that need to be resolved</issues>
</task>
<task percentDone="80">
<description>task #2 info</description>
<issues>any issues that need to be resolved</issues>
</task>
...etc
</root>
Then I have a jsp page that simply calls the xalan/xerces parser/XSL
translator combo, whcih applies a stylesheet to all of our XML files,
and provides a nice little one page snapshot that's is as updated as
the XML files are. We have a policy that we keep the XML files updated
to the day, so we can always get an almost current snapshot of where
our project is at.
This could be translated to the OBOS world by each project having an
XML file checked in to the repository (assuming the web server can
access files on the repository). Then we can just build a page that
gathers all those XML files and displays them with a nifty XSL
stylesheet. The important thing with that is we would all have to
agree on an XML format - it's also a little more work for a developer,
but I tend to keep a TODO list around anyway, so keeping it in a
different format isn't that huge of a deal.
Matt
> > reported. Frankly, *any* designation that we give for a current
> > status
> > is a guess (hopefully an educated one).
>
> Okay, I see your point (exchanging one suboptimal way with another
> may
> make no sense at all) :-)
>
> > Of course, if you have a suggestion for a better way, feel free to
> > propose it. If I can apply it to all the teams, then I will
> > implement
> > it. But keep in mind, I will not impose pseudo-accuracy where it
> > doesn't exist merely to give people a "fuzzy" feeling about the
> > progress.
>
> I just think that the alpha-beta-stable categories are inappropriate
> to
> see how far that kit is. In fact, almost all kits have to be in alpha
> state until they are ready (and the beta phase shouldn't be that
> long)
> - if you would do it otherwise, you'd use a percentage bar with other
> titles than the rough numbers.
> A good way of doing it would be to have milestones in every project,
> and optionally to put colors between the different milestones to
> indicate how mature that part is.
> This comes hand in hand with Gregor's proposal of having the latest
> team news attached to the status.
>
> Most teams I looked at yet, already have such a milestone list
> internally, and it could be easily transferred into a nice graph
> usable
> for the status page.
> And then add the alpha/beta/stable state to that thing (in words, not
> as a bar).
>
> How about that? It would create some work to "reveal" those
> milestones,
> but it makes some sense to do that anyway.
>
> Adios...
> Axel.
>
>
Other related posts:
