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 have 3 project running concurrently that will all be dependent on content. The content is very large and made up of 9 major components with many sub components.
It's in the education sector and the content is the actual learning modules.
What is the best way to track the progress? Will a Kanban using a full backlog of estimated work? Or, would they be better off with Iterative analysis and release of content? There's resistance to sprint planning and short term goals.