Scrum Fundamentals Quiz

• Agile Scrum is an Agile methodology
• It is an iterative incremental process for software development
• It is an approach that controls the chaos of changing requirements
• Agile Scrum uses a team based approach to development
• The whole team travels the distance as a unit, like in Rugby
• Scrum was first introduced in 1995
• Scrum is a way for team collaboration to solve complex problems
• Scrum is an agile methodology focusing on breaking projects down into sprints
• Scrum encourages teams to learn through experiences
• It encourages teams to self-organize while working on a problem
• It encourages teams to reflect on their wins and losses to continuously improve
• The Scrum Team takes part in five events
• It produces three artifacts
• Scrum is an empirical process using observation, experience, and experimentation
• Scrum has three pillars: transparency, inspection, and adaptation
• The three pillars support the concept of working iteratively
• Trust is a critical Scrum Team characteristic that binds all of the elements together

Scrum Values

• Courage for Scrum Team members to do the right thing and work on tough problems
• Focus means everyone focuses on the work of the Sprint and the goals of the Scrum Team
• Commitment means people personally commit to achieving the goals of the Scrum Team
• Respect means Scrum Team members respect each other to be capable, independent people
• Openness means the Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work
• Scrum creates adoption
• Scrum looks to get value first
• Scrum is team focussed

Scrum Structure

• Product Backlog proceeds Sprint Planning
• Sprint Planning proceeds Sprint Backlog
• 1 Scrum Team then commences Daily Scrum
• From Daily Scrum comes Increment
• Increment undergoes Sprint Review
• Sprint Review undergoes Sprint Retrospective

Scrum Artifacts

• Product Backlog is a scrum artifact
• Sprint Backlog is a scrum artifact
• Product Increment is a scrum artifact
• Agile scrum artifacts are information that a scrum team and stakeholders use to detail the product being developed, actions to produce it, and the actions performed during the project

Scrum Artifacts - Product Backlog

• List of new features, enhancements, bug fixes, tasks, or work requirements needed to build a product
• It's made using requirements from customers, competitor analysis, market demands, and general business analysis

Scrum Artifacts - Sprint Backlog

• The sprint backlog is a set of product backlog tasks that have been promoted to be developed during the next product increment
• Sprint backlogs are created by selecting a task from the product backlog and breaking that task into smaller, actionable sprint items
• The sprint backlog is updated during the sprint planning phase of scrum
• The smaller sprint tasks are assigned to the relevant teams like design and development
• If a team does not have the capacity to deliver all the sprint tasks, the remaining sprint tasks will standby in the sprint backlog for a future sprint

Scrum Artifacts - Product Increment

• A product increment is the customer deliverables that were produced by completing product backlog tasks during a sprint
• Product increments also includes the increments of all previous sprints

Scrum Roles

• Product owner is one Scrum Role
• Scrum Master is one Scrum Role
• Team is one Scrum Role

Scrum Roles – Product Owner

• The representative of the stakeholders and customers who use the software
• Focuses on the business part
• Translates the vision of the project to the team, validate the benefits in stories to be
• Incorporated into the Product Backlog
• Decide on release date and content
• Accept or reject work results

Scrum Roles – Scrum Master

• Responsible for enacting Scrum values and practices and training to the teams in case it needs it
• Works with the Product Owner to maximize the ROI
• Enable close cooperation across all roles and functions
• Shield the team from external interferences

Scrum Roles – Team

• A group of professionals with the necessary technical knowledge who develop the project jointly carrying out the stories they commit to at the start of each sprint
• The team is Cross-functional, composed of: Programmers, testers, user experience designers etc

Scrum Phases - Initiate

• Form Scrum Team
• Create Project Vision
• Develop Epic(s)
• Create Prioritized Product Backlog
• Conduct Release Planning
• Identify Scrum Master and Stakeholder(s)

Scrum Phases - Plan and Estimate

• Create User Stories
• Approve, Estimate, and Commit User Stories
• Create Tasks
• Estimate Tasks
• Create Sprint Backlog

Scrum Phases - Implement

• Creating the various deliverables
• Conducting Daily Standup Meetings, and grooming (i.e., reviewing, fine-tuning, and regularly updating
• Conduct Daily Standup
• Groom Prioritized Product Backlog

Scrum Phases - Review and Retrospect

• Reviewing the deliverables and the work that has been done and determining ways to improve the practices and methods used to do project work
• Convene Scrum of Scrums
• Demonstrate and Validate Sprint
• Retrospect Sprint

Scrum Phases - Release

• This phase emphasizes on delivering the Accepted Deliverables to the customer and identifying, documenting, and internalizing the lessons learned during the project
• Ship Deliverables
• Retrospect Project

Sprint

• Basic unit of work for a Scrum team
• Iterative cycles - new or enhanced functionality
• A short, time-boxed period when a scrum team works to complete a set amount of work
• Typically lasts about 2-4 weeks
• The main feature that marks the difference between Scrum and other models for agile development
• Each Sprint involves: Sprint planning, Sprint preparation, Daily Activities, Sprint Demo, and Sprint Retrospective

Scrum Meetings

• Sprint planning
• Sprint review
• Daily scrum meeting

Epics

• Large user stories, typically ones which are too big to implement in a single iteration
• They need to be disaggregated into smaller user and can be broken down into user stories
• Example: As a customer, I want to be able to buy products from the online store

User Stories

• An informal, general explanation of a software feature written from the perspective of the end user
• Its purpose is to articulate how a software feature provides value to the customer
• The smallest unit of work in an agile framework
• Example: As a customer, I want to be able to browse the online store so that my time is saved

User Stories Template

• As a , I can so that

Planning Poker

• Used to estimate time and effort needed to complete each initiative on the product backlog
• Participants use physical cards
• Values stick to 0,1,2,3,5,8,13

Self Study - Extended Scrum Artifacts

• Burndown chart
• Story points

Success Stories of Scrum

• Google
• Apple
• Yahoo
• AirBnB
• HSBC
• Salesforce
• Netflix
• Lego
• Deloitte
• Sage
• Bank of Ireland
• 3M

Test your knowledge of Scrum principles. Questions cover epics, user stories, sprint cycles, and planning poker. Learn about agile project management.