You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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?
Hi @Daniel Sedlacek ,
in the case of Jira Projects...one size does not fit all. 🙂
examples of how I use define projects: