Scrum - ilya-khadykin/notes-outdated GitHub Wiki

Scrum is methodology and project management framework. It includes:

Principles
Empirical Process Control
Self-Organization
Collaboration
Value based Prioritization
Time-Boxing
Iterative Development
Aspects
Organization
Business Justification
Quality
Change
Risk
Processes

"Product" in Scrum terms may refer to a real product, service or any other deliverable

Advantages of Scrum

Adaptability due to its 'sprints'
Customer Centric due to constant meetings with customers
Continuous Delivery of Value due to constant status meetings
Early Delivery of High Value because Customer will have fully working product on each iteration from the beginning. Prioritized backlog of tasks is also used for that
Contious Feedback because of daily Stand-Up meetings
Transparency: Scrumboard and Burndownchart are openly available
Sustainable Pace
Efficient Development Level
Motivation
Faster Problem Resolution
Effective Deliverables
Collective Ownership
High Velocity
Innovative Environment with retrospective meetings

Scrum Roles

There two categories of roles:

Core roles: individuals assigned Core roles are fully committed to the project (Product Owner, Scrum Master, Scrum Team)
Non-core roles: Stakeholder(s), Scrum Guidance Body, Vendors, Chief Product Owner, Chief Scrum Master

Core roles

Product Owner

responsible for achieving maximum business value
articulates customer requirements
maintains business justification for a project
represents voice of the customer

Scrum Master

ensures that Scrum Team has an appropriate environment
Scrum Master guides, facilitates, and teaches Scrum practices
clears impediments for the Team
ensures that all Scrum processes are being followed

Scrum Team

responsible for understanding Product Owner Specified requirements
creating the project deliverables

Non-core roles

Stakeholder(s)

Customers, users and sponsors Interact with Scrum Core Team Influence the project

Scrum guidance body (SGB)

Group of experts, set of documetns (govorment regulations etc) Guides the work carried out by Product Owner, Scrum Master, Scrum Team

Vendors

External individuals or internal organization

Chief Product Owner

Coordinates work between multple Scrum Masters

Chief Scrum Master

Coordinates Scrum related activities between teams

Roles in Scrum

Scrum Aspects

Organization
Business Justification
Quality
Change
Risk

Organization

See section about roles

Business Justification

Business assessments. Scrum attempts to start delivering results as early in the project as possible (value-driven delivery)

Quality

Continuous improvement The Prioritized Product Backlog is simply never complete until the closure or termination of the project Work is complete in incremental fashion through Sprints with constant testing

Change

SCRUm welcomes change by using short iterative sprints. It enables customers (Stackholders) to regularly interact with Scrum Team members and view deliverables as they are ready and even change requirements if needed

Risk

Managing risk must be done protectively Risk management should follow standardized steps to ensure risks are:

Identified
Evaluated
Proper course of action is determined upon and acted upon Two key factors of identifiing a risk:
the probability of each risk`s occurrence
the possible impact in the event of such occurrence