What is Agile?

• So what is Agile?
• Fast releases?
• No documentation?
• Automation?
• What do you guys think?

• Are you confused?
• There are a lot of ways that people talk about agile

• Agile software development is a group of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.

What did we learn at STP 2015?

• San Diego is home to the USA’s largest wooden structure; the Hotel Del Coronado is in San Diego on Coronado island.
• Get your gears going. WD-40 was invented in San Diego by the Rocket Chemical Company in 1953.
• San Diego enjoys beautiful weather year round with an average daily temperature of 70.5° F (21.4 degrees Celsius).

The Three Wise Men!

• Heard from 3 interesting individuals
• Bob Galen
• Matt Heusser
• Curtis Stuehrenberg

• Spoke of the 3 pillars of Agile Quality
• Speak to the slide

3 Amigos!

• Another interesting note was the 3 amigos
• tester developer and designer/product owner get together to discuss each user story
• this creates an opportunity for everyone to discuss requirements
• testers can provide input immediate feedback and ensure that edge cases are covered

• Talked about the major ceremonies in Agile: Daily standups, sprints, backlog planning, demo and retro
• using standups to solve issues not talk about how long something has been outstanding
• 3 major roles in a agile environment: scrum master, team member, and product owner
• one issue that companies encouter is that done does not include tested
• have testing tasks on the board as well
• plan regression into sprints
• FireFighting: team should support it's own software
• make stories for support work
• bug hunts oculd be used to prevent firefighting
• timebox activities and see what you can find

• Document not what you are going to do but what you did
• worry about customers and their value (customer centric test planning)
• make sure what you look at is important to you customer, not to you
• only document what you need to remember
• 10 minute test plan
• minimum value that needs to be met.
• insert value statements
• attributes, capabilities and components
• do exploratory testing in a time box fashion
• do pairing with product owners/users
• you are not writing tests, you are recording your experimentation
• write observations whil you are doing it, not after.
• after action review: what went right, observations, what didn't, what can we improve.
• validation and verficiation should be part of regression, exploratory testing is ours.

What is going on @OTPP?

• so we are agile-ish

The Agile Projects

• We have a few projects that are using Agile methodologies
• Legacy, Mobile, New Web, EIS-Dekstop and PBS Desktop

Agile Boards

• We are using the Scrum work for new web
• EIS desktop started using it as well
• gives visibility of everything going on as well as where the bottleneck is

Daily Standups!

• Daily standups are happening
• discuss blockers and issues, and reasons for things sitting around for a while
• present an opportunity for people to speak up

• automation rules the world
• we are using mock data on new web to test out the UI functionality
• apis are being tested via automation as well
• this frees up the testers time to do exploratory testing and provide feedback on requirements/acceptance criteria

• On new web and the desktops the three amigos are talking before work is started
• as mentioned, this provides for a venue where each story can be discussed thouroughly before work happens
• this saves time once the work is done as everyone is aware of the expectations

• requirements are being documented more often now in user stories
• each user story has success criteria, and the tester know exactly what to look for
• the stories are also estimated and allow for planning of each sprint

• hipchat is being widely used
• provides for persistent data
• allows users to get quick answers from anyone on the team, and saves the data for anyone to see

• so what can we do to be more Agile in the future?

• consistency is important
• we need to make a commitment across projects
• be more agile from a testing point of view

• we should have discussions between the different projects
• compare and contrast how we are doing things
• develop some standards

• we should make our automation leaner
• less testing E2E
• more mocking for UI testing
• expand the tests on the bottom
• less validation and verification

Exploratory testing!

• structured exploratory testing
• 10 minute test plan
• pair testing on the UI
• write down observations
• any bugs found can then be put into regression testing

Fun Stuff

San Diego!

Thanks!