Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
SCRUM - Intro
Transcript of SCRUM - Intro
SCRUM - basics
Individuals and interactions
Agile Manifesto - history of Agile
over processes and tools
over comprehensive documentation
over contract negotiation
Responding to change
over following a plan
Agile - how it works
Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.
Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.
developers vs business
Business people and developers must work
together daily throughout the project.
At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.
Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
Face 2 Face
The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.
Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.
Working software is the primary measure of progress.
Continuous attention to technical excellence
and good design enhances agility.
Simplicity--the art of maximizing the amount
of work not done--is essential.
The best architectures, requirements, and designs
emerge from self-organizing teams.
SCRUM delivers fast subProducts with greatest Business Value
SCRUM is Agile development framework
SCRUM is flexible, responsive to Change* (Scope change)
SCRUM is iterative
SCRUM is incremental
SCRUM is transparent - you see exactly:
how much work is done (on daily basis)
work to be done (on daily basis)
significant aspects of process are visible
Agile Tools/Concepts to be used in IT
JIRA (bug&issue tracking tool) - for maintaining Product + Sprint Backlogs
CI - Continuous Integration - for tests & maintaining committed code
Pair programming & Code Review - for maintaining quality of code
Central/Distributed source code management tools (+quality)
*lets change requirements here!
SCRUM - rugby
TEAM - Most important part of SCRUM
Self - organizing
Cross - functional
Work is done thru collaboration of TEAM
Overall competencies vs.
- Developers, Architects, Analysts Administrators, Business people, Support, Maintenance, Sellers...etc.
many different perspectives!
Joint TEAM responsibility vs.
Somebody with deep understanding of Client needs
Can be from Client organization
Is involved daily in TEAM work
Can help create User Stories / PBI
Product Owner - "Business guy"
Prioritizes work (Product Backlog Items)
Accepts TEAM work
Has its own velocity - speed of work
Somebody responsible for Business, scope, values of product
SCRUM Master - team protector, facilitator, coach / mentor
Responsible for providing all necessary tools for TEAM
Protects TEAM from outside interference
Helps TEAM to resolves obstacles
Facilitates TEAM meetings
Usually 6+-3 people dedicated to one product
SCRUM - ROLES
SCRUM - abbreviated "scrummage"
SCRUM - Artifacts
Sprint - Iteration
In SCRUM between 1-4 weeks
Main objective of Sprint is delivering increase in value
(by potentially shippable increment)
Shippable = WORKING product with Business Value
Shippable = WORKING =
Shippable = DDD (Done-Done-Done)
USER STORY / Product Backlog Item (PBI)
- a platrofm for communication
i would like to
in order to
PBI can be
from simple commonly understandable description / picture / diagram
to sequence graph, technical specyfication, detailed information, main scenario flow,
alternative scenarios (what if something goes wrong) , etc.....
(anything that Team accepts & finds useful)
Daily SCRUM - stand-up meeting
Daily SCRUM is 15 minutes long(!) meeting (all standing) on which team plans daily work:
What I did yesterday?
What I'm going to do today?
Do I have any impediments / blockers?***
* Those questions are to inform rest of TEAM about your progress, so that team can easyly synchronize. They
reports for PM.
*** If you can help somebody with his/hers problem do it AFTER the daily SCRUM
Try to upgrade your Burndown chart at meeting
Product and Sprint Backlog
Meeting with Client/Product Owner in order to plan next sprint.*
On this meeting:
Add acceptance criteria / Definition of Ready for every User Story!
Product Owner & Team will decide which PBI should be included in next sprint (those items will become Sprint Backlog Items)
how much time/resources will each Task consume.
Product Owner will describe increments & values behind them
Sprint retrospective - continues improvement
Sprint retrospective is a meeting after every Sprint.
Its objective is to constantly improve quality of work, development process, tools & also Team happines.
Discuss what was good and is worth cultivating
Discuss what slowed TEAM work
Discuss on how to repair it / improve it.
Agree on what actions are to be done, and who will be responsible for those actions.
Write them down, start next retrospective from discussion about them!
Don't be late for this meeting.
Last person to attend starts meeting.
After your done answering questions, choose next person to speak.
(Use Planning Poker for this)
1) (constant) Product Owner prioritises Product Backlog
b) Product Backlog is divided into Sprints
2) Sprint Planning meeting
a) Tasks are evaluated by resources(time), risks
c) TEAM and Product Owner agree on Sprint Backlog
3) TEAM starts Sprint
a) TEAM works daily
b) TEAM meets at SCRUM stand-up's (dayly)
4) After Sprint, TEAM presents DEMO
5) TEAM meets on Sprint Retrospactive
7) TEAM repeats Sprint cycle until all Product Backlog Tasks are done
* Divide Sprints only into: Current Sprint, Next Sprint, other future Sprints
After every Sprint TEAM should produce WORKING increment of Product, which can be presented to Client.
SCRUM gives Client chance for a fast feedback
Objective of this meeting is to get feedback from Client and other stakeholders about each increment.
If your preparing a DEMO be sure to invite all stakeholders, and people that might be interested in TEAMs work.
Be open for new concepts and feedback.
It will help you improve your Product!
Burndown chart shows daily progress of TEAMs work.
Its important both for TEAM and for management.
On X-axis there is time of sprint(days), on Y-axis User Story Points that are BURNED - done (DDD)
Not committed = doesn't exist!
Q & A
Thanks for attention!
If you hated/disagreed/had other conceptions/(liked?) anything in presentation I would LOVE to hear about it
Thinks a lot for great stormtroopers pics!
TDD - Test Driven Development
(Write test first, write code for which test will pass, refactor.... write another test->code->test passes->refactor...and so on.)
Work in close collaboration
Tested (ex.unit tests) + Installed +
Accepted by Client
(did I finish to what I commited yesterday?
(what is my plan & commitment for today**)
** YES!- you can choose how you want to accompish goals
Product Backlog - List of all value increments ("To Do") for whole Product.
Sprint Backlog - List of all value increments ("To Do") for THIS Sprint.
Try to brake all big items into smaller ones (4-6h is optimal)
You can evaluate using:
* Fibonacci string (1/2);1;2;3;4;5;13;20;20;40;100
* Powers of 2: 1/2;1;2;4;8;16
* or abstract: XS;S;M;L;XL - T-shirt sizes
Just remember about TEAM velocity.
(to accomplish Sprint Goals)
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
That is, while there is value in the items on
the right, we value the items on the left more.
Helps TEAM to improve (Coach/Mentor)
Somebody with vision of product
(by answering 3 questions*)
Tips & Tricks:
Product Owner & Team defines Sprint goal
(in order of priority)
Keep those meetings fun & engaging
Why do we do "Agile"
Why do we do "Agile"
Why do we do "Agile"
Why do we do "Agile"
Reaction to change
Creating stuff that has value for Customer
80% of features are not used
1/3 successful projects
+ EVO, Principles of Software Engineering Management
"Agile" -> Buzzword only ?
6) (constant) TEAM works on Backlog refinement
What "Agile" / SCRUM can do for me
solve your problems,
it will make them
SCRUM - basics
Simple to understand
Difficult to master
"Scrum (n): A framework within which people can address complex adaptive problems, while
productively and creatively delivering products of the highest possible value."