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

Agile development

No description
by

Ian Jones

on 11 April 2016

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile development

Agile
devel pment
(My interpretation of)
What does
'Agile' mean?
Nothing/everything!
Iterations
Pair programming
No documentation
Unit testing
Hacking it in
No control
Fast
Silver bullet
Code review
Scrum
XP
Burn-down
Feedback
No testing
No planning
No design
Agile manifesto
over processes and tools

over contract negotiation

over following a plan

over documentation
Responding to change
Individuals and interactions
Working software
Customer collaboration
value
value more
Agile principles
Early, frequent and continuous delivery of valuable
software.
Welcome changing requirements.

Simplicity is essential.

Work with the business daily.

Working software is measure of progress.

Attention to technical excellence and good design.

Reflect on how to become more effective.
So how do WE apply all this?
Project
Release
Release
Iteration
Iteration
Release
Iteration
Day
Day
Day
For professional developers only
(2m+)
(~1m)
(~2w)
(~1d)
Putting it together...
how principles map
to practices
Definition of 'done',
Burn-downs
Retrospectives
Daily stand-up
Iteration review
Product backlog
'Vertical' slicing,
Incremental delivery
Product backlog
Estimated set of requirements prioritized by the business
Change welcome
Waterfall delivery
Analysis
Design
Coding
Deploy
Testing
3 months
Incremental delivery
3 months
Coding
Analysis
Deploy
Design
Testing
iteration 1
Analysis
Deploy
Design
Testing
iteration 1
Analysis
Deploy
Design
Testing
iteration 1
Development approach
GUI
Database
server
Requirement 1
GUI
Database
server
'Vertical slicing'
Slice 1
Vertical slicing
Each slice delivers small amount of business benefit
Slice 1: Very simple compare - there are differences
Slice 2: Simple compare - What's different
Slice 2: Add filters and dates
Example - compare benchmarks:
Product backlog
User requirements
Requirement 2
Requirement 3
Req 1, Slice 1
Req 1, Slice 2
Requirement 3
Req 1, Slice 3
Slices (stories)
Req 2, Slice 1
Req 2, Slice 2
Req 3, Slice 1
Req 3, Slice 2
slice slice slice
backlog
estimate estimate
Req 1, Slice 1
Req 1, Slice 2
Req 1, Slice 3
Req 2, Slice 1
Req 2, Slice 2
Req 3, Slice 1
Req 3, Slice 2
1
2
3
2
2
1
2
Get business benefit, and feedback sooner
'Points' estimating
Points are measure of relative size and complexity
Whole team estimates
Estimating poker
Burn down
Velocity
Remaining points over time
Points not counted until 'done'
Average points done per iteration
Use historical statistics to predict future
Release early. Release often.
Eric Raymond
Track with burn-down
Test automation
Retrospective
Beta release every week
Iteration planning meeting
Req 1, Slice 1
2
Req 2, Slice 1
2
Task 1
Task 2
Task 3
Task 4
Task 1
Task 2
Task 3
Task 4
Break down into detailed tasks with whole team
Iteration dashboard
Iteration review
Break down into detailed tasks with whole team
Estimate tasks in rough hours
Retrospective
Daily Standups
1) Accomplished since last stand-up
2) Accomplish before next stand-up?
3) What obstacles are impeding me?
4) Do you need help from anyone?
Full transcript