• Share
  • Email
  • Embed
  • Like
  • Private Content
Agile at Seapine (University of Cincinnati 2011)
 

Agile at Seapine (University of Cincinnati 2011)

on

  • 1,054 views

 

Statistics

Views

Total Views
1,054
Views on SlideShare
1,009
Embed Views
45

Actions

Likes
1
Downloads
4
Comments
0

1 Embed 45

http://blogs.seapine.com 45

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Agile at Seapine (University of Cincinnati 2011) Agile at Seapine (University of Cincinnati 2011) Presentation Transcript

    • 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 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
    • 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 described above is risky and invites failure.” – Dr. Winston Royce, Proceedings, IEEE WESCON,1970
    • 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 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
    • 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 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 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/
    • Opportunities @ SeapineInterested in working at Seapine? Check out: http://www.seapine.com/careers.php
    • Questions & Answers Thank you for your time!