SCRUM METHODOLOGY

AGILE’S DERIVATION
INGREDIENTS
• Recall
• Introduction
• Roles of Scrum
• Framework
• Daily Scrum
• Sprint Review
• Conclusion
• References
RECALL
• In software engineering, a software development process is the process of dividing software
development work into distinct phases to improve design, product management, and project
management. It is also known as a Software development life cycle.
• The methodology may include the pre-definition of specific deliverables and artifacts that are created
and completed by a project team to develop or maintain an application.
• Methodologies include waterfall, prototyping, iterative and incremental development, spiral
development, rapid application development, and Agile.
• What is AGILE?
• Agile model believes that every project needs to be handled differently and the existing methods need
to be tailored to best suit the project requirements. In Agile, the tasks are divided to time boxes (small
time frames) to deliver specific features for a release.
• The term Agile was popularized, in this context, by the Manifesto for Agile Software Development. The
values and principles espoused in this manifesto were derived from and underpin a broad range
of software development frameworks, including Scrum and Kanban.
AGILE PRINCIPLES
• Customer satisfaction by early and continuous delivery of valuable software
• Welcome changing requirements, even in late development
• Working software is delivered frequently (weeks rather than months)
• Close, daily cooperation between business people and developers
• Projects are built around motivated individuals, who should be trusted
• Face-to-face conversation is the best form of communication (co-location)
• Working software is the primary measure of progress
• Sustainable development, able to maintain a constant pace
• Continuous attention to technical excellence and good design
• Simplicity—the art of maximizing the amount of work not done—is essential
• Best architectures, requirements, and designs emerge from self-organizing teams
• Regularly, the team reflects on how to become more effective, and adjusts accordingly
INTRODUCTION

• Scrum is an incremental and iterative agile software development framework for managing product
development. It was first defined as "a flexible, holistic product development strategy where a
development team works as a unit to reach a common goal" in 1986 by Hirotaka Takeuchi and Ikujiro
Nonaka in the New Product Development Game.
• According to Ken Schwaber, Scrum is frame for developing complex products and systems It is
grounded in empirical process and control theory. Scrum employees an iterative and incremental
approach to optimize predictability and control risk.
• Scrum encourages a team to work in a focused way for limited period of time on a definite amount of
work. It also allows the team to build and improve ability to estimate how much effort it will take to
develop a new feature and the lesson learnt are documented in a system.
Continued……
• There are a few terms defined in the Scrum to understand its meaning clearly, they are:
• Agile: It is a set of software development practices designed to help developers work together and adapt to changes
quickly and easily.
• Story: A clear and consistent way of dividing, phrasing, and discussing work the team may need to do on the product.
• Customer: Whoever has engaged the team to create a product.
• Developer: A person responsible for creating and maintaining the product.
• Product Backlog: A constantly evolving list of potential features or changes for a project.
• Sprint: A fixed number of days during which the team can work together to produce an agreed upon set of changes to the
product.
 SCRUM TEAM-TWO MAJOR ROLES
Product Owner Scrum Master
• The Scrum Master is the most visible spokesperson for the
• The Product Owner is the business representative of the team. Scrum Masters value transparency. They'll devise charts
team. They're not part-time team members. They show up and boards to share the team's progress with anyone who's
every day, because they're contributing to the final product curious or interested in knowing how they're doing.
every day.
• Helping the product owner maintain the product backlog in a
• Tasks of PO: way that ensures the needed work is well understood so the
• demonstrates the solution to key stakeholders who were not team can continually make forward progress
present at a sprint review • Helping the team to determine the definition of done for the
• defines and announces releases product, with input from key stakeholders

• communicates team status
• organizes milestone reviews
• educates stakeholders in the development process
• negotiates priorities, scope, funding, and schedule
• ensures that the product backlog is visible, transparent, and
clear.
• Coaching the team, within the Scrum principles, in order to
deliver high-quality features for its product
• Promoting self-organization within the team
• Helping the scrum team to avoid or remove impediments to
its progress, whether internal or external to the team
• Facilitating team events to ensure regular progress
• Educating key stakeholders in the product on Scrum principles
• Coaching the development team in self-organization and
cross-functionality
SCRUM FRAMEWORK
• Sprint:
sprint (or iteration) is the basic unit of development in Scrum. The sprint is a timeboxed effort; that is, it is restricted to a specific duration.
The duration is fixed in advance for each sprint and is normally between one week and one month, with two weeks being the most
common.
• In Sprint planning, the work to be performed in the Sprint is planned collaboratively by the Scrum Team.
• The Daily Scrum Meeting is a 15-minute time-boxed event for the Scrum Team to synchronize the activities and create a plan for that
day.
• A Sprint Review is held at the end of the Sprint to inspect the Increment and make changes to the Product Backlog, if needed.
• The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. In this meeting, the Scrum Team is to
inspect itself and create a plan for improvements to be enacted during the subsequent Sprint.
• Sprint Planning focuses on the following two questions -
What needs to be and can be delivered in the Sprint Increment?
How will the work needed for the execution of Sprint be achieved?
• The inputs to this meeting are -
The Product Backlog
The latest product Increment
Projected capacity of the Team during the Sprint
Past performance of the Team
DAILY SCRUM
• The Scrum Master will establish your daily scrum. This is also commonly referred to as the daily standup meeting, or standup, for
short. In order for scrum to work, it relies on the three C’s:
Collaboration
Communication
Cadence
• Each day during a sprint, the team holds a daily scrum (or stand-up) with specific guidelines:
• All members of the development team come prepared. The daily scrum:
• starts precisely on time even if some development team members are missing
• should happen at the same time and place every day
• is limited to fifteen minutes
• Anyone is welcome, though only development team members should contribute.
• During the daily scrum, each team member typically answers three questions:
• What did I complete yesterday that contributed to the team meeting our sprint goal?
• What do I plan to complete today to contribute to the team meeting our sprint goal?
• Do I see any impediment that could prevent me or the team from meeting our sprint goal?
SPRINT REVIEW

• The sprint review meeting is an informal round-up of all completed stories and a demonstration of the
new product increment. By ‘informal’ I mean no slides should be used to guide the direction of the
conversations.
• Included in this meeting are the product owner, the development team, the Scrum mater and often
stakeholders from the client who want to see output of the sprint.
• If any stories were not completed, these are discussed ad the product owner updates the product
backlog for the next sprint.
CONCLUSION

Software development using agile methodologies is becoming a bigger reality in the daily life of software
development companies. Agility brings quality to the software development and management process. In order to
add value to the final software, one must have a well structures team that follows the methodology and uses correct
strategies. The hybridization of scrum with other software development methodologies is common as scrum does
not cover the whole product development lifecycle; therefore, organizations find the need to add in additional
processes to create a more comprehensive implementation. Various authors and communities of people who use
scrum have also suggested more detailed techniques for how to apply or adapt scrum to particular problems or
organizations. Also, projects where the developers are geographically separated are less suitable for the scrum
approach. Because scrum sprints are short, less time is available for iterative testing, making it difficult to maintain
quality control for such projects when using a scrum approach.
REFERENCES

• Study Tonight
• Wikipedia
• Tutorials point
• YouTube
THANK YOU
C.SHARATH
C.S.E 4
2210315405