Agile Dev, Better Software & DevOps Conference East 2015
PRESENTATIONS
Continuous Integration Is for Everyone—Especially DevOps
Continuous delivery and deployment are taking center stage in the DevOps conversations. Neither continuous delivery nor deployment are easy to jump into, and both make a lot of assumptions about the applications being released. Continuous integration (CI), however, is for everyone who... |
Chris Riley, Sauce Labs
|
Data-Driven Software Engineering for Agile Teams
Remember the old days when software engineering teams used to tune software until it passed quality gates, gave golden bits to marketing, and finally threw a big release party? The world was simple, and writing code that worked according to a specification was enough to be a star... |
Viktor Veis, Microsoft |
Detection Theory Applied to Finding and Fixing Defects
Detection theory says: When trying to detect a certain event, a person can correctly report that it happened, miss it, report a false alarm, or correctly report that nothing happened. Under conditions of uncertainty, the decision to report an event is strongly influenced by how likely it... |
Ru Cindrea, Altom Consulting
|
Don't Bulldoze a Vibrant Ecosystem for Agile
Software processes are commonly portrayed using machine metaphors in which consistency is highly prized. Frequently, organizations set up Centers of Excellence in a well-intentioned effort to create enterprise consistency. Steve Adolph reminds us that, in reality, software development... |
Steve Adolph, Blue Agility |
Emerging Product Owner Patterns in Large Organizations
Many organizations are actively searching for the perfect product owner—a unicorn who knows all about the product, anticipates the market, innovates, and improves the product’s quality and architecture, all while making and meeting commitments to the organization. That's a difficult if not... |
Timothy Wise, LeadingAgile |
Exploratory Testing: Make It Part of Your Test Strategy
Developers often have the unfortunate distinction of not thoroughly testing their code. It’s not that developers do not understand how to test well; it’s just that often they have not had an opportunity to understand how the product works. Kevin Dunne maintains that implementing a... |
Kevin Dunne, QA Symphony
|
Fostering Long-Term Test Automation Success
In today’s environment of plummeting software delivery cycle times, test automation becomes a more critical and strategic necessity. How can we possibly keep up with software delivery’s explosive pace while retaining satisfactory test coverage, keeping the reins on costs, and reducing... |
Carl Nagle, SAS Institute, Inc. |
From Waterfall to Agile: A ScrumMaster’s View
In less than one year, a leading software company's product team transitioned from a twenty-five year history of waterfall development to using agile methodologies. They had produced software the old-fashioned way—sequentially, firmly entrenched in the process and procedure of pure... |
Andrew Montcrieff, Veritas |
Getting the Most Value from Feedback Systems: Daily, Every Sprint, and Every Release
Agile methods are empirical. You must inspect and adapt to make agile work. This requires using effective feedback systems which are vital to your success. Agile teams often suffer from agile feedback systems that are dysfunctional—non-existent, delayed, or no learning from feedback. |
Satish Thatte, VersionOne
|
Going Agile? Three Conversations to Have Before You Start
All too often, companies adopt a mission to “go agile” before truly understanding what that entails. Business managers are quick to jump on the agile bandwagon, believing that going agile will magically make projects happen faster. Teams are getting certified in Scrum believing it is the... |
Heather Fleming, Gilt, and Justin Riservato, Gilt |