Uploaded by Christian Linandry


Christian Linandry Wijaya - 2101687104
Its primary inputs are newly envisioned product ideas from product planning. The primary outputs are a
portfolio backlog and a collection of in-process products.
Differences :
-Daily Scrum is a 15-minute time-boxed event for the Development Team.Daily Scrum is held every day
of the Sprint. At it, the Development Team plans work for the next 24 hours.
-Sprint Execution is performed during each Sprint by the Scrum team to meet the Sprint goal.Sprint
Execution starts after Sprint Planning and ends before Sprint Review. For a two-week Sprint, the
duration of Sprint Execution lasts for 8 to 10 days.
Similarities :
The development team always held these both activities (daily scrum and sprint execution) everyday of
the sprint
In Scrum, the sprint planning meeting is attended by the product owner, ScrumMaster and the entire
Scrum team. Outside stakeholders may attend by invitation of the team, although this is rare in most
During the sprint planning meeting, the product owner describes the highest priority features to the
team. The team asks enough questions that they can turn a high-level user story of the product backlog
into the more detailed tasks of the sprint backlog.
Step 1: Review your product roadmap
Step 2: Groom your product backlog and update user stories
Step 3: Propose a sprint goal and backlog before the sprint planning meeting
Step 4: Use data and experience to supercharge your Sprint planning meeting
Step 5: Walk through each user story and describe what tasks need to be done
- Sprint execution planning
- Flow Management
- Daily Scrum
- Task Performances/Technical Practices
- Communication
-Planning the value that will be delivered
- Be sure to agree a sprint goal
- Plan how the work will be done
- Hold a daily scrum
- Refining the product backlog
Review the Sprint’s results : The PO reviews which items from the product backlog were completed
during the previous Sprint and explains any that weren’t.
Discuss and demonstrate the work: The team follows up by discussing their successes and pain points
during the Sprint. Then they hold a live demo of the finished software (or relay their completed work in
whatever medium is appropriate). Finally, the team answer any questions related to the Sprint’s
Update the status of the project: The PO discusses the current state of the product backlog and restates
the scope of the project going forward.
Collaborate on the plan ahead: Finally, the team, stakeholders, PO, and any other meeting members
work together to finalize next steps with respect to the insights gained throughout the meeting.
The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. This is at
most a three-hour meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.
During the Sprint Retrospective, the team discusses:
What went well in the Sprint
What could be improved
What will we commit to improve in the next Sprint