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.
We are doing a data lake project where we use scrum. We have a certain project team, deadlines, etc and we do sprints to plan our work load. With great success! But between this bigger projects we have smaller tasks and changes. My approach would be to still continue with this two week sprint planning and to clean the backlog, building a sprint etc. And if a new bigger project with more importance will apear just to focus on this tasks with appropriate story pointing etc. But I am not 100% sure if this is the proper way, maybe somelse has experience in this kind of field? In a data lake project we will have to improve, adapt, etc. anyway in cirlces due to the CRISP model.
For me this is project and change Management with no hard sperations realized with scrum....