This document provides an overview of the Scrum framework, highlighting its role within Agile methodologies and its effectiveness in project management. It describes the components of Scrum, including roles (Product Owner, Scrum Master, Development Team), events, and artifacts, while emphasizing the benefits of its implementation for delivering quality products efficiently. The document also outlines the importance of collaboration, adaptability, and a well-defined 'Definition of Done' in ensuring the success of Scrum teams.

1. WHAT IS SCRUM
Basic Introduction of SCRUM Framework
Presentation by Gul Zaman Ilyas

2. About Presenter
Email: zamanilyas@hotmail.com | Ph. #: (+92) 323 141 6914
Professional Summary:
A Certified Scrum Master & MCSD possessing almost 18+ Total Years of
Professional IT Work Experience & almost 10 Years of Project Management
related experience.
Overall possessing experience in Entrepreneur-ship, IT Operations, IT
Infrastructure, Software Architecture & Development, IT Consultancy, Cloud
Platforms, Virtualization, Networks and much more.
Tools Stack:
Communication, Training, Networks, IT Operations, IT Infrastructure, Microsoft
Technologies, Linux, Cloud (Public, Private & Hybrid), Virtualization, AWS, Azure

3. What is Agile?
Agile software development refers to a group of software development methodologies
based on iterative development, where requirements and solutions evolve through
collaboration between self-organizing cross-functional teams.
Agile methods or Agile processes generally promote a disciplined project management
process that encourages frequent inspection and adaptation, a leadership philosophy
that encourages teamwork, self-organization and accountability, a set of engineering
best practices intended to allow for rapid delivery of high-quality software, and a
business approach that aligns development with customer needs and company goals.

4. What is SCRUM?
Scrum is a subset of Agile. It is a lightweight process framework for agile development,
and the most widely-used one.
“Scrum is a simple yet incredibly powerful set of principles and practices that
helps teams deliver products in short cycles, enabling fast feedback, continual
improvement, and rapid adaptation to change”.
As defined by scrumalliance.org
“A framework within which
people can address complex
adaptive problems, while
productively and creatively
delivering products of the
highest possible value”.
As defined by scrum.org

5. Benefits of Scrum & What Scrum is and is not
Benefits of SCRUM:
• Increase the quality of the deliverables
• Cope better with change (and expect the changes)
• Provide better estimates while spending less time creating them
• Be more in control of the project schedule and state
• …
• …
Scrum is:
• Lightweight
• Simple to understand
• Difficult to master
Scrum is NOT:
• Software / Tool
• Software Dev. Framework

6. Manifesto for Agile Software Development
We are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value:
– Individuals and interactions over processes and tools
– Working software over comprehensive documentation
– Customer collaboration over contract negotiation
– Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.

7. SCRUM Values
Using these as a guidepost, additional Scrum values have been created, and continue to be developed
and modified (in true Agile fashion). These five values are the foundation for a Scrum team's processes
and interactions:

8. Why should you use SCRUM?
Scrum has the power to transform project management across every industry, every
business, and even across life in general. By using Scrum, you’ll become more Agile,
discovering how to react more quickly and respond more accurately to the inevitable change
that comes your way. And by staying focused, collaborating, and communicating, you can
accomplish what truly needs to be done — successfully.
Most important, Scrum is not unproven hype. It’s a solid and successful Agile framework
that’s been applied to a variety of projects and teams. Universities use Scrum to deliver
valued projects to clients. Militaries have relied on Scrum to prepare ships for deployment.
So whether you’re working on the next smartphone app, managing logistics for a store, or
planning a charity event, you should take a closer look at using Scrum. And Scrum Alliance
can give you the proven framework, best implementation practices, and supportive guidance
you need to achieve success.

10. SCRUM Events
Prescribed events are used in Scrum to create regularity and to minimize the need for
meetings not defined in Scrum. All events are time-boxed. Once a Sprint begins, its
duration is fixed and cannot be shortened or lengthened. The remaining events may
end whenever the purpose of the event is achieved, ensuring an appropriate amount of
time is spent without allowing waste in the process.
The Scrum Events are:
– Sprint
– Sprint Planning
– Daily Scrum
– Sprint Review
– Sprint Retrospective

11. SCRUM Artifacts
Scrum’s artifacts represent work or value to provide transparency and opportunities for
inspection and adaptation. Artifacts defined by Scrum are specifically designed to
maximize transparency of key information so that everybody has the same
understanding of the artifact.
The Scrum Artifacts are:
– Product Backlog
– Sprint Backlog
– Increment

12. Definition of DONE (DoD)
■ Definition of done is crucial to a highly functioning Scrum team. The following are
characteristics that you should look for in your team’s definition of done. Verifying that your
team’s DoD meets these criteria will ensure that you are delivering features that are truly
done, not only in terms of functionality but in terms of quality as well.
■ Definition of Done is a simple list of activities (writing code, coding comments, unit testing,
integration testing, release notes, design documents, etc.) that add
verifiable/demonstrable value to the product. Focusing on value-added steps allows the
team to focus on what must be completed in order to build software while eliminating
wasteful activities that only complicate software development efforts.
■ Reporting in its simplest form is the ability to say, “This feature is done.” After all, a feature
or Product Backlog Item is either done or it is not-done. DoD is a simple artifact that adds
clarity to the “Feature’s done” statement. Using DoD as a reference for this conversation a
team member can effectively update other team members and the product owner.

13. Scrum Teams & Roles
Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose
how best to accomplish their work, rather than being directed by others outside the
team. Cross-functional teams have all competencies needed to accomplish the work
without depending on others not part of the team. The team model in Scrum is
designed to optimize flexibility, creativity, and productivity.
SCRUM Team consists of:
– Product Owner
– Scrum Master
– Scrum Team

14. What is a Product Owner?
A Scrum Product Owner is responsible for maximizing the value of the product resulting from the work
of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and
individuals.
“The Product Owner is the sole person responsible for managing the Product Backlog”.
Product Backlog management includes:
– Clearly expressing Product Backlog items.
– Ordering the items in the Product Backlog to best achieve goals and missions.
– Optimizing the value of the work the Development Team performs.
– Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows
what the Scrum Team will work on next.
– Ensuring the Development Team understands items in the Product Backlog to the level
needed.
The Product Owner may do the above work, or have the Development Team do it. However, the Product
Owner remains accountable.
The Product Owner is one person, not a committee. The Product Owner may represent the desires of a
committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must
address the Product Owner.
For the Product Owner to succeed, the entire organization must respect his or her decisions. The
Product Owner’s decisions are visible in the content and ordering of the Product Backlog. No one can
force the Development Team to work from a different set of requirements.

15. What is a ScrumMaster?
The Scrum Master is responsible for promoting and supporting Scrum. Scrum Masters do this by helping everyone
understand Scrum theory, practices, rules, and values.
The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those outside the Scrum Team
understand which of their interactions with the Scrum Team are helpful and which aren’t. The Scrum Master helps
everyone change these interactions to maximize the value created by the Scrum Team.
Roles a Scrum Master Plays:
– Service to the Product Owner
■ Ensuring that goals, scope, and product domain are understood by everyone on the Scrum
Team as well as possible.
■ Finding techniques for effective Product Backlog management.
■ Helping the Scrum Team understand the need for clear and concise Product Backlog items.
■ Understanding product planning in an empirical environment.
■ Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value.
■ Understanding and practicing agility.
■ Facilitating Scrum events as requested or needed.
– Service to the Development Team
■ Coaching the Development Team in self-organization and cross-functionality.
■ Helping the Development Team to create high-value products.
■ Removing impediments to the Development Team’s progress.
■ Facilitating Scrum events as requested or needed.
■ Coaching the Development Team in organizational environments in which Scrum is not yet
fully adopted and understood.
– Service to the Organization
■ Leading and coaching the organization in its Scrum adoption;
■ Planning Scrum implementations within the organization;
■ Helping employees and stakeholders understand and enact Scrum and empirical product
development;
■ Causing change that increases the productivity of the Scrum Team; and,
■ Working with other Scrum Masters to increase the effectiveness of the application of Scrum
in the organization.

16. What is a Scrum Team?
A Scrum Development Team consists of professionals who do the work of
delivering a potentially releasable Increment of “Done” product at the end
of each Sprint. A "Done" increment is required at the Sprint Review. Only
members of the Development Team create the Increment.
Development Teams are structured and empowered by the organization to
organize and manage their own work. The resulting synergy optimizes the
Development Team’s overall efficiency and effectiveness.
Scrum / Development Teams have the following characteristics:
– They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn
Product Backlog into Increments of potentially releasable functionality;
– Development Teams are cross-functional, with all the skills as a team necessary to create a product
Increment;
– Scrum recognizes no titles for Development Team members, regardless of the work being performed by the
person;
– Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed
like testing, architecture, operations or business analysis; and,
– Individual Development Team members may have specialized skills and areas of focus, but accountability
belongs to the Development Team as a whole.
Development Team Size
Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within
a Sprint. Fewer than three Development Team members decrease interaction and results in smaller productivity gains.
Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be
unable to deliver a potentially releasable Increment. Having more than nine members requires too much coordination.
Large Development Teams generate too much complexity for an empirical process to be useful. The Product Owner and
Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog.

17. Some useful links:
■ Scrum Guide
■ Download Scrum Guide Audio Book Version
■ Scrum Foundation E-Learning Series