Roles Meetings Development process

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