SCRUM FUNDAMENTALS CERTIFIED
SCRUM IS:
->Popular Agile Methodology
->Adaptive, iterative, fast, flexible and effective
->Ensures transparency in communication
->Creates collective accountability and progress
->Scrum framework supports all kinds of projects
Developed by Hirotaka Takeuchi and Ikujiro Nonaka
SBOK Guide:
-Compilation of the latest methods and best practices
-Broadly divided into three key areas:
*SCRUM PRINCIPLES:
->Empirical Process Control: based in three ideas
[*] Transparency
[*] Inspection
[*] Adaptation
->Self-organization:
[*] Focuses on Today's workers
->Collaboration: Three core dimensions related to collaborative work:
[*] Awareness
[*] Articulation
[*] Appropriation
->Value-Based priorization
[*] Maximum business value
->Time-boxing: Time-boxing elements of SCRUM includes:
[*] Sprints
[*] Daily Standup Meetings
[*] Sprint Planning Meetings
[*] Sprint Review Meetings
->Iterative Development:
[*] Manage changes better
[*] Build projects that satisfy customer needs
*SCRUM ASPECTS:
->Organization
[*] Understanding defined Roles (Core/Non-Core) of Responsabilities: it ensures the successful implementation of Scrum
->Business justification
[*] It is important for an organization to perform business assesment before the start of a project
[*] Helps the key decision makers to understand the business need for a change, new product or service
[*] the concepts:
=>Value-driven delivery
=>Uncertainty of results or outcomes
=>Impossible to guarantee Project's success and completion
->Quality:
[*] Is defined as the ability of the completed product or deliverables to meet the Acceptance Criteria and achieve the business value expected by the customer.
[*] Scrum adopts an approach of continuous improvement
->Change:
[*] Every project, regardless or its method or framework used, is exposed to change
[*] Organization should try to maximize the benefits that arise from change and minimize any negative impacts
->Risk:
[*] Is defined as an uncertain event or set of events that can affect the objectives of a project and may contribute to its success or failure
[*] Risk Management should follow standardized steps to ensure risks are:
=>Identified
=>Evaluated
=>Proper course of action is determined upon and acted upon
[*] Risk should be identified assessed, and responded to, based on two factors:
=>The probability of each risk's ocurrence
=>The possible impact in the event of such occurrence
*SCRUM PROCCESS: (How do you get the work done?) Ninetheen proccess into Five phases
->Initiate
[*] Create project Vision
=>First Process
=>Project Business is reviewed to create Project Vision Statement
=>Product Owner is identified
[*] Identify Scrum Master and Stakeholders
=>Second process
=>Scrum Master is identified
[*] Form Scrum Team
=>Third process
=>Scrum Team members are identified
=>Product Owner responsible for selecting team members, often does so in collaboration with the Scrum Master
[*] Develop Epic(s)
=>Fourth process
=>Project Vision Statements serves as the basis for developing Epics
=>User Group Meetings may be held to Develop Epics(s)
[*] Create a prioritized Product Backlog
=>Fifth process
=>Epic(s) and Unrefined User stories refined and elaborated and priorized to create a Priorized Product Backlog
=>Done Criteria is also established
[*] Conduct Release Planning
=>Sixth process
=>Scrum Core team reviews the User stories in the prioritized Product Backlog to develop a Release Planning Schedule
->Plan and Estimate
[*] Create User stories
=>First process
=>User stories and their related user story acceptance criteria are created
=>Usually written by the product owner
=>Designed to ensure that the customer's requirements are clearly depicted and understood
=>Involves Scrum team members creating the user stories
[*] Approve, Estimate and commit user stories
=>second process
=>product owner approves user stories for a sprint
=>scrum master and scrum team estimate the effort required
=>scrum team comits to develop the customer requirements in the form of approved, estimated, and commited user stories
[*] Create Task
=>Third process
=>The approved, estimated and user stories are broken down and compiled into a task list
=>Task planning meeting is held
[*] Estimate Task
=>Fourth process
=>Scrum core team in a task estimation workshop estimates effort required to accomplish each in the task list
=>Result of this process is an Effort estimated Task List
[*] Create Sprint Backlog
=>Fifth process
=>the scrum core team holds sprint planning meetings
=>sprint backlog containing all tasks to be completed in the sprint is created
->Implement
[*] Create Deliverables
=>First process
=>Scrum team works on the tasks in the sprint backlog to create sprint deliverables
=>Scrumboard is often used to track the work and activies being carried out
[*] Conduct Daily Standup
=>Second process
=>Everyday a highly focused time-boxed meeting is conducted referred to as the daily standup meeting
=>Forum for the scrum team to update each other on their progress and impediments
[*] Groom prioritized product backlog
=>Third process
=>The prioritized product backlog is continuously updated and maintained
=>Priorized product backlog review meeting may be held
=>Any changes or updated to the backlog are discussed and incorporated into the Priorized Product Backlog
->Review and Retrospect
[*] Convene scrum of scrum
=>first process
=>scrum team representatives convene for scrum of scrum meetings
[*] Demostrate and Validate Sprint
=>second process
=>Scrum team demostrates the sprint deliverables
=>purpose of this meeting is to secure approval and acceptance of the product or service by the product owner
[*] Retrospect sprint
=>Third process
=>scrum master and scrum team meet to discuss the lessons learned
=>Information is documented as lessons learned which can be applied to future sprints
->Release
[*] Ship deliverables
=>first process
=>accepted deliverables are delivered or transmitted
=>a formal working deliverables agreement documents the successful completion of the sprint
[*] Retrospect Project
=>organization stakeholders and scrum core team members assemble to retrospect the project
=>Identify, document and internalize the lessons learned
-All areas need to work together for effective application of SCRUM
SCRUM PRINCIPLES: are the core guidelines for applying the SCRUM Framework and should mandatorily be used in all SCRUM Projects
->Can be applied to any type of project in any organization
->Non-negotiable
SCRUM ASPECTS: must be addressed and managed throughout a SCRUM project
SCRUM Aspects and Processes can be modified to meet requirements of the project or organization
SCRUM PROCESSES address the specific activities and flow of a Scrum project In total, There are 19 proccess which are grouped into 5 phases
*Product: may refer to a product, service, or other deliverable
*Sprint: are short time spans in which a certain amount of work must be done
SCRUM CORE TEAM ROLES/MEMBERS: are involved in producing the project's product or service
->Product Owner:
[*] Responsible for achieving maximum business value for project
[*] Articulates customer requirements
[*] Maintains business justification for a project
[*] Represents customer's voice
->Scrum Master:
[*] Ensures that Scrum Team has an appropriate environment
[*] Guides, facilitates and teaches Scrum practices
[*] Clears impediments for the team
[*] Ensures that Scrum processes are being followed
->Scrum Team members: do work
[*] Responsible for understanding Product Owner specified requirements
[*] Creating the project deliverables
SCRUM NON-CORE ROLES: Optional and may include all team members who are interesed in the project:
->Stakeholder(s)
[*] customers, users and sponsors
[*] interface with the Scrum Core team
[*] influence the project throughout
[*] Project produces the collaborative benefits
->Scrum Guidance Body
[*] Set of Documents or group of experts
[*] Involved with defining objectives
[*] Guides the work carried out by the Product Owner/Scrum Master/Scrum Team
->Vendors
[*] External individuals or internal organization
->Chief Product Owner: in Bigger projects has multiple Scrum Team
->Chief Scrum Master: in Bigger projects has multiple Scrum Team
->Popular Agile Methodology
->Adaptive, iterative, fast, flexible and effective
->Ensures transparency in communication
->Creates collective accountability and progress
->Scrum framework supports all kinds of projects
Developed by Hirotaka Takeuchi and Ikujiro Nonaka
SBOK Guide:
-Compilation of the latest methods and best practices
-Broadly divided into three key areas:
*SCRUM PRINCIPLES:
->Empirical Process Control: based in three ideas
[*] Transparency
[*] Inspection
[*] Adaptation
->Self-organization:
[*] Focuses on Today's workers
->Collaboration: Three core dimensions related to collaborative work:
[*] Awareness
[*] Articulation
[*] Appropriation
->Value-Based priorization
[*] Maximum business value
->Time-boxing: Time-boxing elements of SCRUM includes:
[*] Sprints
[*] Daily Standup Meetings
[*] Sprint Planning Meetings
[*] Sprint Review Meetings
->Iterative Development:
[*] Manage changes better
[*] Build projects that satisfy customer needs
*SCRUM ASPECTS:
->Organization
[*] Understanding defined Roles (Core/Non-Core) of Responsabilities: it ensures the successful implementation of Scrum
->Business justification
[*] It is important for an organization to perform business assesment before the start of a project
[*] Helps the key decision makers to understand the business need for a change, new product or service
[*] the concepts:
=>Value-driven delivery
=>Uncertainty of results or outcomes
=>Impossible to guarantee Project's success and completion
->Quality:
[*] Is defined as the ability of the completed product or deliverables to meet the Acceptance Criteria and achieve the business value expected by the customer.
[*] Scrum adopts an approach of continuous improvement
->Change:
[*] Every project, regardless or its method or framework used, is exposed to change
[*] Organization should try to maximize the benefits that arise from change and minimize any negative impacts
->Risk:
[*] Is defined as an uncertain event or set of events that can affect the objectives of a project and may contribute to its success or failure
[*] Risk Management should follow standardized steps to ensure risks are:
=>Identified
=>Evaluated
=>Proper course of action is determined upon and acted upon
[*] Risk should be identified assessed, and responded to, based on two factors:
=>The probability of each risk's ocurrence
=>The possible impact in the event of such occurrence
*SCRUM PROCCESS: (How do you get the work done?) Ninetheen proccess into Five phases
->Initiate
[*] Create project Vision
=>First Process
=>Project Business is reviewed to create Project Vision Statement
=>Product Owner is identified
[*] Identify Scrum Master and Stakeholders
=>Second process
=>Scrum Master is identified
[*] Form Scrum Team
=>Third process
=>Scrum Team members are identified
=>Product Owner responsible for selecting team members, often does so in collaboration with the Scrum Master
[*] Develop Epic(s)
=>Fourth process
=>Project Vision Statements serves as the basis for developing Epics
=>User Group Meetings may be held to Develop Epics(s)
[*] Create a prioritized Product Backlog
=>Fifth process
=>Epic(s) and Unrefined User stories refined and elaborated and priorized to create a Priorized Product Backlog
=>Done Criteria is also established
[*] Conduct Release Planning
=>Sixth process
=>Scrum Core team reviews the User stories in the prioritized Product Backlog to develop a Release Planning Schedule
->Plan and Estimate
[*] Create User stories
=>First process
=>User stories and their related user story acceptance criteria are created
=>Usually written by the product owner
=>Designed to ensure that the customer's requirements are clearly depicted and understood
=>Involves Scrum team members creating the user stories
[*] Approve, Estimate and commit user stories
=>second process
=>product owner approves user stories for a sprint
=>scrum master and scrum team estimate the effort required
=>scrum team comits to develop the customer requirements in the form of approved, estimated, and commited user stories
[*] Create Task
=>Third process
=>The approved, estimated and user stories are broken down and compiled into a task list
=>Task planning meeting is held
[*] Estimate Task
=>Fourth process
=>Scrum core team in a task estimation workshop estimates effort required to accomplish each in the task list
=>Result of this process is an Effort estimated Task List
[*] Create Sprint Backlog
=>Fifth process
=>the scrum core team holds sprint planning meetings
=>sprint backlog containing all tasks to be completed in the sprint is created
->Implement
[*] Create Deliverables
=>First process
=>Scrum team works on the tasks in the sprint backlog to create sprint deliverables
=>Scrumboard is often used to track the work and activies being carried out
[*] Conduct Daily Standup
=>Second process
=>Everyday a highly focused time-boxed meeting is conducted referred to as the daily standup meeting
=>Forum for the scrum team to update each other on their progress and impediments
[*] Groom prioritized product backlog
=>Third process
=>The prioritized product backlog is continuously updated and maintained
=>Priorized product backlog review meeting may be held
=>Any changes or updated to the backlog are discussed and incorporated into the Priorized Product Backlog
->Review and Retrospect
[*] Convene scrum of scrum
=>first process
=>scrum team representatives convene for scrum of scrum meetings
[*] Demostrate and Validate Sprint
=>second process
=>Scrum team demostrates the sprint deliverables
=>purpose of this meeting is to secure approval and acceptance of the product or service by the product owner
[*] Retrospect sprint
=>Third process
=>scrum master and scrum team meet to discuss the lessons learned
=>Information is documented as lessons learned which can be applied to future sprints
->Release
[*] Ship deliverables
=>first process
=>accepted deliverables are delivered or transmitted
=>a formal working deliverables agreement documents the successful completion of the sprint
[*] Retrospect Project
=>organization stakeholders and scrum core team members assemble to retrospect the project
=>Identify, document and internalize the lessons learned
-All areas need to work together for effective application of SCRUM
SCRUM PRINCIPLES: are the core guidelines for applying the SCRUM Framework and should mandatorily be used in all SCRUM Projects
->Can be applied to any type of project in any organization
->Non-negotiable
SCRUM ASPECTS: must be addressed and managed throughout a SCRUM project
SCRUM Aspects and Processes can be modified to meet requirements of the project or organization
SCRUM PROCESSES address the specific activities and flow of a Scrum project In total, There are 19 proccess which are grouped into 5 phases
*Product: may refer to a product, service, or other deliverable
*Sprint: are short time spans in which a certain amount of work must be done
SCRUM CORE TEAM ROLES/MEMBERS: are involved in producing the project's product or service
->Product Owner:
[*] Responsible for achieving maximum business value for project
[*] Articulates customer requirements
[*] Maintains business justification for a project
[*] Represents customer's voice
->Scrum Master:
[*] Ensures that Scrum Team has an appropriate environment
[*] Guides, facilitates and teaches Scrum practices
[*] Clears impediments for the team
[*] Ensures that Scrum processes are being followed
->Scrum Team members: do work
[*] Responsible for understanding Product Owner specified requirements
[*] Creating the project deliverables
SCRUM NON-CORE ROLES: Optional and may include all team members who are interesed in the project:
->Stakeholder(s)
[*] customers, users and sponsors
[*] interface with the Scrum Core team
[*] influence the project throughout
[*] Project produces the collaborative benefits
->Scrum Guidance Body
[*] Set of Documents or group of experts
[*] Involved with defining objectives
[*] Guides the work carried out by the Product Owner/Scrum Master/Scrum Team
->Vendors
[*] External individuals or internal organization
->Chief Product Owner: in Bigger projects has multiple Scrum Team
->Chief Scrum Master: in Bigger projects has multiple Scrum Team
