Scrum - Agile Methodology
-
Upload
niel-deckx -
Category
Leadership & Management
-
view
4.157 -
download
3
Transcript of Scrum - Agile Methodology
NIEL DECKX
Freelance iOS Developer
Certified ScrumMasterCertified Product Owner
www.nieldeckx.be
HAVE A DECENT PROCESS WHEN CREATING A PRODUCT
What’s the main goal?
HAVE A DECENT PROCESS WHEN CREATING A PRODUCT
What’s the main goal?
Why?
CREATE THE BEST PRODUCT
SUMMARY
- Waterfall- The Agile Manifesto- SCRUM Principles - SCRUM Framework - Roles & Team - Artefacts - Activities
WATERFALL
OVERVIEW
IdeaAnalysis
Design
Development
Testing
FinalProduct
OVERVIEWDesign
…Testing
FinalProduct
FeedbackCollaboration
Business Value
PUSH SYSTEM
Input Capacity Delivery
overwhelm capacitycreating waste and delay
QUALITY
Scope
BudgetTime
Quality
If budget, time and scope are fixed,quality will vary.
THE AGILE MANIFESTO
Individuals and Interactions
over processes and tools
Working software
over comprehensive documentation
Customer collaboration
over contract negotiation
Responding to change
over following a plan
BE AGILE- Team and collaboration- Incremental - Iterative- Value driven - Frequent delivery - Product quality- Inspect and adapt- Self-organisation
SCRUM PRINCIPLES
BE ADAPTIVEDesign, Testing, Development
ProductIncrementBusiness Value
FinalProduct
Repeat!Feedback,Collaboration Repeat!
PDCA
ProductIncrement
Plan Do Check Act
VALUE DRIVEN
CONSTRAINTS:
ESTIMATES: Scope
Time Budget
Quality
PRIORITIZATION
MoSCoW
Must HaveShould HaveCould HaveWon’t Have Out of scope
Buffer
In scope
BENEFITSfor business
- Quicker ROI - Lower Total Cost- Respond to Change- Reduce Risk- Faster Time to Market- Stakeholder Relations
BENEFITSfor development
- Teaming- A Sense of Done - Quality Work- Rhythm - Visible Progress- Feedback and Iteration
SCRUM FRAMEWORK
Roles, Artefacts and Activities
ROLES & TEAM
- Product Owner - Scrum Master - Development Team
SCRUMTEAM
MEMBER
a good is focussedhas respect for others has courageis committedis open
5 - 9 members
TEAM
Self-organising
Cross functional
SCRUM TEAM
- Represents customers and stakeholders - Maximise product value- Track time and budget- Manage product backlog
PRODUCT OWNER
- Bring up impediments- Resolve impediments - Support the Scrum team in implementing Scrum
SCRUM MASTER
- Cross functional - Accomplishing the Sprint goal- Delivers a product increment
DEVELOPMENT TEAM
Scrum MasterProduct Owner
Development Team
SelectFeatures
ProductIncrement
Discuss
Work onFeatures
SupportsScrum Team
ARTIFACTS
- Product Backlog- Sprint Backlog- Product Increment- Definition of Done - Progress Monitors
PRODUCT BACKLOG
User Story
User Story
User Story
Epic Story
Epic Story
STORY FORMAT
AS A …
I WANT TO …
SO THAT …
Who?
What?
Why?
User role
Action
Business goal
STORY
Acts as- Requirement- Planning item- Reminder - Conversation trigger- Shared understanding
EPIC STORY
- Must be split in user stories
- Stories which do not satisfy INVEST criteria
INVEST CRITERIA
IndependentNegotiableValuableEstimableSmallTestable
Can deliver value by itself Details can be worked out by conversation Value to the user is clear Team understands it well to estimateFits in a sprintClear test criteria
PRODUCT BACKLOGBug
User Story
User Story
Epic Story
Epic Story
Refactoring
- Prioritised set of estimated items- Constantly in change as the situation changes- Contains stories, bugs, refactorings, …- Detailed appropriately - Source of work for the Development team
PRODUCT BACKLOG
SPRINT BACKLOG
User Story
User Story
User Story
Epic Story
Epic Story
User Story
User Story
PRODUCT BACKLOG
TASKEach user story can be separated into (technical) tasks.
As a plan to accomplish the work.
AS A …
I WANT TO …
SO THAT …
Set up the database
Create API call
…
User Story
User Story
Task
Task
Task
Task
Task
INITIALSPRINT BACKLOG
TO DO
User Story
User Story
Task
TaskTask
DOING BLOCKED DONE
SPRINT BACKLOG
Task Task
Dynamic representation of the work during a sprint.
DEFINITION OF READY
Sprint
Minimise Waste
When is a product backlog item sprintable?
DEFINITION OF DONE
Sprint ProductIncrement
Minimize Risk
When is a task really done?
PRODUCT INCREMENT
= Potentially shippable increment of the product.
It meets the Definition of Done!
PROGRESS MONITORS
First we have to understand what
a sprint and a sprint planning is.
PRODUCT BACKLOG
SPRINT BACKLOG
SPRINT PLANNING
DAILY SCRUM
SPRINT
PRODUCT INCREMENT
DEFINITION OF DONE
SPRINT REVIEW
SPRINT RETROSPECTIVE
PROGRESS MONITORS
ACTIVITIES
- Sprint- Sprint planning- Daily scrum - Sprint review - Sprint retrospective- Product backlog refinement
Be adaptive! Iterate!
Sprint
Fixed timebox in which the Scrum team delivers a product increment
according to the Definition of Done.
between 1 and 4 weeks
SPRINT
Project progresses in sprints
Sprint commitment by Development team
No new requirements during the spint
Scrum team delivers a product increment
How do we plan?
Sprint Planning
Timeboxed meeting for the Scrum Team,to pull work into the Sprint Backlog
max 2 hours per week of sprint
SPRINT PLANNING
SPRINT BACKLOG
PRODUCT BACKLOG
Which items can the team commit to?What is the sprint goal?
Which tasks can we identify for each story?
ITEM ESTIMATES
The development team plays planning poker
RELATIVE ESTIMATES
- Story points are more then just time - Compare to reference item- Faster, more accurate planning- Independent of developer skills
Fibonacci: 1 2 3 5 8 13 ..
PLANNING POKER
1 - Product Owner explains item2 - Developer compares with a reference item 3 - All cards are shown together 4 - Highest and lowest explained5 - Team gets to a consensus, possible other round
Track progress during the sprint?
Daily Scrum
Timeboxed meeting for the Development team to make sure the sprint goal is reached.
max 15 minutes
What did you do yesterday? What will you be doing today? Are there any blocking issues?
Everyone. Short. Turn by turn.
And take necessary steps after the Daily Scrum
Sprint improvements?
Sprint Retrospective
Timeboxed meeting for the Scrum team to discuss the sprint and improve further.
max 1 hour per week of sprint
What did we do good in last sprint? What did we do less in the last sprint?
Are there any questions or uncertainties? Are there any open items from last retrospective?
Everyone. Write down.
Group the items and discuss. Plan and take action.
Delivered product?
Sprint Review
Timeboxed meeting for the Scrum team and stakeholders to review the product increment
max 1 hour per week of sprint
Updated backlog!
Product Backlog Refinement
Scrum team keeps the product backlog up to date,to have a shared understanding of what needs to be done
ongoing activity
Add stories.
Remove stories.
Split stories.
Add detail to stories.
Prioritise stories.
Estimate stories.
Product Backlog Refinement
PRODUCT BACKLOG
SPRINT BACKLOG
SPRINT PLANNING
DAILY SCRUM
SPRINT
PRODUCT INCREMENT
DEFINITION OF DONE
SPRINT REVIEW
SPRINT RETROSPECTIVE
PROGRESS MONITORS
PROGRESS MONITORS
Now we understand what
a sprint and a sprint planning is.
A story point is more then just time.
How do we know how many story points we can handle as a development team?
MEASURE!
STORY POINTS DONE
SPRINTVELOCITY =
VELOCITY
used by developers for better sprint estimations and to stabilise progress
VELOCITY
used by the product owner to make forecasts that help
to prioritise items
VELOCITY GRAPH
| | | | | | | |
Long Term ?
Remainingstory points
Sprints | | | | | | | |
Stability ?
Predictability ?
VELOCITY GRAPH
| | | | | | | |
Remainingstory points
Sprints | | | | | | | |
Deadline
VELOCITY GRAPH
| | | | | | | |
Remainingstory points
Sprints | | | | | | | |
Deadline
Will deliverMight deliver
Not delivered
PRODUCT BACKLOG
SPRINT BACKLOG
SPRINT PLANNING
DAILY SCRUM
SPRINT
PRODUCT INCREMENT
DEFINITION OF DONE
SPRINT REVIEW
SPRINT RETROSPECTIVE
PROGRESS MONITORS