[teampractices] Experimenting with Pivotal Tracker

[Toby Negrin]

I'm going to be a bit cranky here but the analytics team has but a lot of
effort into getting our data into Mingle. Personally, I've used better
systems but it's the weather at this point.

I don't have a lot of room in the backlog for data migration so I'd like
point out that the impact of changing planning systems is considerable and
this should be taken into account.

-Toby


On Thu, Nov 14, 2013 at 3:52 AM, Pau Giner <pginer at wikimedia.org> wrote:

> I refactored https://www.mediawiki.org/wiki/Project_management_tools
>
>
> I added iceScrum ( http://www.icescrum.org/en/ ) to the list. It is
> Opensource and it has automatic charts, and the basics to support scrum.
> I used it in a former company (about 2 years ago) but I didn't made such
> an intensive use as with Mingle today, so I cannot provide an accurate
> comparison
>
> Pau
>
>
> On Thu, Nov 14, 2013 at 9:48 AM, Erik Moeller <erik at wikimedia.org> wrote:
>
>> On Wed, Nov 13, 2013 at 10:34 PM, Steven Walling <swalling at wikimedia.org>
>> wrote:
>> > Does this mean we get to hire an internal tools team someday? :)
>>
>> Absolutely, we will get to hire an internal tools team someday.
>> Someday is a nicely relative agile time estimate - maybe I'll give you
>> a burndown chart to go along with it. ;-)
>>
>> In seriousness, I think the tooling problem is very tricky, and a
>> "tools team" isn't necessarily the answer. My worry would be that they
>> immediately take on a very large problem (like creating our own agile
>> PM tool), which then becomes their only development/maintenance
>> responsibility.
>>
>> Distributing the load among other orgs that have the same problem
>> would be ideal. At the same time, the development of tools with a
>> beautiful user experience and a clear product vision tends to benefit
>> from a significant degree of integrated resourcing and leadership. For
>> a very ambitious project like a solid alternative to
>> Mingle/Trello/Pivotal/..., this might be a case where a joint
>> investment by e.g. Wikimedia+Mozilla in a third party org could be a
>> better way to bootstrap something than in-house development.
>>
>> For less ambitious projects (like experimenting with existing
>> Bugzilla-based solutions), the combination of more engineering
>> staffing overall + careful choices where we prioritize effort will
>> hopefully enable us to make steady progress.
>>
>> Erik
>> --
>> Erik Möller
>> VP of Engineering and Product Development, Wikimedia Foundation
>>
>> _______________________________________________
>> teampractices mailing list
>> teampractices at lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/teampractices
>>
>
>
>
> --
> Pau Giner
> Interaction Designer
> Wikimedia Foundation
>
> _______________________________________________
> 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/20131114/e0db0b94/attachment.html>