Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

An Automation Culture: The Key to Agile Success

For organizations developing large-scale applications, transitioning to agile is challenging enough. But if your organization has not yet adopted an automation culture, brace yourself for a big surprise because automation is essential to agile success. From the safety nets provided by automated unit and acceptance tests to the automation of build, build verification, and deployment processes, the iterative nature of agile demands a culture of automation across your engineering organization. Geoff Meyer shares lessons learned in adopting a test automation culture as the Dell Enterprise Systems Group simultaneously adopted Scrum and agile processes across its entire software product portfolio. Learn to address the practical challenges of establishing an automation culture at the outset by ensuring that your organizational makeover incorporates changes to your hiring, staffing, and training practices. Find out how you can apply automation beyond the Scrum team in areas of continuous integration, scale and stress testing, and performance testing.

2.
Geoff Meyer
Dell, Inc.
A test architect in the Dell Enterprise Solutions Group, Geoff Meyer has
more than twenty-seven years of experience as a software developer,
manager, test architect, and business analyst. Geoff co-chairs the Agile
Steering committee within Dell Enterprise Solutions Group which guides
the software development practices of more than 600 development, test,
and UX engineers across three Global Design Centers. He is an active
member of the Agile Austin community.

6.
9/3/13%
Why is Automation So Important in Agile?
• Near-term
– Ensures that you don’t break what you just built
– Provides safety net for developers & rapid feedback to new changes
– Continuous Integration and use of Build Verification Test (BVT)
• Long-term
– Maximizes velocity of Scrum team
– Creates capacity for Exploratory and ad-hoc Testing
– Enables activities that can’t be done cost-effectively by humans
And if you don’t…
Quality is at risk from an unmanageable regression suite
Differences with Automation in Waterfall?
In Waterfall…
• Automated tests are derived from the backlog of
completed features
– In Agile, Automation can be incorporated in the requirement
• Testing and automation is performed after Development is
“complete”
• Focus is on first-time discovery of defects and optimizing
your test coverage
vs. Agile… where automation development is ongoing
and provides immediate feedback throughout
development
8
4%