Question 1 – Evaluates on the overall communication skills
 Clarity on message sent
 Communicating the message to all relevant parties
 Timeliness
 Specificity
Note:
communication wise it is very much clear, but after the meeting they do not share the
message to all the relevant parties.




Many things we get from Developers instead of Product owners. But I feel
Product owners are responsible for communicating with stakeholders across the board, including
customers, business managers, the development team and QA team to make sure the goals are clear,
and the vision is aligned with business objectives. Everyone needs to be on the same page for a
project to work effectively.
Product owners should meet with their teams [Developers and QA] to refine the process, identify
areas for improvement, and support the sprint which is missing here.
Every product release needs a goal release date — even if it’s a rough estimate.
This should give you flexibility to adapt to a change in priorities. But it should restrict scope creep by
limiting how many features stakeholders can add.
We know that scope, budget, and time, weighing priorities according to the needs and objectives of
stakeholders but As the project evolves, the product owner will have to gauge which areas have flexibility and
which don’t to determine how and when each iteration and product element will be developed.
Every product release needs a goal release date — even if it’s a rough estimate.
This should give you flexibility to adapt to a change in priorities. But it should restrict scope creep by limiting
how many features stakeholders can add.
Question 2 – Product Requirements
 How exhaustive are the requirements ?
 How elaborate are the requirements ?
 How specific are the requirements ?
 Ad-Hoc changes in the requirements
Note:
Requirements are discussed in call only but not documented anywhere. and the requirements are changes
continuously and discussed in call but not documented.



The PO should work with the team to agree on accepted story completion. This includes validating
that the story meets acceptance criteria, that it has the appropriate, persistent acceptance tests, and
that it otherwise complies with its Definition of Done (DoD). In so doing, the PO also assures a level of
quality, focusing primarily on fitness for use.
While POs are not expected to drive technological decisions, they are supposed to understand the
scope of the upcoming enabler work and collaborate with System and Solution
Architects/Engineering to assist with decision-making and sequencing of the critical technological
infrastructures that will host the new business functionality. This can often be best accomplished by
establishing a capacity allocation, as described in the Team Backlog article.
User Story's Acceptable Criteria must be clearly defined, otherwise it becomes difficult to judge
whether story is Done or not and when the team struggles to clearly define how a feature should be
tested, it may indicate an issue.


The User Story shall be testable and used as one of the inputs for QA.
The User Story is easy to evaluate and helps estimate the time required for implementation.

The User Story should contain a valuable function that can be developed during a Sprint and has a
specific outcome


The User Story should be short and easy to read, understandable to all.
It is essential to understand that a User Story is a small target for a successful product.
Question 3 – Jira Management
 Informing which tickets to be prioritized
 Moving the tickets to appropriate queues if tickets are assigned on their name
Note:



Tej:
The product owner’s responsibility is to create the list of backlog items and prioritize them based on
the overall strategy and business objectives. We never have backlog items prioritised.
Product backlog will change frequently, the product owner must make the list accessible and available
to all stakeholders (particularly developers, QA) to ensure optimized performance and project
outcomes.
The Product Owner is required to have the Backlog sequenced prior to the Sprint Planning Meeting.
This means that each user story must be ordered by relative importance.
Product owner roles and responsibilities
Agile product owner takes on several roles, including business strategist, product designer, market analyst,
customer liaison, and project manager.
1. Defining the vision
Product owners are responsible for communicating with stakeholders across the board, including customers,
business managers, and the development team to make sure the goals are clear and the vision is aligned with
business objectives. Everyone needs to be on the same page in order for a project to work effectively.
A product owner can help the team maintain that vision is by creating a product roadmap.
2. Managing the product backlog
scrum product owner is managing the product backlog.
The product owner’s responsibility is to create the list of backlog items and prioritize them based on the
overall strategy and business objectives.
product backlog will change frequently, the product owner must make the list accessible and available to all
stakeholders (particularly developers,QA) to ensure optimized performance and project outcomes.
Managing the product backlog
The primary responsibility of the role of a Product Owner is managing the product backlog. Today’s
market is really dynamic and every customer wants to stay on the top of the latest trends in the industry.
This product backlog is derived from the roadmap created by the Product Owner. Even the items in the
product backlog might require some movement due to changing priorities. It is the Product Owner’s
responsibility to build up a stack of items in the backlog and prioritize them as per the business goals and
the global approach. The product backlog is a dynamic list of items and as we call it in agile, it is a ‘live
document’ that should be frequently updated, based on changing project requirements, all the way through
to development. The Product Backlog exists as long as there is a Scrum team that works on the product.
Prioritizing and Ordering Items in the Product Backlog:
Another area where the product owner focusses on is to prioritize the needs of the stakeholders. A product
owner should be able to determine the priority of product backlog items in order to deliver the maximum
outcome. The Product Owners are constantly in touch with the stakeholders and understand the
environment in which the product operates. When the needs and market conditions for the product change,
the Product Owner will change the priorities in the Product backlog. He / she may add new items in the
Product Backlog and remove the ones which are now obsolete due to new stakeholder needs. This means
that the Product Owner must order the items in the Product Backlog to best achieve goals and missions.
There are many tools to help Product Owners do this. The Product Owner is required to have the Backlog
sequenced prior to the Sprint Planning Meeting. This means that each user story must be ordered by
relative importance. The Product Owner will determine what needs to be developed in each iteration and
how the product element will be developed over the life of the product.
3. Prioritizing needs
scope, budget, and time, weighing priorities according to the needs and objectives of stakeholders.
For example, if the product under development needs to launch within six months, that constrains the scope
of the project. As the project evolves, the product owner will have to gauge which areas have flexibility and
which don’t to determine how and when each iteration and product element will be developed.
4. Overseeing development stages
agile product owner works with stakeholders to identify and organize the steps required for the next iteration.
They will then meet with their team to refine the process, identify areas for improvement, and support the
sprint.
5. Anticipating client needs
The successful scrum product owner will be an expert at understanding and anticipating the client’s needs to
more effectively manage the development process.
Their deep market knowledge and communication skills allow them to anticipate problems or needs and
address them.
6. Acting as primary liaison
The product owner is also the primary communicator and link between stakeholders and teams. As such, they
have to be expert communicators, making sure there’s buy-in from stakeholders on all major decisions and
strategy and clear instructions and deliverables for the developers.
7. Evaluating product progress at each iteration
The product owner is accountable for each stage of the development process and the final product
https://www.scaledagileframework.com/product-owner/
https://medium.com/agileinsider/tips-tricks-for-writing-user-stories-like-a-pro-product-owner-guide-part-iifc9fa0c6538a