This was actually quite helpful. I am currently transitioning from BA to product owner. I am actually with the same team as before, but previously my focus was writing user stories and acceptance criteria, and “suggesting” features to implement that I thought would be helpful. This video is great to outline how my approach must change. Instead of thinking about how to implement new features, I need to think about problems to solve. The WHY seems to be almost more important than the WHAT. It’s not that I didn’t care about the WHY before, it’s just that at the end of the day I just wrote down what I was told needed to be built. I have a better understanding of my role now (I think). It’s more than just the authority to drag user stories up and down in the backlog.
Thank you, David. Could you please advise? If my product deals with some complex logic: puzzling algorithm or formula to calculate some chart or widget value. Should the team (Devs + QAs + PO) investigate the proper rules? Who should document the description, diagram, spreadsheet in acceptance criteria? I can hardly imagine developers spending time on science papers research. Thanks again
Yes, I am in this same transition from a Business Analysis to Product Owner
This was actually quite helpful. I am currently transitioning from BA to product owner. I am actually with the same team as before, but previously my focus was writing user stories and acceptance criteria, and “suggesting” features to implement that I thought would be helpful. This video is great to outline how my approach must change. Instead of thinking about how to implement new features, I need to think about problems to solve. The WHY seems to be almost more important than the WHAT. It’s not that I didn’t care about the WHY before, it’s just that at the end of the day I just wrote down what I was told needed to be built.
I have a better understanding of my role now (I think). It’s more than just the authority to drag user stories up and down in the backlog.
Thank you. I am quite happy to know it.
Thank you, David. Could you please advise? If my product deals with some complex logic: puzzling algorithm or formula to calculate some chart or widget value. Should the team (Devs + QAs + PO) investigate the proper rules? Who should document the description, diagram, spreadsheet in acceptance criteria? I can hardly imagine developers spending time on science papers research. Thanks again