Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,283
Community Members
 
Community Events
176
Community Groups

Creative Agency Sprints

I'm working with a creative agency to adjust the way they manage work in Jira (not JWM) going from Kanban boards mainly to a 2 week Sprint model. I have had a few a challenges and have mitigated them in the best way I thought possible. However I'd love to hear your feedback and perspective.

The the first challenge I had was, since marketing efforts are tied to different clients there are an array of client project boards. So I created a filter to pull them all together into 1 project. This works for now, I just need to make sure every project is using the same screens so the team work off this board in unison. 

Secondly, due to the nature of the work some people are working the same issue at the same time so it's hard to REALLY see what someone has on their plate since it's assigned to only 1 person. I thought to create a custom assignee field in addition to the preexisting one. 

Lastly, this marketing team does monthly marketing reports for some clients, the previous PM's have a made a Jira ticket lasts until the end of time. The way I mitigate that is with automation that once it hits DONE the reporting ticket is cloned and put into the backlog. Ready for use again next month. The only other way I see to do is to have PM's recreate the tickets every month. 

What do you think?

 

1 comment

Interesting use case. I am wondering if it might be easier to have a list of sub-tasks for everyone working on one bigger issue [aka epic or story] so that it is clearer who is doing what and what is the overall progres on the task?

@Marta Woźniak-Semeniuk - good point - something I forgot to do is mention the board is organized by person not epics 

Comment

Log in or Sign up to comment