Hello,
I work in a smaller non-profit healthcare organization IT department and the way we currently use Jira is this:
- Projects based on teams and/or applications (mostly scrum projects as we work in two week sprints)
- Boards based on teams, and/or projects but also have a main sprint board that pulls everything in as many of our resources work cross-functionally and need one view to manage their work
- Epics are equal to a project and these are created within the Jira Software project that makes the most sense, usually based on what team the project lead belongs to
We will be migrating to the Cloud in just a few months and are assessing our current processes to see if there is anywhere we can streamline things and/or simply.
One of my co-workers mentioned that best practice for Jira Software is to create a new project every time there is a new project started and then archive it when the project is completed. So, with that theory, we'd create a new Jira Software project which may house only one or several Epics (projects) and then it'd be archived when the project or initiative is complete. My issue with this or question I guess is, how would you then have one board or view that pulls in everything for the active sprint? Right now our board is pulling based on a filter that identifies our Jira Software projects, but if we are constantly creating new Jira Software projects and archiving them, wouldn't we have to constantly be updating that filter also? How are other organizations using Jira to manage work? Is there a best practice?
Any thoughts or feedback would be greatly appreciated.
