Skip to main content
UploadLanguage (EN)Support
BusinessMobileSocial MediaMarketingTechnologyArt & PhotosCareerDesignEducationPresentations & Public SpeakingGovernment & NonprofitHealthcareInternetLawLeadership & ManagementAutomotiveEngineeringSoftwareRecruiting & HRRetailSalesServicesScienceSmall Business & EntrepreneurshipFoodEnvironmentEconomy & FinanceData & AnalyticsInvestor RelationsSportsSpiritualNews & PoliticsTravelSelf ImprovementReal EstateEntertainment & HumorHealth & MedicineDevices & HardwareLifestyle
Jyaasa Technologies, profile picture
Uploaded byJyaasa Technologies
PPTX, PDF3,596 views

Scrum ceromonies

The document provides an overview of Scrum, an agile framework for managing software development projects, including its ceremonies such as sprint planning, daily scrums, sprint reviews, and retrospectives. It details best practices, roles, and checklists for organizing effective Scrum meetings, highlighting the importance of team collaboration and preparation. The material emphasizes that successful Scrum implementation requires clear communication and trust within the team.

Engineering◦
Downloaded 130 times
Scrum Ceremonies
Ganesh Kunwar - Co-founder and VP of Engineering at Jyaasa Technologies - Certified Scrum Master - Ruby Mentor at GoodMinds Technologies
Overview What is Scrum? Scrum Planning Meeting Daily Scrum Sprint Review Meeting Sprint Retrospective Meeting
Scrum is a framework for managing software development. Jyaasa : We Design, Build and Develop Products What is Scrum? Scrum framework for completing complex project Scrum is an iterative and incremental agile software development framework for managing product development.
Jyaasa : We Design, Build and Develop Products Scrum planning meeting Timebox: Eight hours for a four-week sprint, proportionately shorter for shorter sprints Attendees: The complete Scrum team, including all roles Most important: Team capacity and DoD
Jyaasa : We Design, Build and Develop Products Purpose of Scrum planning meeting A Sprint Goal A Sprint Backlog
Create a recursive calendar invitation include all team members including development and QA. Meeting invitation for agile sprint planning should be from the Product Owner. Jyaasa : We Design, Build and Develop Products Sprint planning Meeting Best Practices Include agenda in the invitation, add the user stories link which should be included in the sprint
Always included more User stories to be included in the sprint then the team’ capacity. Make sure the User story you are proposing from the sprint should be really defined well, all the use cases, functional requirements and condition of satisfaction are in detailed level and, at least, grooming once with some senior team members. Jyaasa : We Design, Build and Develop Products Sprint Planning Meeting Best Practices Order a tea/Coffee with something sweet, sometimes a coffee bribe does work or, at least, it keep the developers or QA not to fell a sleep.
Jyaasa : We Design, Build and Develop Products Sprint Planning Meeting Rules Remember the sprint planning meeting is run by scrum master and he has the highest authority. PO role in sprint planning meeting is only as a contributor, (s)he make active contributor in answering the question if the team have and explaining the user stories to the team. Scrum master is the timekeeper, leader, facilitator, and coordinator of the agile sprint planning meeting
Jyaasa : We Design, Build and Develop Products Sprint Planning Checklist: Product Owner Define Sprint Scope Define each User Story items in detail Prepare notes or include them in the agenda the thing concern, the question for a particular user story so the team can come prepare and have those answers before the before. Make sure backlog is in priority order Describe definition of done for each user story and for sprint
Making sure video, audio conference is reserved and working Pre-order coffee and light refreshment, “no coffee no code” Enough post-it notes and markers, whiteboard etc. Available capacity for the team (team members holidays, public holidays, etc) Keep tracking the team’s velocity vs the amount of work committed by the team Jyaasa : We Design, Build and Develop Products Sprint Planning Checklist: Scrum Master
Jyaasa : We Design, Build and Develop Products Ask questions to clear any ambiguity or else “speak now or hold your“ Do not commit more than you can not deliver Remember to think of your personal availability for the coming sprint. Taking part in technical discussion during estimation or planning poker Sprint Planning Checklist: Development Team
Jyaasa : We Design, Build and Develop Products Input - Team Capacity - Groomed Product Backlog - Business Conditions - Current Product - Definition of Done - Sprint Planning Meeting - Tools And Techniques - Planning Poker - Expert Judgement - Brainstorming - Knowledge Sharing - Collaborations Output - Sprint Goal - Backlog item solutions - Sprint Backlog Summary
Jyaasa : We Design, Build and Develop Products Daily Scrum Timebox: Fifteen minutes is standard, irrespective of the duration of the sprint length Attendees: The complete Scrum team, including all roles Most important: To speak about any impediments
Remain Standing 3 questions agenda Have your project management tool visible It’s a collaborative effort Plan the meeting around the team Jyaasa : We Design, Build and Develop Products Best Practices for Daily scrum meeting
Waiting around your team Introducing new idea Letting people ramble Jyaasa : We Design, Build and Develop Products Avoid
Jyaasa : We Design, Build and Develop Products Scrum Review meeting Timebox: Four hours for a four-week sprint, proportionately shorter for shorter sprints Attendees: The complete Scrum team, including all roles, plus any other stakeholders who are interested in the project success Most important: Demo of working software and assessing the feedback
Jyaasa : We Design, Build and Develop Products Scrum Retrospective Timebox: Three hours for a four-week sprint, proportionately shorter for shorter sprints Attendees: The complete Scrum team, including all roles; the product owner's attendance is optional Most important: To brainstorm and agree on what is working and what is not
Jyaasa : We Design, Build and Develop Products Problems Boring Repeat Same Problem
Jyaasa : We Design, Build and Develop Products
Jyaasa : We Design, Build and Develop Products Team is not a group of people who work together, Team is a group of people who trust each other. Simon Sinek
Jyaasa : We Design, Build and Develop Products Questions