Most organizations find themselves organized in silos either because of a level of comfort and familiarity or a belief system based on separation of concerns (maybe one in the same).  This type of separation usually creates some unattractive side effects, which typically include, duplication of effort, break downs in collaboration, and a fragmented delivery model.  These issues are further exacerbated when dealing with a significant amount of Legacy code or just code with detectable levels of Technical Debt.  This session will show how Extreme Programming Practices such as Test Driven Development, Pair Programming and others will aid in creating great teams that yield great software.  Case studies discussed will include exploration in teams focused on Embedded Systems along with traditional purely software oriented agile teams.  It is often said that Agile teams tend to be lax, and unstructured but that could not be further from the truth.  Great agile teams are efficient, well tuned, and center them selves on outcomes rather than outputs.

 

 
1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

The talk will start off with an introduction to Behavior Driven Development along with a focus on complexity of testing a system that was not designed with testing in mind.  From there the talk will take the audience on a journey first with the basics of refactoring to allow for testability and Continuous Delivery as well as how adopting these techniques can shorten the feedback loop and bug detection cycle.  To add context, I will include a few case studies from highly regulated industries while saving a few minutes for a quick question and answer session toward the end.

 

Learning Outcome

At the conclusion of this talk, we will demonstrate strategies that will help create efficient teams that share a common understanding of success.  Along with outlining how adopting varying requirement solicitation and documentation strategies to drive an automated testing strategy that grows in parallel to the System Under Development.  The audience will also get an understanding of where these strategies have worked best in real world scenarios along with some of the shortcomings.

 

Target Audience

Testers, Application Developers, Software Mangers,

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal