Roles
Chief Product owner
Clarify req with PO and FO
Prioritize backlog.
Explain the backlog to POs.
Update, justify the product
release to stakeholder.
Product line owner
Maintain knowledge on all
products and functions to
provide info to customer.
Monitor product life cycle and
solutions for all problems.
Product owner
Refines the customer
requirement.
Define acceptance criteria of
required feature.
Submits master epic.
Feature owner
Ensure the consistency of
the features under his
responsibility.
Creates a ticket for
development team after
discussion from PO.
Scrum Master
Ensure Scrum method is
applied effectively in team.
Monitor agile performances
and continuous
improvement.
Development team
Estimates size of backlog
items.
Implementation of
backlog items.
Self organized.
Meetings
2 weeks sprint cycle Backlog grooming session:
• Decompose epic into small
tickets.
• Team will discuss and
estimate ticket with initial
analysis.
Week 1 - Monday
Sprint planning meeting:
• Team will estimate (if
required)
• As per team velocity and
availability, tickets will be
added as per priority in the
sprint.
Daily Scrum:
• What did you do yesterday ?
• What have you planned to
do today ?
• What were problems you’ve
encountered ?
Sprint review meeting:
• Demonstration of
deliverables to the product
owners.
Sprint retrospective meeting:
• Team will provide feedback
about sprint.
• What was good ? What was
bad ?
• What can we improved ?
• What should we stopped to
do ?
Week 2 - Friday
Development process
Start of work package :
• Developer shall pick the ticket from sprint board, and assign to them self.
• Developer shall do initial analysis by changing the state of the ticket to
“In Analysis”. And discuss with FO, if any clarification required.
• Check “SW needed actions “ for what documents shall be updated.
• Once implementation started, change the state of the ticket to “In progress”.
Project setup and implementation:
• Create GIT de environment in local workspace where you will work
repo init -u <manifest_project_url> -m <manifest_file> -b <branch_name>
• repo sync
• repo start <branch_name> (-all if you want to create a branch on all git project)
• Do development according to analysis done.
• make –j7 rebuild (for rebuilding buildset) or build (for building builset
• git add <filepath>
• Generate Quality report for any modification in the code and report shall be
available in the environment.
• Generation and attachment of traceability and code coverage report is required, if
appropriate changes are done (i.e, SRS, SDD, CODE).
• Avoid introducing new compiler warning or LINT/MISRA.
• git commit (use –amend if it is not first time changes ). Integration info should
present in commit message.
• repo upload
• Change the ticket state to “In review” in Jira.
Review:
• Add reviewers in Gerrit.
• In case of -1 or -2 from reviewer,
• if fix is required, upload new patch set as a fix version and reply as
“Done” in Gerrit for all remarks.
• If remark is not valid, it shall be replied as “Rejected” with justification
or “Postponed “ if new ticket is created for that.
• Trigger single pipeline to validate the changes before triggering full pipeline.
• In case of +2 from reviewer, trigger Jenkins (full pipeline to get verified+1).
• In case of +1 from Jenkins, submit the change in Gerrit. Incase of -1 from Jenkins,
check for the failure.
• If Type of the ticket is task, attach the analysis report to the ticket and has to be
reviewed.
• Change the ticket state to “Closed” in Jira.