Outputs:

• Agreed Actionable Improvements: these are the things that the team has come up to address the problem and improve processes.
• Assigned action items and due dates: every action item from above is assigned to a one person and has the deadline
• Proposed Non-functional items for Prioritized Product Backlog
• Retrospect Sprint Logs: A project diary that is available to everyone
• Scrum Team Lessons Learned:

5. Release

5.1 Ship Deliverables

Deliver the solution.
PO helps deploy Product Release and coordinates this with the customer.
Inputs:
• Product Owner, Stakeholders, Accepted deliverable, Release Planning Schedule, Scrum Master, Scrum Team, User Story Acceptance
Criteria
• Piloting Plan: It maps out the deployment of the function in detail.
Tools:
• Organizational Deployment Methods:
• Communication Plan:
Outputs:
• Working Deliverables Agreement: The deliverable is signed off by the customer
• Product Releases: the document includes release content which describes the functionns of the deliverable released

5.2 Retrospect Project

Your whole Scrum team and stakeholders should have a post-mortem meeting after the project is finished.
Po participates in retrospective meeting at the end of the project.
Development Team participates in the meeting.
Inputs:
• Scrum Core Team, Stakeholders
Tools:
• Retrospect Project Meeting
Outputs:
• Agreed Actionable Improvements, Assigned Action Items,

ORGANIZATION

Core Roles

Product Owner
They are responsable for maximizing business value for the project. The PO is the voice of the customer.
They work between the customer and the team, setting priorities based on customer inputs and giving feedback based on workshop they
did with the customer.
The PO represents the stakeholders interests to the Scrum team. They should clearly communicate what is expected of the product and
what the product should do.
The PO needs to understand the Scrum team, the Customer, the User and other Stakeholders.
PO accepts or rejects change that is proposed by the customer. PO needs to know how complex the change is so that they can make a good
decision. Changes are usually requested after the sprint review when the customer sees the result.
The change can also come from the scrum team, usually when they are working on the deliverable, during standup or in some other way.
The responsibility of the PO stays the same.

Scrum Master
This person manages the whole Scrum process.