Can product vision creation be a joint exercise between PO Dev and SM..where they collectively come up with a well defined vision that ensures long term alignment
Yes, a joint effort is often the best approach to ensure the product vision is comprehensive and aligned with the overall strategy. It is also very likely that Sr Stakeholders are extensively involved in setting the vision for development.
The difference between User Story and Feature is about the size, if you have something which is small enough to get completed in one sprint, you can work with team and get it developed, but if it takes more time, than you want to make sure it is divided in a manner so incremental development help in learning and delivering value and that is the usual case we create User Stories from feature to support that. So if you have small features you can work directly on them else create user stories to support incremental development
I am software engineer with over six years of experience and i want to pivot to Product owner role. Could you do a video about that ? How to build resume for that, certifications and if there are any advantages of becoming PO with development experience. Thanks in advance. Btw very well made video, your clarity of thought is amazing.
Sir it was very helpful for me to understand about po
Glad it helped
Can product vision creation be a joint exercise between PO Dev and SM..where they collectively come up with a well defined vision that ensures long term alignment
Yes, a joint effort is often the best approach to ensure the product vision is comprehensive and aligned with the overall strategy. It is also very likely that Sr Stakeholders are extensively involved in setting the vision for development.
Please do a job training course for po with no job experience
I make note, as of now we are doing standard programs like CSPO and SAFe PO PM
As a PO, can i ask scrum team to work on features directly or should i give them user stories only ? Request your inputs.
The difference between User Story and Feature is about the size, if you have something which is small enough to get completed in one sprint, you can work with team and get it developed, but if it takes more time, than you want to make sure it is divided in a manner so incremental development help in learning and delivering value and that is the usual case we create User Stories from feature to support that. So if you have small features you can work directly on them else create user stories to support incremental development
Quite helpful. Thankyou
Thank you for checking it out.
I am software engineer with over six years of experience and i want to pivot to Product owner role. Could you do a video about that ? How to build resume for that, certifications and if there are any advantages of becoming PO with development experience. Thanks in advance.
Btw very well made video, your clarity of thought is amazing.
Here is the quick short to start with : ua-cam.com/users/shortspVjhtpavl5E
Thanks very well explained
Glad it was helpful!
Can you do an interview for a new PO
Sure, do you want to support us for volunteering for it ? if yes please drop an email to saket.bansal@izenbridge.com
Please stick to either Scrum Master point of view vs product owner point of view... They 2 absolutely different roles..
Thank you for your feedback.