the team is not mature in agile, and i'm not able to convince them of the benefit of creating tasks! they create generic once like each user story has three tasks, one as BE, and one as UI and one as integration. this does not really give the team any transparancy as what is being worked. I am encouraging them to create tasks every day for what they plan on deliverying in a daily basis but they think this is micromanagment! I beleive a task should be self-explanatory and reflect on a job that shouldnt take more than one day of work!
any help or resources I could share with the team? cuze it's hard to manage the progress of our sprint if i cant measure it
There are 2 aspects here :
I would suggest having a discussion with the team and explain what you're trying to achieve and why - be transparent and you may get better buy-in from the team.
Suggest trying to "meaningfully" break all issues down into tasks for 1 sprint so that you and the team can see what benefits you get from it - inspect and adapt after that.
Worst case scenario is that the team doesn't break down any issues - but as Scrum Master you can insist that each issue has a time estimate. Then you can track progress by looking at a time burndown chart
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs