Agile @ Seapine SoftwareUniversity of Cincinnati Lecture Series© 2011 Seapine Software, Inc. All rights reserved
About Alan Bustamante
Agenda          What is Agile?           Why Agile?         Agile Challenges
Agenda          What is Agile?           Why Agile?         Agile Challenges
An Umbrella Word
A Set of Values  Individuals &     Process &  Interactions      Tools         “…while there is value in                   ...
Agenda          What Is Agile?           Why 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 des...
Traditional Methods“Requirements”   Rigid Change   Unhappyand BDUF         Control        Customer
Agile Iterative and Incremental                             Happy                             Customer
Iteration Contents
It’s About Feedback
It’s About Risk
Activities – Task Board            Product                       Iteration                       To-Do                  WI...
Burn Down
A Parting Thought           $200,000
Agenda          What is Agile?           Why Agile?         Agile Challenges
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    so...
Challenges►   Cooperation►   Estimates►   Test-Driven Development►   Pair Programming►   QA and Documentation►   User Stor...
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 t...
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-fr...
User Stories►   Starting out, it’s hard to write good user stories.►   Can’t explain how to write good user stories – it  ...
Why Agile is Worth It►   Estimates – team members participate in estimation    of all user stories►   TDD – better design,...
Conclusions►   Learn value of Agile►   Directly demonstrate value of Agile►   Use our tools to develop using Agile
Additional ResourcesAgile on The Seapine View http://blogs.seapine.com/category/agile/Ramblings of an Agile Padawan http:/...
Opportunities @ SeapineInterested in working at Seapine? Check out: http://www.seapine.com/careers.php
Questions & Answers         Thank you for your time!
Upcoming SlideShare
Loading in …5
×

Agile at Seapine (University of Cincinnati 2011)

1,305 views

Published on

Published in: Technology, Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,305
On SlideShare
0
From Embeds
0
Number of Embeds
47
Actions
Shares
0
Downloads
9
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Agile at Seapine (University of Cincinnati 2011)

  1. 1. Agile @ Seapine SoftwareUniversity of Cincinnati Lecture Series© 2011 Seapine Software, Inc. All rights reserved
  2. 2. About Alan Bustamante
  3. 3. Agenda What is Agile? Why Agile? Agile Challenges
  4. 4. Agenda What is Agile? Why Agile? Agile Challenges
  5. 5. An Umbrella Word
  6. 6. A Set of Values Individuals & Process & Interactions Tools “…while there is value in the items on the right, we value the items on Working Comprehensive Software Documentation the left more.” Customer Contract Collaboration Negotiation Agile Manifesto, 2001 Responding To Change Following A Plan www.agilemanifesto.org
  7. 7. Agenda What Is Agile? Why Agile? Agile Challenges
  8. 8. Traditional Software Projects Standish Group Chaos Report, 2004, 2006, 2009
  9. 9. A Tale of Two Triangles
  10. 10. Traditional Waterfall “I believe in this concept, but the implementation described above is risky and invites failure.” – Dr. Winston Royce, Proceedings, IEEE WESCON,1970
  11. 11. Traditional Methods“Requirements” Rigid Change Unhappyand BDUF Control Customer
  12. 12. Agile Iterative and Incremental Happy Customer
  13. 13. Iteration Contents
  14. 14. It’s About Feedback
  15. 15. It’s About Risk
  16. 16. Activities – Task Board Product Iteration To-Do WIP Complete Task Task 10 Task Task Task User Story User Story User Story 5 8 13 5 Task Task Task 8 User Story 1 User Story User Story 3 13 User Story Task Task 8 4 16 Task Task User Story User Story 5 5 Task 10 Bug Fix User Story User Story Task Task Task 2 3 User Story Task Task 5 Bug Fix User Story User Story User Story Bug Fix
  17. 17. Burn Down
  18. 18. A Parting Thought $200,000
  19. 19. Agenda What is Agile? Why Agile? Agile Challenges
  20. 20. Challenges to Implementing Agile Katie Dwyer
  21. 21. 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
  22. 22. Challenges► Cooperation► Estimates► Test-Driven Development► Pair Programming► QA and Documentation► User Stories
  23. 23. Cooperation► Estimates (Planning Poker)► Product Owner► QA analysts► Technical writers
  24. 24. Estimates► Normally done in hours► Story points don’t directly correspond to hours► Requires cooperation from team to come up with estimates
  25. 25. Test-Driven Development► Legacy code► C++► Qt► Different mindset► Fending off cowboy coding► Demo
  26. 26. Pair Programming► Personality conflicts► Can’t be done with one developer
  27. 27. 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
  28. 28. 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.
  29. 29. 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
  30. 30. Conclusions► Learn value of Agile► Directly demonstrate value of Agile► Use our tools to develop using Agile
  31. 31. Additional ResourcesAgile 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/
  32. 32. Opportunities @ SeapineInterested in working at Seapine? Check out: http://www.seapine.com/careers.php
  33. 33. Questions & Answers Thank you for your time!

×