tag:blogger.com,1999:blog-30978416.post7218063117944622096..comments2023-04-05T15:22:55.100-07:00Comments on Agile Advocate: Jira and GreenHopper for agile project managementBrad Swansonhttp://www.blogger.com/profile/03081884860431841622noreply@blogger.comBlogger12125tag:blogger.com,1999:blog-30978416.post-15160314388594035222010-08-11T07:21:51.903-07:002010-08-11T07:21:51.903-07:00What you think about JIRA's UI and overall usa...What you think about JIRA's UI and overall usability? One of my friends started using JIRA when he switched jobs (he used our <a href="http://www.bananascrum.com" rel="nofollow">Scrum tool</a> before), and after a few weeks of using it he complains that navigating projects in JIRA+Greenhopper is a nightmare: complex and unintuitive. <br /><br />How do you rate it as a long-time user?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-30978416.post-78791471039282979932010-07-05T21:50:19.958-07:002010-07-05T21:50:19.958-07:00This comment has been removed by a blog administrator.Project Management Softwarehttp://www.project-drive.net/noreply@blogger.comtag:blogger.com,1999:blog-30978416.post-1873419975251288032010-06-21T02:01:20.869-07:002010-06-21T02:01:20.869-07:00This comment has been removed by a blog administrator.IT Support Sherman Oakshttp://www.dcgla.com/small-business-computer/it-support-sherman-oaks.htmlnoreply@blogger.comtag:blogger.com,1999:blog-30978416.post-54008795983076409612010-06-09T23:21:36.209-07:002010-06-09T23:21:36.209-07:00This comment has been removed by a blog administrator.Project Management Softwarehttp://www.project-drive.net/noreply@blogger.comtag:blogger.com,1999:blog-30978416.post-45869643500580423982010-03-12T00:20:54.091-08:002010-03-12T00:20:54.091-08:00Hi Brad, I think that finally I'm able to expl...Hi Brad, I think that finally I'm able to explain myself in a better way. After my first evaluation of JIRA+GH I realize that even if this tool is great for organizing your development effort it's not the best tool for initial planning and especially for getting initial user requirements by User Stories.<br />So I configured a series of Confluence (Wiki) templates for creating and discussing user stories in a collaborative way. Only when we approved one of this US we move it as a formal requirement into JIRA+GH.<br /><br />So, far I think this approach helps to get the best of the two worlds.Unknownhttps://www.blogger.com/profile/05047040619939489686noreply@blogger.comtag:blogger.com,1999:blog-30978416.post-31958814504957742872010-03-10T09:13:36.905-08:002010-03-10T09:13:36.905-08:00Hi Brad, I started down a similar path of using JI...Hi Brad, I started down a similar path of using JIRA versions to represent iterations, and found that even with GreenHopper, the JIRA-generated release notes are no longer useful. Although GH gives the ability to group versions together into releases, there isn't always a clear parent-child relationship between iterations and releases. <br /><br />Your original post already gave the example of a bug fix against a previous release being mixed into an iteration of stories for a subsequent release. Or, along the same lines, you might have some experimental activity that isn't going to be released with the rest of the stories in the iteration. <br /><br />This makes sense for velocity tracking--all these activities take time and count against your velocity, limiting the number of other stories you can complete. But the JIRA release notes are now no longer useful - they give you a list of things in an iteration, which may be a combination of multiple releases or some things that aren't being released at all. <br /><br />Ideally, there would be a way to extract the set of JIRA issue keys for release notes from SVN logs instead of by a set Fix Version/Iteration.Anonymoushttps://www.blogger.com/profile/10473101381793442268noreply@blogger.comtag:blogger.com,1999:blog-30978416.post-79119367148493495902009-12-24T09:49:35.240-08:002009-12-24T09:49:35.240-08:00What specifically do you find too complicated? In ...What specifically do you find too complicated? In my opinion, it's easy to create a new user story in Jira. Just click the "Create new issue" button and go! The fields to fill in are easy to understand. You can also use the "New Card" button on the planning board view, which shows fewer fields and might be easier to learn.Brad Swansonhttps://www.blogger.com/profile/03081884860431841622noreply@blogger.comtag:blogger.com,1999:blog-30978416.post-45650796537913593932009-12-22T01:41:10.111-08:002009-12-22T01:41:10.111-08:00Thanks a lot for you reply.
I'm talking about...Thanks a lot for you reply.<br /><br />I'm talking about internal users, we have to educate them on the use of JIRA anyway(as we are using it for incident tracking), but the problem is that I find JIRA+GH too complicate for simple User Stories writing, maybe creating a simplified client of JIRA with a basic layout could be developed, or just using a different tool. But I'm also worried about duplicating functionality.Unknownhttps://www.blogger.com/profile/05047040619939489686noreply@blogger.comtag:blogger.com,1999:blog-30978416.post-6821455698115572972009-12-19T11:46:42.280-08:002009-12-19T11:46:42.280-08:00For large organizations with a need for portfolio ...For large organizations with a need for portfolio management, Rally Enterprise and VersionOne enterprise have rich feature sets for multi-project portfolios, although I don't have much experience using them myself. I intend to dig deeper into those two to learn more.<br /><br />Jira simply doesn't support cross-product feature hierarchies, roadmap planning and portfolio planning IMO.<br /><br />I compared some open source tools in <a href="http://olex.openlogic.com/wazi/2009/comparing-open-source-agile-project-management-tools/" rel="nofollow">this article</a>. Among these, AgileFant probably fares the best for portfolio management but the lack of "Epics" (feature hierarchies) is a serious limitation. IceScrum has some features for large organizations but still is lacking in others.Brad Swansonhttps://www.blogger.com/profile/03081884860431841622noreply@blogger.comtag:blogger.com,1999:blog-30978416.post-43098699995143902482009-12-19T11:35:37.030-08:002009-12-19T11:35:37.030-08:00Regarding emachado's question: Do your custome...Regarding emachado's question: Do your customers have access to Jira? Are they internal or external customers? For internal customers with access to Jira, you would need to educate them on how to write good user stories, and then I would create a Jira version called "requests" where those could be analyzed and ranked by the product owner. For external customers, you _may_ be able to setup Jira roles and security in a way that gives them access to make requests and report bugs but nothing else; I don't know for sure if Jira supports that, though. You could certainly host a separate Jira instance, or other ticket tracking system for external customers, and import those items into your internal Jira backlog. Good luck teaching external customers to write good user stories, though!Brad Swansonhttps://www.blogger.com/profile/03081884860431841622noreply@blogger.comtag:blogger.com,1999:blog-30978416.post-12078123111322105432009-12-18T13:23:01.467-08:002009-12-18T13:23:01.467-08:00Brad, you've now reviewed a number of tools. ...Brad, you've now reviewed a number of tools. For an enterprise with 10 teams and multiple projects in a portfolio what do you recommend? Keeping in mind the need for some simple Kanban stuff as well as more in depth portfolio management.<br /><br />- Bob -Bob Hartmanhttp://www.agilebob.comnoreply@blogger.comtag:blogger.com,1999:blog-30978416.post-2004162632301281302009-12-18T12:48:14.191-08:002009-12-18T12:48:14.191-08:00What I'm missing in a JIRA+GH enviroment is a ...What I'm missing in a JIRA+GH enviroment is a way to get customers to write their own User Stories. Any advice on how to do this using another tool if needed.Unknownhttps://www.blogger.com/profile/05047040619939489686noreply@blogger.com