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 am planning to avail Advanced Roadmap for planning of my project which has just initiated.
Some of the constraints I am having since the project is at initial stage are:
1. There are multiple cross-project dependencies at this stage itself, with each team having either Scrum board or Kanban board.
2. Backlog grooming and sprint planning have visibility up to maximum 1 or 2 sprints. Hence Sprint, Size details are not available.
3. Since there are multiple teams involved, Jira hygiene is a constraint with missing sprint detail, sizing, release plan, dependency etc.
My initial goal is to start with basic project planning, mainly with tracking dependencies and their schedule impacting my schedule and gradually work towards availing Auto Schedule features.
e.g. If project D1 (Dependency 1) has changed its sprint or due date, my project plan should understand it with basic auto scheduling.
In short, I do not want to adjust the schedules manually, however, the Auto-schedule feature is overwhelming for me at this stage with mentioned constraints above.
Please advice how can I start with ARM in this case and what are the mandate of Auto- Scheduling which I need to maintain with each ticket and all boards?
@Ravi Sagar _Sparxsys_ This is indeed a good suggestion to start with.
I might not even use Auto-Schedule feature just now, since the algorithm gives some random date for some of the tickets, which are not realistic (something like Nov 21). Understand, it could be because of combination of not enough details with tickets And selection of All values and Empty values with Sprint, Release and Team.
Thanks for the courses @ https://www.ravisagar.in/courses/mastering-advanced-roadmaps-portfolio-jira.