Agile @ Seapine SoftwareUniversity of Cincinnati Lecture Series

© 2011 Seapine Software, Inc. All rights reserved

About Alan Bustamante

Agenda

Why Agile?

Agile Challenges

What is Agile?

Agenda

What is Agile?

Why Agile?

Agile Challenges

An Umbrella Word

A Set of Values

Process &Tools

WorkingSoftware

Individuals &Interactions

Customer Collaboration

ComprehensiveDocumentation

RespondingTo Change

ContractNegotiation

FollowingA Plan

Agile Manifesto, 2001 www.agilemanifesto.org

“…while there is value in

the items on the right,

we value the items on

the left more.”

Agenda

Why Agile?

What Is Agile?

Agile Challenges

Traditional Software Projects

Standish Group Chaos Report, 2004, 2006, 2009

A Tale of Two Triangles

Traditional Waterfall

“I believe in this concept, but the

implementation described above is

risky and invites failure.” – Dr. Winston

Royce, Proceedings, IEEE WESCON,1970

Traditional Methods

“Requirements”

and BDUF

Rigid Change

Control

Unhappy

Customer

Agile Iterative and Incremental

Happy

Customer

Iteration Contents

It’s About Feedback

It’s About Risk

Activities – Task Board

Product Iteration WIP Complete

Bug Fix

User Story

To-Do

User Story

User Story

User Story

User Story

User Story

User Story

User Story

User Story

User Story

User Story

User Story

User Story

Bug Fix

Bug Fix

Task

Task

Task

Task

Task

Task

Task

Task

Task

Task

TaskUser Story 5

8

User Story

3

13

13

8

1

3

5 5

Task8

Task16

Task2

4

Task10

Task5

Task5

Task10

Burn Down

A Parting Thought

$200,000

Agenda

Agile Challenges

What is Agile?

Why Agile?

Challenges to Implementing Agile

Katie Dwyer

Background

► Been at Seapine Software for ~5 years. One year

as a software support engineer, and four years as a

software engineer on the Surround SCM team.

► Recently started learning and using Agile to give

Seapine credibility in Agile development space

► I develop using Agile – everyone else is still using

Waterfall

Challenges

► Cooperation

► Estimates

► Test-Driven Development

► Pair Programming

► QA and Documentation

► User Stories

Cooperation

► Estimates (Planning Poker)

► Product Owner

► QA analysts

► Technical writers

Estimates

► Normally done in hours

► Story points don’t directly correspond to hours

► Requires cooperation from team to come up with

estimates

Test-Driven Development

► Legacy code

► C++

► Qt

► Different mindset

► Fending off cowboy coding

► Demo

Pair Programming

► Personality conflicts

► Can’t be done with one developer

QA and Documentation

► QA analyst usually writes test cases based on up-

front feature design. Since there is no up-front

design, how should this happen?

► Technical writers usually write documentation

based on the feature design as well.

► Solution: QA analyst and technical writer must

attend sprint review meetings

User Stories

► Starting out, it’s hard to write good user stories.

► Can’t explain how to write good user stories – it

comes with practice.

Why Agile is Worth It

► Estimates – team members participate in estimation

of all user stories

► TDD – better design, you know immediately if you

broke other code

► QA – test earlier, adapt to changes easier

► Scope changes – don’t waste time designing

features that you won’t have time to implement

Conclusions

► Learn value of Agile

► Directly demonstrate value of Agile

► Use our tools to develop using Agile

Additional Resources

Agile on The Seapine View

http://blogs.seapine.com/category/agile/

Ramblings of an Agile Padawan

http://blogs.seapine.com/padawan/

Agile Expedition

http://www.seapine.com/exploreagile/

Opportunities @ Seapine

Interested in working at Seapine?

Check out: http://www.seapine.com/careers.php

Questions & Answers

Thank you for your time!