Agile Dev, Better Software & DevOps Conference West 2015

PRESENTATIONS

Mobile App Testing: Design Automation Patterns You Should Use

In mobile app development, better test design is important to project velocity and user satisfaction. Jon Hagar explores underused or poorly practiced test design automation approaches that you should employ in development and testing. Jon begins by defining the domain of mobile app...
Jon Hagar, Grand Software Testing
Overcome DevOps Adoption Barriers to Accelerate Software Delivery

Many organizations want to create systems delivered in a DevOps framework with diverse services implemented via API building blocks. Chris Haddad says that people, processes, and tools often hinder a team's ability to comply with security policies, streamline collaboration, and rapidly...
Chris Haddad, WSO2
Prevent Test Automation Shelfware: A Selenium-WebDriver Case Study

Eid Passport had a suite of Selenium tests with a bad reputation—difficult to maintain, broken all the time, and just plain unreliable. A tester would spend more than four days to get through one execution and validation pass of these automated tests. Eid Passport was ready to toss these...
Alan Ark, Eid Passport
Requirements and Acceptance Tests: Yes, They Go Together

The practice of software development requires a clear understanding of business needs. Misunderstanding requirements causes waste, slipped schedules, and mistrust. Developers implement their perceived interpretation of requirements; testers test against their perceptions. Disagreement can...
Ken Pugh, Net Objectives
Requirements Are Simply Requirements—or Maybe Not

People talk about requirements, use identical terms, and think they have a common understanding. Yet, one says user stories are requirements; another claims user stories must be combined with requirements; and another has a still different approach. These “experts” seem unaware of the...
Robin Goldsmith, Go Pro Management, Inc.
SAFe Integration Patterns: Scaling with Continuous Collaboration

“Going agile” at a fifty-person startup is easy; at a 5,000 person ISV it’s impressive; and in a Fortune 500 company it’s often a nightmare. At large scale, the sheer number of legacy systems, stakeholder specific tools, and governance processes can turn even a simple agile deployment...
Jeff Downs, Tasktop Technologies
Teaching Pointy-Haired Bosses to be Agile Enablers

Ryan Ripley says that Scrum failures can often be traced back to management not understanding their role in an agile world. What gets managed during an agile project? How is success measured? Will I keep my job in the transition? Managers have all these questions and more during an agile...
Ryan Ripley, AgileAnswerMan.com
The Business Analyst Role on Agile Projects

Agile—a single word that sparked unprecedented confusion in the technology world. When it went agile, did your organization throw out your business analyst team? Have they banned all requirements documentation? Are teams struggling to see the big picture? Brian Watson has encountered...
Brian Watson, VersionOne
The Tester Role in the Agile Release Train

In a classical agile team, testers and developers work together on feature teams to produce functioning software in each sprint. As enterprises scale up their agile adoption, the agile feature teams must work in concert with many other teams, such as component teams and system teams. They...
Malcolm Isaacs, HP
User Stories: From Fuzzy to Razor Sharp

User stories are the basis for products built using agile development. User stories are relatively short, comprised of enough information to start the development process, and designed to initiate further conversation about details. Short doesn’t necessarily mean useful. Ambiguous stories...
Phil Ricci, Agile-Now

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.