Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start 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.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Scrum

an agile development framework

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Scrum

SCRUM
by Marcela Craciunescu
an agile development framework
Scrum is a framework for developing products that customers really value
1. Scrum is an empirically adaptive framework for complex product development
2. Cross-functional and Self-organizing teams
3. Deliver something at the end of each short iteration
4. Scrum is for Product Management
Four messages about Scrum in this presentation:
SCRUM is
daily stand-up
time-boxed iterations
backlogs
TRANSPARENCY
INSPECT
ADAPT
Team members
Scrum Master
Product Owner
Cross functional
Self-Organizing
Teams
Scrum does not
mean :

miniature

waterfalls
Scrum does not mean ‘Ad-hoc’
Scrum is disciplined and structured,
but not a sequential life cycle
Scrum is an Agile
approach that applies
many Lean principles
Deliver Customer Value Fast
Reduce Cost of Change
Continuous Improvement
Respect for People
Managers, Mentors and Lean Experts
Decisions for Long Term
End - to -End Process
Flow
Delight Customers
LEAN
SCRUM
AGILE
Continuous Improvement
Self - Organizing Teams
Cross - Functional Teams
Short Time-boxed Iterations
Incremental business value
Inspect & adapt (Plans, Product and Process
Long term sustainability
Transparency
Servant - Leaders
Quality
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Scrum is the most popular agile approach

 Over 50% of agile projects in industry use Scrum

Scrum focuses on “the art of the possible”

 Do the best you can in the current iteration
 Use what you learn to replan the rest of the project
 Continually try to improve

Scrum is not limited to small projects

 Useable for larger projects, geographical distribution, and legacy systems
Scrum is compose from:
Roles
Artifacts
Meetings
Process
Scrum components ...
PRODUCT OWNER
Set priorities
Manage Product Backlog
SCRUM MASTER
Teach Scrum
Manage Process
Protect Team
Enforce Rules
Remove Blocks
TEAM MEMBER
Develop Product
Organize Work
Report Progress
STAKEHOLDERS
Observe and advise
ROLES
ARTIFACTS
Product Backlog
Sprint Goal
Sprint Backlog
Impediment List
Release
List of requirements
Owned by product owner
Anybody can add to it
Prioritized by business value
Can change without affecting the active sprint
One sentence summary
Defined by Product Owner
Accepted by Team
Decomposed task list
Driven by a portion of Product Backlog
Owned by Team
Only Team modifies it
List of impediments and
pending decisions
Owned by Scrum Master
Impediments stay on list
until they are resolved
Version of the product
Potentially shippable
Working functionality
Tested & documented according to project definition of "DONE"
MEETINGS
Daily Scrum
Time-boxed to 15 minutes
Run by Scrum Master
Attended by all
Stakeholders do not speak
Same time/place every day
Answer 3 questions:
What I did yesterday?
What I'll do today?
What's in my way?
Team updates the Sprint Backlog
Scrum Master updates the Impediment List
Sprint Review
Time-boxed to 2 or 4 hours
Run by Scrum-Master
Attended by all
Informal, informational, Discussion
Team demonstrates increment
All discuss
Sprint Retrospective
Sprint Planning
Time-boxed to 1 or 2 hours
Run by Scrum Master
Attended by Team and Product Owner
Discuss process improvement,
successes and failures
Adjust process
PART A
Time-boxed to 4 hours
Run by Scrum Master
Declare Sprint Goal
Top of Product Backlog presented by Product Owner to Team
Team asks questions & selects topmost features'
PART B
Time-boxed to 4 hours
Run by Scrum Master
Team decomposes selected features into a Sprint Backlog
Team adjust +/- features by estimates against sprint capacity
Process
Repeat
Product Backlog
Sprint Goal
Sprint Backlog
Sprint ( N days )
Daily work
Daily Scrum
Release
Impediment List
Sprint Retrospective
Sprint Review
Task board
Thank you
for
your
attention!
Sprint 1 - first user screen, get data from DB, deliver data to application XYZ
Sprint 2 - support two-way data transfers
Sprint 3 - add second user screen
Sprint 4 - support 1000 users
A Release Plan is the "strategic plan" - Product Owner's view for 2 to 4 months
Cust-featuer 1
2 Story Points
Cust-featuer 2
5 Story Points
Arch-pkg 1
5 Story Points
Doc-pkg 1
3 Story Points
Arch-pkg 2
2 Story Points
Cust-featuer 2
8 Story Points
Arch-pkg 3
5 Story Points
Cust-featuer 4
13 Story Points
Cust-featuer 5
1 Story Points
Doc-pkg 2
2 Story Points
Cust-featuer 6
8 Story Points
Cust-featuer 7
8 Story Points
Sprint Plan for Sprint 1
Cust-featuer 1
2 Story Points
Cust-featuer 1
5 Story Points
Arch-pkg 1
5 Story Points
Dock-pkg 1
3 Story Points
Create
screen
mockup
2h
Review F1
mockup with
customer
4h
Build/test F1
screen display
scenario
6h
Code database
operations
for F2
4h
Batch testing
of F2 database
operations
6h
Test F2 with F1
screen
interface
4h
Performance
and usability
tests for F2
16h
Design the A1
remote
access API
8h
Build and test
all A1 API
functions
16h
Create D1
documentation
outline
2h
Write and
review D1
document
12h
Tasks
All tasks are done, all Product Backlog Items are done
Cust-featuer 1
2 Story Points
Cust-featuer 1
5 Story Points
Arch-pkg 1
5 Story Points
Dock-pkg 1
3 Story Points
Create
screen
mockup
2h
Review F1
mockup with
customer
4h
Build/test F1
screen display
scenario
6h
Code database
operations
for F2
4h
Batch testing
of F2 database
operations
6h
Test F2 with F1
screen
interface
4h
Performance
and usability
tests for F2
16h
Design the A1
remote
access API
8h
Build and test
all A1 API
functions
16h
Create D1
documentation
outline
2h
Write and
review D1
document
12h
not started
in progress
done
Task Board Day 2
Cust-featuer 1
2 Story Points
Cust-featuer 1
5 Story Points
Arch-pkg 1
5 Story Points
Dock-pkg 1
3 Story Points
Create
screen
mockup
2h
Review F1
mockup with
customer
4h
Build/test F1
screen display
scenario
6h
Code database
operations
for F2
4h
Batch testing
of F2 database
operations
6h
Test F2 with F1
screen
interface
4h
Performance
and usability
tests for F2
16h
Design the A1
remote
access API
8h
Build and test
all A1 API
functions
16h
Create D1
documentation
outline
2h
Write and
review D1
document
12h
not started
in progress
done
Try to focus
highest priority items first ->
Keep focus and reinforce cross
functionality
Task Board Day 1
Cust-featuer 1
2 Story Points
Cust-featuer 1
5 Story Points
Arch-pkg 1
5 Story Points
Dock-pkg 1
3 Story Points
Create
screen
mockup
2h
Review F1
mockup with
customer
4h
Build/test F1
screen display
scenario
6h
Code database
operations
for F2
4h
Batch testing
of F2 database
operations
6h
Test F2 with F1
screen
interface
4h
Performance
and usability
tests for F2
16h
Design the A1
remote
access API
8h
Build and test
all A1 API
functions
16h
Create D1
documentation
outline
2h
Write and
review D1
document
12h
not started
in progress
done
Full transcript