There does not appear to be a local user group in Memphis and we are not budgeted for a consultant. I need advice and feedback on implementing JIRA from a business perspective of 'how should we implement' not 'here are the technical configuration steps to implement'.
For example: I have seen JIRA implemented so that each 'department' was a 'project' and all issues for that department were entered under that project. There was a full SDLC waterfall workflow implemented. We had issue types that were not associated with development and had a different workflow. I was going to implement similar process at my new place of employment and I will be the administrator. However, the new development manager has just chosen SCRUM and the Agile add on as our methodology for managing (first dept in the company to do so). But not all issues will be an agile development project. I will need to track all issues together but you have to chose agile as a feature of the project.
Need advise on best implementation.
First, don't worry about the Agile Add-on. See it as a layer on top of JIRA. Even if you start with an Agile project, you can create new issue types later on. It is just a starting point that makes sense with regards to the Scrum methodology.
In my company, we try to create one JIRA project per product/project. Management, for tracking purpose, has the tendency to want everything under the same project. However the project soon becomes a mess. If you really want to do that then you could at least create components by teams or products/projects.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG