Re: [Scrum] Open Source Scrum Teams -

[Mark Levison]

Nancy - Is this a full time team or a volunteer team? if the later I'm not sure that Scrum is useful. Scrum is a tool to organize a **dedicated** team to attain high performance. A part time volunteer team will get some benefit but not what we all shoot for.

Cheers

Mark

On Mon, May 13, 2013 at 3:00 PM, Nancy Fox <na...@nancyafox.com> wrote:

I'm working with an open source scrum team and interested to hear from anyone else that has experience with open source projects.  What kind of tools work best for open source scrum teams?  How do you interact with the public for managing feature request and scrumboard communication?

--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumallianc...@googlegroups.com.
To post to this group, send email to scruma...@googlegroups.com.
Visit this group at http://groups.google.com/group/scrumalliance?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Cheers
Mark Levison
Agile Pain Relief Consulting | Writing
Proud Sponsor of Agile Tour Gatineau Ottawa Nov 28, Toronto 26 and Montreal 24

[Nancy Fox]

This is an enterprise level, full dedicated scrum team.  There is a dedicated scrum development within the company to the project/product, but we also have a public facing open source aspect and would like to expose what we are doing to the public and manage dev request. issues from that perspective also.  We have been using VersionOne but it is very limited with what we can do and would ideally like something that we could integrate possibly with Github.

Thanks,

Nancy Fox, CSM

[Ran Nyman]

Hello Nancy, I have worked with such a team.

We did not expose outside our Sprint content instead we exposed release contents and gave open source community change to vote items for the releases (and also contribute code for releases). We had issue tracking system where we and open source community submitted defects and new feature ideas. Issue tracking system was used as single source of information what will come for next releases.

For tooling we had our own infra for issues tracking but you could pick any openly hosted issue tracking system.

Good reading for open source development can be found here:
http://producingoss.com/en/index.html

Best Regards,

Ran

Ran Nyman
+358 44 3410 124
http://rannicon.com

[Mark Levison]

Hmm, I suspect you would benefit from seeing what projects like NUnit, JUnit, robotFramework et al do.

NUnit uses github and features/bugs are pull requests.

Both JUnit and NUnit have  public mailing lists where all features are discussed before implementation. The dev team do a better job because they hear many perspectives.

Other projects use Trello, UserVoice etc. to get weighted udder feedback. These are used more frequently with closed source applications.

Cheers
Mark - writing on a bouncing phone while on a bus.

[Nancy Fox]

Thanks for all the great suggestion...Hopefully with be able to find a solution that works well!

~Nancy