I am confused by "Projects". how should I use them?

Question

The guide defines a Project as:

> Typically, a project can be defined as a collection of tasks that need to be completed to achieve a certain outcome.

https://www.atlassian.com/software/jira/guides/projects/overview#what-are-key-elements

This indicates that a project is something that has an end once an outcome is achieved. It would makes sense, but then the examples in the the screenshot make no sense at all. "Customer Experience" is not something that "need to be completed to achieve a certain outcome". It is either a company department or a component of the software development process.

Should my Jira projects copy my company structure? Or software development phases? Or should they mimic my components? Or should they really be projects that will end once the outcome is achieved?

Jeremy Cooley · Answer

Hi @Jack Brickey

I just came across this response and noticed that you use Jira projects for on-boarding and off-boarding. I wanted to let you know that we recently created an HR Professionals community group. It's just getting started so there isn't a ton of activity yet, but we're hoping to make it a place where customers, community leaders, and product managers can talk about how they are using (or wish they could be using) Atlassian Products for HR applications. If that sounds interesting, check it out & join! Thanks!

Jeremy

cc: @Daniel Sedlacek

Daniel Sedlacek_w79pes · Answer

Ok, that makes sense. I wish the guide would clearly say this.

Jack Brickey · Answer

Hi @Daniel Sedlacek ,

in the case of Jira Projects...one size does not fit all. 🙂

examples of how I use define projects:

* Teams - I have set up projects for specific teams that like to get work done. In today's world I would typically use JWM for this.
* Software products - If software development is your thing, then typically you set up a project associated with a specific product and the team can use scrum or kanban. These projects will live as long as the product does even through the Post development support years.
* if software development is your thing, then typically you set up a project associated with a specific product and the team can use scrum or kanban. These projects will live as long as the product does even through the Post development support years.
* Short term projects. Sometimes work has a designated completion, and it is often useful to find a project for this.
* Staffing or other business needs. I have created many on-boarding and off-boarding projects for human resources. I have also created projects for financial teams.