Hi Matt,<div><br></div><div>Unfortunately I wasn't at AstriDevCon and I'm not entirely sure how you currently manage the different projects that go into major releases; but we utilise Jira heavily at my place of work and it seems like you could too (outside of just making jiras and working on them). Firstly, the wiki page in Confluence is a great "human readable" overview of what the project is, what it aims to do, what's going to be involved and so I'd absolutely keep that; but it seems like you'd want more within Jira itself - for the people working directly on the project.</div>
<div><br></div><div>Firstly, this process seems like a lot of work (and I wasn't a fan when we changed over to this), but it really does help and makes the team working on the project very clear on what needs doing, what the requirements are etc.</div>
<div><br></div><div>When we get a project in, we get a list of requirements with it - this comes in the form of an "Epic" jira, which has a list of requirements within it.</div><div><br></div><div>We, as developers, break these requirements down into chunks of work called "stories", each story is a deliverable - this would maybe be a little different for you, but i can imagine a story would be "construct AMI events", "construct AGI" and so on. Stories are high level bits of work.</div>
<div><br></div><div>These stories get linked to the Epic as "fulfilled by" in Jira.</div><div><br></div><div>Then within each of these stories we break down everything that we need to do to complete that story. These are called "dev tasks" within our workflow and are sub tasks to the story within jira.</div>
<div><br></div><div>In the end you should have your Epic (with requirements), Stories which are linked to the epic (all your stories should complete your requirements) and then dev tasks which are sub tasks to the stories.</div>
<div><br></div><div>I'm not sure on the limitations of your Jira installation as I know Atlassian give different plans different functionality.</div><div><br></div><div>This would then allow you to make dashboards (if you wanted) for different projects; allowing people to glance at a project and really understand where everything is etc.</div>
<div><br></div><div>Like I said at the beginning, you might already be doing all of this within Jira; but I've had little experience of your workflows within Jira (only ever submitted bugs).</div><div><br></div><div>
Am I telling you something you know about already?</div>
<div><br></div><div>Dan</div><div class="gmail_extra"><br clear="all"><font face="arial, helvetica, sans-serif" color="#333333">-- <br>Dan Jenkins - Senior Web Developer<br>email: <a href="mailto:dan.jenkins@holidayextras.com" target="_blank">dan.jenkins@holidayextras.com</a><br>
twitter: <a href="http://twitter.com/dan_jenkins" target="_blank">dan_jenkins</a><br>linkedin: <a href="http://www.linkedin.com/in/jenkinsdaniel" target="_blank">jenkinsdaniel</a><br>skype: <a>d-jenkins</a></font><div><font face="arial, helvetica, sans-serif" color="#333333">blog: <a href="http://www.dan-jenkins.co.uk/" target="_blank">www.dan-jenkins.co.uk</a></font></div>
<div><font face="arial, helvetica, sans-serif" color="#333333"><a href="http://about.me" target="_blank">about.me</a>: <a href="http://about.me/dan_jenkins" target="_blank">about.me/dan_jenkins</a></font></div><br>
<br><br><div class="gmail_quote">On 3 November 2012 03:01, Matthew Jordan <span dir="ltr"><<a href="mailto:mjordan@digium.com" target="_blank">mjordan@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello all -<br>
<br>
One of the topics discussed at AstriDevCon was how we could, as an open<br>
source project, better coordinate efforts between developers on major<br>
projects being developed for Asterisk 12. One idea that came up was to<br>
have a page on the Asterisk wiki for each major project and - on that<br>
page - provide information for developers to aid in collaboration.<br>
Information could include things like:<br>
* The subversion feature branches being used for active development for<br>
that project<br>
* Tracking of the efforts that have been done on a project, what efforts<br>
are currently in progress, and what still has to be done<br>
* Convey the requirements for the project, high-level design, and other<br>
useful concepts for software development<br>
* Link to other pertinent information related to the project (RFCs, etc.)<br>
<br>
The pages should *not* be used as a means for discussion - that has<br>
historically worked quite well on the mailing lists, and the consensus<br>
was to keep it that way.<br>
<br>
As such, we've created a draft project planning template on the Asterisk<br>
wiki:<br>
<br>
<a href="https://wiki.asterisk.org/wiki/display/AST/Project+Planning+Template" target="_blank">https://wiki.asterisk.org/wiki/display/AST/Project+Planning+Template</a><br>
<br>
If everyone thinks this is a good idea, I'll make the template an actual<br>
wiki template on the Asterisk wiki, so pages can be made directly from<br>
it (and I'll update the Confluence Tips page to explain how to do<br>
that!), as well as keep it in the Policies subsection.<br>
<br>
Feedback welcome!<br>
<br>
Thanks,<br>
<br>
Matt<br>
<br>
--<br>
Matthew Jordan<br>
Digium, Inc. | Engineering Manager<br>
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA<br>
Check us out at: <a href="http://digium.com" target="_blank">http://digium.com</a> & <a href="http://asterisk.org" target="_blank">http://asterisk.org</a><br>
<br>
<br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
</blockquote></div><br></div>