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 Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I was given this task by the CEO. Come up with a naming convention for our sprints that embed more information in the name, like the VIN of a car. I think he's asking to see some info about what types of things were worked on (which modules, etc.). Any bright ideas?
We currently simply number our sprints (Sprint 1, Sprint 2, etc.). I'm afraid of losing the value that comes with ordinal sprint numbers. Has anyone successfully done something like this?
Hello @Nate Mark
Welcome to the Atlassian community!
How is the CEO getting information about the sprints?
Depending on how they get their information, maybe you could enter that information into the Sprint Goals field instead?
Or you could use Components or Labels (or another custom field) in the issues to identify the modules impacted by the work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.