Application Architect - Bengaluru, India - Wipro Limited

Wipro Limited

Verified Company

Bengaluru, India

2 weeks ago

Posted by:

Deepika Kaur

beBee Recuiter

Description

Overview:

Role

Customer representative for the Product features, roadmap, and evaluation of the product. Strong knowledge and experience on Telecom 4G/5G domain._

Responsibilities and Tasks

Accountable for the requirements.
Clarifies the high level requirements with the customer unit.
Allows time for Retrospective action points.
Defines the sprint goal ? together with the team.
Responsible for slicing the user stories that fits the sprint cycle.
Cancels and re plans the sprint if necessary.
Transparently communicates towards the customer unit.

Participate on team ceremonies
Planning/ review(demo) mandatory.
The rest of the ceremonies are optional.
Product owners stand up for product quality and integrity by setting Definition of Done and Acceptance Criteria for Team deliverables.
Product owners focus heavily on delivering value for the customer on time with quality.
Product owners are responsible for features that the teams are working on, owning the features
Product owners presents the feature level progress to stakeholders
Product owners have enough solid technical knowledge of the product to:

o Identify customer value and customer risk;

o Understand product quality and measurements;

o Clarify and break down customer requirements;

o Define the DoD at an appropriate level.

The Product Owner works with a Team to:

o Participate in planning to prioritize task/user stories and set a weekly/sprint goal;

o Verifies in reviews whether the DoD and Acceptance Criteria are met;

o Participate in retrospectives but on team request;

o Answers questions and clarifies requirements;

Backlog grooming & scope agreement
Read and understand the document which is to be signed off or already signed off
Enable the team to assess, analyze and understand the deliverables and the development criteria
Usually, backlog grooming happens three weeks before the sprint starts
Work with various stakeholders to iron out any differences or lack of clarity among various stakeholders
Epics breakdown to user stories and writing acceptance criteria; Epics breakdown should be broken to user stories in such a way that the product is created in incremental steps (user stories should be meaningful and deliverable)
Breaking down the bigger task into smaller user stories such that each user story is deliverable
Ensure that the acceptance criteria are defined properly
Reviewing and approving Demos (which team gives as part of the work)
Validate the acceptance criteria
Anticipate any potential pitfalls from the customer viewpoint and take measures to correct the same
Creating the sprint backlog for the teams
Give the inputs regarding what will be the content for a sprint; align the team and gain acceptance on the content; (scrum master and scrum team maintain the sprint board)
Prioritize the backlog