[teampractices] Scrum-y tools based on BZ (was Re: Scrumbu.gs)

[Toby Negrin]

At Yahoo one of the most popular agile tools was a front-end for BZ. It had
charts, graphs, backlogs -- it was really nice.

Yahoo's bugzilla instance was heavily patched so even if the source code
was available, it probably wouldn't work with out of the box bugzilla but
it definitely proves the concept.

-Toby


On Tue, Oct 29, 2013 at 11:12 PM, Steven Walling <swalling at wikimedia.org>wrote:

>
> On Tue, Oct 29, 2013 at 10:54 PM, Erik Moeller <erik at wikimedia.org> wrote:
>
>> Thanks for sharing, Greg! I've also reached out to the scrumbu.gs
>> developer. I'd like to coordinate a bit more with Andre/Quim, but it'd
>> definitely be great to see if a joint approach with other major
>> players to improving our open source agile team tooling. Like I said,
>> I think Mingle is a great tool for now (and don't want to discourage
>> its use now that we've just started to get good at it), but getting a
>> good open alternative to work well for everyone is going to take a
>> long time, so we should start thinking about this early.
>>
>
> I really don't like Mingle much, and I'm a bit perplexed on how everyone
> is still using it. We tried it early in my team, I found it very
> heavy-handed and time consuming to work with. On top of this, the usability
> is terrible and it doesn't have mobile support like Trello or other tools.
> However, Trello is not able to support useful Scrum practices like burndown
> charts though (many users are using browser extensions to add this
> functionality). Ward Cunnigham and others who I've seen do Agile well like
> Pivotal Tracker, which is yet another popular but proprietary tool.
>
> Having bookmarked reports like this mapping of bug priority/severity<https://bugzilla.wikimedia.org/report.cgi?x_axis_field=priority&y_axis_field=bug_severity&z_axis_field=component&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=MediaWiki&product=MediaWiki+extensions&component=User+login+and+signup&component=GuidedTour&component=GettingStarted&component=Campaigns&resolution=---&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap>,
> I'm coming around to seeing Bugzilla as more useful for big picture
> prioritization these days. I'd be happy to see how a Bugzilla-based tool
> like scrumbu.gs might work for us, as an experiment. My one worry is that
> prioritization in Bugzilla is less in our control, and can sometimes be the
> subject of a tug-of-war with community members.
>
> --
> Steven Walling,
> Product Manager
> https://wikimediafoundation.org/
>
> _______________________________________________
> teampractices mailing list
> teampractices at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/teampractices
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wikimedia.org/pipermail/teampractices/attachments/20131030/0bebd505/attachment.html>