Please enable JavaScript.
Coggle requires JavaScript to display documents.
Core Concepts in Scrum (Product Backlog (PBI Estimation Concepts (Estimate…
Core Concepts in Scrum
Core Concepts
Planning porker
Estimation Scale
► To perform planning porker the team must decide which scale or sequence of number will use for assigning estimates
► Most used scale is Fibonacci sequence
How to Play
► Full team participates when planning porker performed
► Product owner presents, describes and clarifies the PBI
► Scrum Mater coaches the team to help apply planning porker
► Each dev.team member provided with set of planing po. cards
Intro
► This is a technique for sizing PBI and for estimating effort
► Described by Hames Grenning and popularized by Mike Cohn
► Few Important concept follows:
Consensuses Based
Expert opinion
Relative sizing
Accurate grouping/binning
Leverage estimating history
► Expert Slated to work on PBI
Benifits
► Foster (feed) the worthiness of estimating PBI
► Help team to decide who will work and allows them to reach consensus
Velocity
What is Velocity
► Amount of work completed each sprint
► measured by adding the sized of the PBI s that are completed by the end of the sprints
► Velocity measure the output not outcome
► Purposes > Scrum Planning and release planning
► Can evaluate and improve the use of scrum to deliver customer value
-
-
Scrum Phases
Pre-game
Focus on understanding project in terms of business and technical ► requirements
Simply, Planning-define system. Product backlog and architecture -high ► level design of system
Key Activities
Conduct workshop to clarify requirements►
Document, review and refine requirements, - Generate PBL►
Estimate the effort required for the phase (HL Ball park estimate)►
Required planning activities are performed for the entire phase ►
Key Deliverables
SRS updates with use case - PBL►
High level architecture & Design document►
Deployment Model►
Project schedule ►
Quality Assurance Test Strategy/ Plan►
Sprint
Introduction
Scrum organizes work it iterations or cycles up►
to calendar month call sprint
Sprints are skeleton of scrum framework►
Sprint output is potential shhippable product ►
Scrum team decide the length of a sprint►
Sprints are time boxed►
Time Boxed
Time box is a time-management technique►
define maximum time duration►
Benefits
Establishes a WIP Limit►
Forces Prioritization ►
Demonstrates Progress ►
Avoids Unnecessary Perfectionism►
Motivates Closure►
Improves Predictability►
Short Duration
Ease of Planning ►
Fast Feedback►
Improved ROI►
Bounded Error►
Rejuvenated Excitement►
Frequent Checkpoints►
-
-
-
-
-
-
Post - game
Requirements Satisfied- no new item or issues►
Conduct a Sprint demo- Sprint review meeting►
Conduct Retrospective ( What went right and wrong?)►
Deliverable of post - game
Working and tested software (as per Sprint backlog)►
Sprint Release notes►
Test reports ►
-
Meeting Types
Release planning meeting - aim to plan a particular release►
Sprint planning meeting - aim to plan a particular sprint►
Stand up planning meeting►
Sprint review meeting►
Sprint retrospective meeting►
Product Backlog
Who does the grooming
► Collaborative effort
► Led by product owner and significant participant from internal and external stakeholders
► Ultimate grooming decision maker is the Product owner
Release flow management
► PBL must be groom in way that support ongoing release planning
PBL have 3 ares:
► Must have - items that we simply must have in upcoming release
► Nice to have - utens we are targeting for the next release and would like to include
► Won't have - items that we're declaring won't be included in the current release
Grooming
► Set of 3 principal activities :
Creating and refining PBI
Estimating PBI
Prioritizing PBI
► Reshapes the PBL
PBI Estimation Concepts
Estimate as a Team
► People who will do the work will provide estimate
► Owner and Scrum Master don't provide estimate
► Owner describe the PBI roles to clarify the team's questions
► Scrum master will help coach and facilitate the estimation activity
-
Focus on accuracy, not precision
-
-
Good PBL Characteristics
Roman Pichler 2010 and Mike Cohn DEEP
► Detailed appropriately
► Emergent
► Estimated
► Prioritized
DEEP helps to decide if a PBL has been structured in good way
-
-
Introduction
► This is a prioritized list of desired product functionality
► PBL is the heart of the Scrum framework
Scrum Plannig
Portfolio Planning►
Product Planning (Envisioning)►
Release Planning (Milestone/Longer Term Planning)►
About Scrum
Scrum is not a standardized process►
It's and Agile Framework►
Product, on time, or budget, high quality and delight customers►
Can make own versions of scrum (Model can be customize)►
Favor to time box development►
-