...
Who? | Tool(s) | Why? |
|---|---|---|
Lehigh staff | Jira and Trello | Both tools can support managing work defined by staff with licenses for these tools working within the tools |
Students, faculty, external entities that are not working in the tools | JSM | JSM allows tickets to be submitted and collaboration on those tickets without the reporter needing a license for the product. Technically all of the tools support submitting tasks by sending an email to a specified address but if the submitter wants to continue collaborating on the task once submitted JSM works best. |
What type of work is being done?
What? | Tool(s) | Why? |
|---|---|---|
Software or product development | Jira | Jira has more tools that support agile development such as sprints, burn down charts, and other capabilities that might be overkill for most teams. |
All other work | Jira or Trello | Jira and Trello have features most appropriate for work that falls outside of actual development. Both offer calendar views and Jira offers a timeline view for visualizing tasks in a Gantt chart like view. |
NOTE: Jira is the only tool that currently supports visualizing work across Jira & Jira Service Management so you need to have at least one person with a Jira license that is able to build visualizations that will allow the rest of your teams to see work across those tools if using multiple tools. The Jira Kanban or Scrum board visualizations also provide the most advanced customizations of the boards such as the ability to add swimlanes and move subtasks through the board independent of each other and the parent task.
What is the scope of the work?
...