Re: Sprint demo meeting...
- PO and BA can be the same person - they are just roles.
Although the qualities that you need from a PO are distinct from the
qualities of a BA.
The PO needs the power to prioritise and accept the team's work.
He/she must be empowered to make the business decisions that sometimes
hold teams up.
With their BA skills , they should be able to drill down on stories
and help the team uncover complexity.
Regardless of whether this is all one person, it is important that
they have the quality to collaborate and not feel too defensive about
their stories etc.
you get one individual who knows what is to be built and has the
executive power to get things built.
Its easier to site this person close to the team (rather than 2 or
with a joint BA/PO role, you have someone who may has alot of work on
their plate and helping them to make time to support your team may be
very hard. (They may be PO on this project and BA on others!).
Watch out for scope creep - as a BA they may uncover stuff that needs
building but try and get the team to build it for free (rather than
put their PO cap on and get it into the backlog and prioritised!).
Value your PO, the better your team gets, the worse the PO's job, they
have to get stories defined faster (if they are also the BA, they have
to get the guts of the stories done faster too! - they can easily
become the bottleneck in your pipeline!
hope this helps.
--- In email@example.com, "Jaideep Khanduja"
> This question is in context with an organization aspiring to be Agile.
> Can Business Analyst and Product Owner be same for a product? What
> the pros and cons?attachments to this message are intended for the exclusive use of the
> Best Regards,
> Confidentiality Notice:
> The information contained in this electronic message and any
addressee(s) and may contain confidential or privileged information.
If you are not the intended recipient, please notify the sender at
admin@... immediately and destroy all the copies of this message and