Customer representative for the Product features, roadmap and evaluation of the product; Complete owner of the Product from Wipro’s side

͏

Do

1. Review the complete Function requirement document with the Architect and the team

• Gain complete understanding of the function requirements through review meetings and other discussions
• Bring the team upto speed w.r.t the requirements and provide the right direction; clarify any queries that may come up
• In case the team has a different point of view, work towards ironing out any differences between the team and the architect for effective resolution 
• Assist the solution architect in preparing the Function requirement document; the Approve the final epics in the document and ensure they are in line with the requirement and expectations
• Explain and communicate all the intricacies in the final document to the team and ensure that every team member is on the same page

͏

2. 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
• Regularly interface with the product and project management; continuously groom the backlogs based on the feedback 

͏

3. 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 is defined properly
• Ensure that the user stories cover all the aspects of the feature like verification, requirement of real note (all the pre-requisites)
• Agreeing on the story point with the team

4. 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
• Ensure the quality is as per the agreed standards
• Make sure that all the documents are verified including any changes that were required to be done by the team as part of the demo

͏

5. Creating the sprint backlog for the teams

• Give the inputs regarding what will be the content for a particular sprint; align the team and gain acceptance on the content; (scrum master and scrum team maintains the sprint board)
• Prioritize the backlog

͏

6. Providing technical assistance to the team

• Analyze the different technical options by understanding various parameters (like cost, priorities, features); {Architect provides other technical assistance to the team that are beyond these parameters}
• Give feedback to the team based on the different options and guide them in taking a final call
• Define & own backlog (product / sprint) and ensure that the requirements are light weight and written in User Story format that needs to be groomed and can be implemented within the   sprint cycle. Define all stories with the required Acceptance Criteria
• Contributes to the product management meetings, to groom the backlog and refine vision statements.
• Owns team backlog and implementation. Drives sprint via prioritized stories.  
• Ensure specific and measurable sprint goals. 100% Availability and contribution to the sprint planning activities so that the sprint goal is attainable. Ensure participation in team demo and accept stories meeting the acceptance criteria.  
• Support to the Scrum Master and team as per mutual agreement. Participation in backlog refinement and estimation sessions. 
• Mapping to customer business/ product management and business teams. Identify integration points in Customer architecture and involve the relevant teams.

͏