Although all teams require a healthy level of interaction, high-performing teams' interactions are all based on trust, respect, and shared goals. Such teams find ways to overcome the fear of conflict, and quickly identify and resolve issues that are getting in the way. Scott Ross shares how, when the Omnyx software R&D department determined their culture was hindering performance, they crafted a core values statement that has served them well for the past three years. Scott describes the ways they proactively and intentionally use their value statement to drive the culture they seek and discusses the results they have achieved. Take back the list of resources that Scott uses daily to help himself and others see how their actions add to and take away from their core values.

Like agile development, performance testing is an iterative process in which new problems and risks are identified, and appropriate steps are taken to fix issues or mitigate risks. Experience tells us that in an agile environment, performance testing must be built into the development process, owned by the entire team, and coordinated by the performance analyst. Agile programs spanning multiple scrums running in parallel and sharing a common infrastructure present a unique set of problems that can challenge any performance analyst. Sai Subramanian shares his experience in the evolution of performance testing within agile teams. Sai discusses the strengths and challenges posed by the different levels of collaboration between the performance analysts and other project stakeholders.

By next year, 90 percent of large enterprises will include open-source software as business critical elements of their IT portfolios. However, most software development organizations have limited capability to govern the process of selecting, managing, and distributing open-source components-leaving them exposed to unforeseen technical and compliance risks. Larry Roshfeld examines how open-source components-and their dependencies-may expose your company to unforeseen and unnecessary vulnerabilities. He outlines the significant threats to software quality, stability, performance, security, and intellectual property that have occurred using such components. Then, Larry shares an action plan for balancing the risk/reward trade-offs of open-source software in the enterprise. Find out how to ensure that your organization uses only the highest quality open-source components and avoids the common vulnerabilities.

Historically, performance testing has been relegated to simply adding a few weeks to the back end of a project to run a series of prescripted tests. The problem with this approach is that issues that performance test engineers uncover late in the project are often too costly to remediate, placing the entire effort at risk. Agile development methodologies can further complicate the issue due to their ever-changing landscape and often a lack of focus on performance testing. Eric Gee shares innovative ideas and techniques on how testers can engage as meaningful partners earlier in the software development lifecycle. Eric explores the benefits of partnering with software engineers in unit testing under load, testing at the component level, and other novel approaches you can use for early performance testing. If you are concerned about finding performance problems late in development, this session is for you.