Agile Software Development

Project
Unique work
Timeframe established
Driven by people
Limited resources

Process
A set of established interdependent activities that take inputs and produce results.
Models
Waterfall (R, D, I, T, M)
Spiral (risk management, waterfall + prototyping)
Iterative and incremental (vertical slices)
Agile (iterative model and change emphasis)

Since the 80's

Velocity

The product's life cycle it's more short
Continous innovation
Uncertainty

Requirements and scenarios changes rapidly

How to succeed in the new scenario?
Continuous feedback
Add great value to the product
Early time to market
The product isn't finished, it's in a continual development cycle

A common tale from the trenches
The client says "I want a car"

And we build ...

Angry client: "I said I want a Boeing, period!"

Client and Software Provider interaction:
Contracts
Meetings
Time estimations
Costs estimations
Costs negotiation
Discussions and negotiations
Re scheduled agendas

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

Does the Agile Manifesto says " Left is cool and right is bad" ?

NO

The Agile motto
"It's all about teams working together to produce great software"
"Embrace change"

Agile Software Development
Agile is a set of process frameworks
Extreme Programming
Lean
Scrum
Kanban (software maintenance phase)

The Agile cycle

Agile - Team Workspace
It's for the team
The team organize desks, library and billboards
Books corner
Meeting room

Agile - Innovation
An environment without innovation leads to bored and unmotivated teams.

New technologies
New practices
Golden cards
Don't forget about continuous improvement

Agile - Planning meeting
Planning the next sprint
What to build?
Understand
Business requirements
Business stakeholders
Stories
Tasks
Validations
"As a <role>, I want to <functionality> so that <benefit>"
Understand impact on design

Estimating is not guessing
All the team participates in the estimation

Don't take into account who will implement each story
POCs to decrease guessing when there are no experience with the platform, language, libraries
Write the estimations on the corresponding cards

Team capacity
How much effort the team can deliver in the next sprint?
Meetings
Works in another project
Previous team's velocity
Estimation + Team capacity => Sprint backlog
Tasks and stories are put on the team board

Agile - Daily Standup
Questions
What did I do yesterday?
What will I do today?
What's in my way?
Improve team communication
Talk about the project, nothing else
Short time period, 15 minutes
Around the team board

Agile - Team Board
Stories, tasks and charts

Agile - Team Board
Burn down chart

Agile - Team Board
Burn up chart

Agile - Day to day
Automated tests

Continuous integration

Incremental design

Refactoring

Collective code ownership

Broken windows

Agile - Demo
Prepare for the demo

Be aware of the expectations

Separate environment

Take notes on feedback

Celebrate success

Agile - Retrospective
Process improvement
What were the problems?

Why occurred?

Take actions to avoid the problems in the future

bye :)

http://blog.moove-it.com	297
http://paper.li	2
http://www.moove-it.com	1
http://translate.googleusercontent.com	1

Agile Software Development

by gian-zas on Jun 03, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

4 Embeds 301

Statistics

Agile Software Development — Presentation Transcript