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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Time Estimation in Agile for Business Analyst and Product Owner Roles

In Agile how can the time be accounted for Business Analyst and Product Owner Roles.



Log in or Sign up to comment

Our BA's are not on the actual development agile teams for our internal system products.  We have the BA work under their own project board, and share "EPIC" topics across BA and development boards.  This is sort of a hybrid waterfall and scrum approach.  We have the BA's point their work and manage in sprints.  Project managers track hours for the BA's outside of the Jira tool.

Like # people like this

Thank you for the reply its interesting how various organizations Agile mindset is applied slightly differently.

2 more questions for Business Analyst and Product Owner Roles 

1) In the above scenario are your BA's  part of the daily scrum call?

2) Seem Like Product Owners also have their own project board.

Like Imran Taqvi likes this

1) for the BA's, they are not part of the daily scrum call, but the BA does participate in the development team grooming when it is the BA's story being reviewed.  The PO is on the daily call and can relay questions back to BA's if needed. Otherwise, Jira is used to  @ mention BA author by name on questions.  Questions might be posed by the PO, dev team System Analyst, head developer or even the scrum master...just depends on the team.

2) Yes, PO's have two boards they help prioritize, the BA board of work that is being vetted and approved so that reqmts can be drafted (before it even gets to the dev board), then the PO also is prioritizing all the work of the dev team board and sprints.  The PO is vetting out priority and approval of small enhancements on the BA board, but large corporate project work the scope is already approved to the PO is more of a reviewer of these requests and then help organize all the project and enhancement priorities as part of standard scrum ceremonies with the development team.

Like Imran Taqvi likes this

This helps great. TY.

We also faced questions about the evaluation of different roles. Our task was to make sure that all the work was taken into account in the sprint, and that's why we came up with our Scrum Assistant plugin.

Try it in use and then you will always have a transparent dynamics of the work of the whole team.

AUG Leaders

Atlassian Community Events