[feedhenry-dev] Using mailing list as main source of new functionalities

[David Martin]

I initially created the trello board as a landing ground and discussion
area for features requests and enhancements.
A way for users to give their feedback and make sure their voice was heard
before an action was taken ('action was taken' meaning something was added
to the Jira backlog)
The mailing list didn't even come into mind as the place for that to happen.

Thanks to Summers for bringing it up with me, I think using trello for this
is probably not the best way forward.
The mailing list makes so much sense, and I really should have thought of
it.

Where I think we're lacking, and some other teams have found it useful, is
having the team roadmap view visible.
All our backlog is ultimately in Jira.
The roadmap is hidden away in our Jira backlog in the form of issues &
Epics.
Is there a way to better visualise the backlog at the 'roadmap' level?
Is that something people would find useful?



On 21 November 2016 at 16:27, Wojciech Trocki <wtrocki at redhat.com> wrote:

> Url to our public trello board: https://trello.com/b/
> olSlTR9m/rhmap-developer-experience-feedback
>
> On Mon, Nov 21, 2016 at 4:18 PM, Wojciech Trocki <wtrocki at redhat.com>
> wrote:
>
>> Hi Everyone
>>
>> We want to keep our backlog consistent and clean from ideas that may not
>> be addressed in near future. To provide some collaboration space we created
>> new trello board.
>> Why duplication over jira? This matches some agile approach: "When
>> backlog has some tickets that would not be part of roadmap for the next 6
>> months then they should be removed from backlog :] ".
>>
>> I would like to ask all interesting parties about opinion on using Trello
>> vs Mailing List
>>
>> Why we created trello and decided to not use mailing list (IMHO)
>>
>> *Positive parts:*
>>
>> - Simplicity
>> - Defaulting to one source (email)
>> - Easy to contribute - just sent email.
>>
>> *Negative parts:*
>>
>> - No overview and visibility for our roadmap - just bunch of emails.
>> - No way to retrieve emails before signed to group
>> - No way to stage and label issues for customers and better visibility
>> - Mixed content - feature request can be mixed with other non related
>> email threads like this one.
>> - Interface from the last century:
>> http://www.redhat.com/archives/feedhenry-dev/2016-November/msg00000.html
>>
>>
>> Regards
>>
>> --
>> Wojciech Trocki
>> Software Engineer, Red Hat Mobile
>>
>>
>
>
> --
> Wojciech Trocki
> Software Engineer, Red Hat Mobile
>
>
> _______________________________________________
> feedhenry-dev mailing list
> feedhenry-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/feedhenry-dev
>
>


-- 
David Martin
Red Hat Mobile
Twitter: @irldavem
IRC: @irldavem (feedhenry, mobile-internal)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/feedhenry-dev/attachments/20161121/ccf7b65d/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo.png
Type: image/png
Size: 11472 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/feedhenry-dev/attachments/20161121/ccf7b65d/attachment.png>