Agile presented by Jeff Bollinger & Cliff Robbins at SCSU on 2/15/2012.

1. Agile

2. About us
Jeff Bollinger
CTO
jeff.bollinger@w3i.com
@Jbollinger
• www.jeffbollinger.net
Cliff Robbins
Software Development Manager
cliff.robbins@w3i.com
@DeadBigRedDog

3. Agenda
• Waterfall
• Agile
• Scrum @ W3i

4. What’s a Development
Methodology?
Idea  Software

5. Methodologies
• Waterfall
• Agile
– Scrum W3i’s Flavor
– XP
– Kanban

7. Waterfall
Requirements
Design
Implementation
Testing
Deployment
Maintenance

8. Waterfall The Real World
Requirements Change
Design
Implementation Takes too long
Gets skipped Testing
Deployment
Maintenance

9. Waterfall Works Well When…
• Requirements are stable
• Technology is well
known and mature
• Everything happens as
one would expect
• We are not taking on
anything new or
unknown
• We have done this many
times before

10. What is Agile?
• Iterative Development
• Requirements and solutions evolve
• Collaboration between self-
organizing cross-functional teams

11. Agile Manifesto
Individuals &
over Processes & Tools
Interactions
Comprehensive
Working Software over
Documentation
Customer Contracts and
over
Collaboration Negotiation
Responding to
over Following a Plan
Change
http://agilemanifesto.org/

12. Agile Principles

13. Embrace Change
Welcome changing
requirements, even
late in development.
Agile processes
harness change for the
customer's
competitive
advantage.

14. Frequent Delivery
Deliver working
software frequently,
from a couple of
weeks to a couple of
months, with a
preference to the
shorter timescale.

15. Early Delivery
Our highest priority is
to satisfy the
customer through
early and continuous
delivery of valuable
software.

16. Collaboration
Business people and
developers must
work together daily
throughout the
project.

17. Motivated Individuals
Build projects around
motivated
individuals. Give
them the
environment and
support they need,
and trust them to get
the job done.

18. Conversation
The most efficient
and effective method
of conveying
information to and
within a development
team is face-to-face
conversation.

19. Working Software
Working software is
the primary measure
of progress.

20. Sustainable
Agile processes
promote sustainable
development. The
sponsors,
developers, and
users should be able
to maintain a
constant pace
indefinitely.

21. Simplicity
Simplicity--the art of
maximizing the
amount of work not
done is essential.

22. Technical Excellence
Continuous attention
to technical
excellence and
good design
enhances agility.

23. Self Organizing Teams
The best
architectures,
requirements, and
designs emerge
from self-organizing
teams.

24. Tune and Adjust
At regular intervals,
the team reflects on
how to become more
effective, then tunes
and adjusts its
behavior accordingly.

25. Why Agile?

26. The Agile Paradigm Shift
Waterfall Agile
Fixed Requirements Resources Time
Vision
VALUE
Driven
PLAN
Driven
Estimated Resources Time Features

27. What is Scrum?
• Scrum is popular flavor of agile
• Used @ W3i for past 6 years

28. Scrum Illustration

29. Scrum
User Story Planning Meeting
Burndown Chart
Epics
Retrospective
Review Meeting
Story Points
Estimating
Backlog
Tasks
Velocity

30. User Stories
Example:
As a mobile advertiser I would
like to be able to export
reports via a web service in
order to import data into my
own system.

31. Estimating
0,1,2,3,5,8,13

32. Velocity
How fast are you
going?

33. Planning Meeting
• Specific amount of
time with specific
resources.

34. Daily Scrum
– What did you work
on yesterday?
– What are you going
to work on today?
– What are your
roadblocks, if any?

35. Burndown

36. Sprint Reviews
Time to show off

37. Retrospectives

38. Questions?
We’re Hiring!
- Summer Interns
- .NET Developers
Jeff Bollinger Cliff Robbins
CTO Software Development Manager
jeff.bollinger@w3i.com cliff.robbins@w3i.com