Off-shoring is a common practice nowadays. It promises a number of benefits such as easier access to talent, cost savings, and more. However, close to 50% of off-shore projects fall short of delivering the expected level of quality. How do we enjoy the benefit from off-shore teams while hedging ourselves from the dangers? As usual with complex software processes, the answer is multi-faceted. The right approach to off-shoring must include all the stages of the engagement, from choosing the partner to project closure. During this session, we will review the most important aspects: defining the criteria for choosing an off-shore partner and selecting the partner, setting up management procedures, managing project assets, project closure, and more. Special attention will be given to integrating off-shore teams into the existing work process and to the criteria for deciding which jobs are worth doing off-shore and which are better keep in-house.
Whether you are involved in small, medium, or extra-large testing projects you will benefit from this informative and entertaining session describing the planning, design and successful implementation of real world mega-testing projects at T-Mobile, FICO and a large Hospital System. The principles and strategies for managing over 400 Testers around the globe can be applied to almost any testing project. Bring your questions and biggest scariest test planning and design challenges for an interactive Q&A period toward the end of the session.
Bringing new software product features to market faster is becoming the top priority for many businesses. Testing organizations are under pressure to keep quality high while not becoming a bottleneck for application development. Applications are increasing in complexity, and cycle times are getting shorter with expanded use of Agile practices. While traditional testing methods are effective, spending weeks, months or years on project testing is not practical to meet the demands of the business. To “keep up,” testing teams must pivot to become more than a gate in the process, but be a quality enabler throughout the project lifecycle. Shifting quality left is a common phrase and testing teams will do this effectively by enabling and promoting testing practices that mimic advantageous application development engineering practices. This session will review the above challenges from the view point of a Quality Engineering (QE) team that is currently transforming its own practices to shift quality left by leveraging continuous integration, automated regression testing, “in-cycle” test automation, and developer tools enablement. With Quality Engineering, testing can keep up with the speed of application development without sacrificing quality.
In an ideal world, each project would have time to execute all test cases for all combinations of logic and devices. In reality, there is rarely enough time or resources to do this. We need to be proactive in determining what we test in order to maximize the value of our testing. Risk based testing is an approach that maximizes the likelihood of identifying important defects and minimizes the risk of unpleasant surprises. Managing testing risk requires continuously analyzing the health of projects, and their deliverables, and addressing the identified risks. Learn the guidelines for adopting risk based testing, identifying the best use of available resources, and updating testing plans to reflect and mitigate current risks throughout the project lifecycle and even before a project starts. Join Carolyn to discover how her team delivers applications with no unexpected defects being found in production.
Many organizations have encountered difficulties incorporating traditional end-of-cycle performance testing into their agile processes. In the case study presented you will learn how a global manufacturer transformed their ability to deliver high quality projects faster by adapting their traditional performance testing practices to fit an agile development approach.
Obtain tips and techniques for bringing effective performance analysis to your agile organization. Learn the thought processes required to implement performance analysis in an agile development environment. Adjust your traditional performance testing approach to support agile. Determine how to shift performance analysis earlier in the development cycle and get the information required for critical decisions earlier. Join Lee to make sure your Agile Applications will stand up under heavy load.
In today’s Agile environment, teams are expected to do more, more quickly and with less resources. The move to Agile is problematic for test teams as cuts around time and resources tend to hit the quality assurance group first and shortcuts taken by other groups can have major impacts on testing quality. Amanda focuses on processes, approaches, and tools that can help testing teams ensure quality and mitigate risk while maintaining the fast pace that businesses expect to see in an Agile environment. In particular, improving quality in an Agile environment, using automation, and ensuring the infrastructure does not stop progress are all crucial to success. Join Amanda as she addresses these problems.
Join Vikas and learn how to swiftly write test scripts using JMeter and integrate these into Jenkins. Automatically gather performance data that includes key metrics like throughput/response-time/errors and identify key outliers in logs(Splunk) and use a byte code instrumentation tool (Dynatrace) to facilitate analysis. Address the problem of running tests across different environments, release versions with a simple user interface, and integrate with a cloud-framework such as Blazemeter to perform high concurrency tests to promote Scalability.
Open source components are being used in internal IT and commercial projects. The general acceptance of the quality of many open source solutions as well as developing trends in open source licensing have made it a reasonable risk for organizations to rely on these components for at least part of their critical deliverables. This changing landscape has significant implications on test organizations and what it means to “test” the product of a modern development project.
Bruce discusses the organizational changes that are necessary to address these mixed source applications, as well as how to perform integration testing in this environment. QA needs to be involved in the architectural decisions and ensure that any vulnerabilities are included in the system threat model. Demonstration testing will not be enough to ensure the safety of these applications.
Join Bruce and deal with the reality of a Mixed Source world!
Agile methods, principles, and techniques are core to how many IT organizations develop and maintain software. Even though techniques like Test Driven Development and Scrum are widely practiced, one of the common complaints is that it is tough to scale them. Scaling Agile, in general, and Agile testing, specifically, requires having a framework to help teams, stakeholders, and program managers identify and reflect upon what is needed to deliver quality and value. Test Maturity Model Integration (TMMi) provides a framework for all forms of testing and reviews. The model provides a mechanism to identify the criteria needed to evaluate the effectiveness and efficiency of testing. The TMMi is not prescriptive; rather the model is outcome-focused so that testing is not only cost efficient, BUT also effective. Join Tom and learn how to effectively tailor and use the TMMi model in plan-based and Agile environments, and how to measure the results.
Quality plays a significant role in business success, but is often an area that is difficult to sell. Many business leaders have interesting, false, or incomplete perceptions and knowledge regarding quality and the costs associated with it. Quality managers have been told that to get the “ear” of senior management they need to present information using terminology that senior management relates to such as “bottom line” “strategic impact” etc. Since marketing has a significant presence in business today, a question can be posed, “Are there marketing models and approaches that could help quality managers sell quality more effectively?”
Using the marketing techniques of Strategic Alignment, Identifying Influence, Pain Sheet, and Value Proposition, Clyneice provides approaches and examples that will sell quality to senior management.
Join this session to get Quality Sold.
When creating system performance models, the primary challenges are where and how to start. Whatever the performance characteristics being estimated or modeled, we need a solid approach that addresses both business and system needs. All too often performance tests inadvertently mix load and stress scenarios with little regard for how this will confound recommendations and business decisions. If you are a test manager, a business process owner, or you simply want to better understand performance testing, you will be interested in Will’s case study. Will presents a real-world example that demonstrates the impact on business decisions and shows how to use production data and statistical modeling to improve both the analysis and business decisions. The study is based on a back-end re-hosting project where acceptance criteria were based on an achieving “equal or faster” performance. Take away new insights and approaches to improve performance-based decisions for your organization.
Managing risk is what a quality team does – we look for risks in requirements, code, and applications. We consider ‘what if’ scenarios to prioritize defects, thus managing software risk. Do we take that same thoughtful approach when managing the makeup of our teams? Do we consider risk of the team makeup a priority? In this session, Anne will offer a series of considerations and methods for evaluating team risk. Do you have the staff you need for upcoming projects? Are you prepared to support Social, Mobile, Analytics, Cloud, and DevOps trends? Do you have people ready for new assignments or considering retirement? Are you too heavily dependent on external support – how do you know? Join this session for a practical look at your team and leave with an understanding and the tools to assess your team’s risk and generate the appropriate risk response.
- Identify where quality teams have inherent risk
- Learn concrete ways to measure current risk of team makeup
- Build an approach to manage and minimize risk going forward
The art of test planning has always been a special skill in preparing for the unexpected. Time for testing is commonly impacted by increases in scope, delays in development, and hard deadlines. This presentation analyzes areas that should be assessed and rules of thumb for consideration when planning for test events. Efficient impact assessment of changes during all phases can determine whether changes are able to be absorbed. Building an execution schedule that incorporates the unique organizational developmental considerations including troubleshooting, deployments, and resource mix can account for potential delays. Finally, leveraging Risk Based Testing to prioritize tests based on production impact can minimize risk of untested critical functionality. Leveraging these strategies in test planning will minimize the firefighting around testing phase
There is a heated debate about the relevance of a QA team in this brave new software world of Agile development. Some say that a QA team is no longer needed because Agile calls for heavy automation. Others say that QA is needed more than ever given the fast pace of shipping software.
Not only is a QA team still very relevant in this new Agile world, but there are innovative ways that the QA team can really contribute to raising the quality bar in today’s fast paced world.
Learn how to hire and build a QA team that will be respected and counted on by the development team regardless of whether it is for an IID or Agile software development process. Find out where a QA team fits in a Testing Pyramid that involves both QA and Development.
In today’s competitive IT landscape, if you lose your data, you lose your livelihood and reputation! When data breaches occur, you have unhappy customers and it makes the news! It’s not a matter of IF, it’s a matter of WHEN a data breach will happen to YOU…
Make sure you know who to draft for your application and security testing team for the starting and bench positions. Select the correct tools and players for the field. Stay current with the vulnerabilities and issues you will encounter. Gather the statistics and build the reports to know how you are doing. Invest in continuous improvement to help ensure a winning season of application security and testing.
Join David to avoid getting a penalty flag for unsportsmanlike conduct, or even worse, making front page headline news due to a customer data breach!
An alarming 65% of apps today have a 1 star rating or less. That’s over 1.3 million apps! According to the fifth annual World Quality Report, “over half of organizations (56%) do not have the right process or methods in place to test mobile applications and 52% don’t have access to required devices.” If not addressed, these gaps will have a major impact on the quality of your mobile applications. What’s worse is that users are intolerant of issues and are quick to switch to competing apps.
Costa will share key findings from the latest World Quality Report, and explore how to address the unique challenges of mobility by starting with the right test strategy. The discussion continues with the top challenge QA leaders are faced with today: how to design a proper device lab, given thousands of unique devices. Costa also provides insight into choosing the right devices to optimize test coverage and reduce risks. Lastly, Costa shows you how to leverage existing tools and evaluate automation options, as well as how to keep your team current with the faster pace of mobility.
Metrics have always been used in corporate sectors, primarily as a way to gain insight into what is an otherwise invisible world. Organizations blindly adopt a set of metrics as a way of satisfying some process transparency requirement, rarely applying any statistical or scientific thought behind the measures and metrics they establish and interpret. Many metrics do not represent what people believe they do and as a result can lead to erroneous decisions. Joseph looks at some of the common and some of the humorous testing metrics and determines why they are failures. He further discusses the real purpose of metrics, metrics programs and finishes with pitfalls into which you fall. Attend this session and learn how to stay out the metric hole.
Do you find it difficult to complete stories on time? Is rework a consistent part of your work stream? Are your team members frustrated because they don’t understand how to test the requirements? Do you really deliver value every time? Story writing is key to successful implementations. Collaboration and conversation among analysts, testers, developers, and product owners is critical to ensure a common understanding of scope and a clear definition of done. Acceptance criteria are the foundation for defining done and testing scope, but sometimes they are hard to get right. Come to this session to learn about creating strong stories with a clear definition of done. Tips on critiquing stories to improve acceptance criteria will be reviewed. Discussion will touch on several different technology stacks for writing testable stories. Examples of strong and lacking stories will be compared and you’ll go home with a toolkit to use as you work through your own story writing process.
Most QA organizations treat test automation as a subset of their overall testing process. Thus, test automation must fit within the predefined manual test processes. However, test automation work and deliverables do not always fit perfectly into that predefined manual testing process.
Test automators must understand development standards for controls and objects, structure the tests for modularity and flexibility, and eliminate the manual efforts for the same testing function. Revisions to a typical V-model testing process are required to fuse in the test automation work and there may be changes to the manual testing process, specifically in the overall Test Plan and down to the Test Case level.
Attend this session and learn how to make your test automation processes complementary to your manual test processes and derive the maximum benefit from both.
Implementing a Culture of Quality will require the support of various IT organizations as you verify and improve processes, standards, execution, and measurements. The goal is to be sure that IT development teams focus on successful deliveries that improve or elevate the ability to execute. The Culture of Quality program promotes effective and efficient service delivery within IT by applying expertise and knowledge in process and practice improvement, and by optimizing technology and resources to achieve a superior customer experience.
Learn how to implement best practices for an optimal Culture of Quality. Obtain a roadmap to implement a Culture of Quality and create an internal and external feedback cycle for continuous improvement.
In markets driven increasingly by consumer adoption of mobile applications, a 360-degree app quality approach is the only way for brands to stand out from their competitors and turn their users into raving, loyal fans. Brian explains how to maximize the best mix of a 360-degree approach to launching great apps users love – data to plan & measure, testing under real-world conditions, and the right tools to release, monitor and optimize. 360-degree app quality combines the importance of user insights with QA and pre- and post-launch analytic research. Join Brian as he discusses real-world case studies using client anecdotes, results from testing, SDKs and analytics, and the blood, sweat, and tears a client has put into the lifecycle of an app that wins revenue, loyalty, and envy from their competition.
Software quality has traditionally been a “time-boxed” exercise and we can’t possibly expect that accelerating the SDLC via DevOps will yield better results from a quality perspective. Automating the build-test-release-deploy process will undeniably get the application into the hands of users faster. However, if you haven’t also re-engineered the processes by which the application is built and tested, you’re quite likely flooding your users with more defects at a more rapid rate.
Join Wayne to find out how a holistic continuous testing process can help you balance speed with quality by reducing the number of defects being injected into the application and mitigating existing risks before they progress to the next stage of the SDLC.
It is a struggle to make regression testing easy to manage and initiate consistently throughout multiple environments (Development, System Test, Systems Integration, etc.). Each development and test environment brings with it unique variables which make implementing consistent automation difficult. The problem is compounded in environments which have highly integrated application architectures. Leveraging Service Virtualization reduces the environment variability and makes automated regression testing easier to manage and more reusable. Robb discusses the challenges of creating consistent and re-usable automation via Service Virtualization along with specific examples. Find out how to test earlier and more often by using Test Automation and Service Virtualization. Benefit from Robb’s knowledge of the process of implementing a combined Automation-Service Virtualization solution.
We live in a world where “change” is business as usual. You may only see your team two or three times a year, but need to implement a new testing process. Change happens in the companies we work for and in our departments, as well as in our daily lives. Yolonda provides an overview of how to implement QA process changes within a globally distributed team using John Kotter’s 8 Step Change Model. She discusses the required skills of a person leading such a change which include: attitude, knowledge, team building, networking, negotiation, communication, influencing, trustworthiness, persistence, and patience, as well as the role of the Test Manager implementing change.
Join Yolonda and learn how to implement change in your organization.
Quality generates business value. Companies must now extend their brand quality to a proliferation of platforms and devices to satisfy employees, partners, and customers. Accomplishing this goes beyond ensuring a new system or initiative merely “works as expected.” Instead, companies must know how a new program will affect existing business processes, productivity, customer satisfaction, costs, and revenues. Understanding those factors requires companies to gather “quality intelligence” – and to shift away from tech-oriented quality testing to a holistic approach focused on business assurance.
Business assurance zeroes in on the points at which new programs and initiatives intersect with existing business processes. It is a rigorous, proactive method based on putting business success, resiliency, and agility first, and technology second. Learn how to apply Business Assurance to your work. Engage in active Risk Management and interact with business constituents. Understand how business assurance strategies enable companies to successfully introduce new initiatives and programs while avoiding costs and business risks.
Test teams have traditionally used document templates to communicate the test strategy and coverage for releases. However, these documents are rarely reviewed by project team members other than testers. Using the technique of mind maps, test teams can effectively initiate discussions with the business and development team members to establish testing priority and coverage and to ensure that all project team members understand and are involved in the testing strategy. In this presentation, Mush discusses how mind maps can be leveraged to visually document key business workflows and features for test coverage, reinforce domain expertise and business concepts with distributed teams, establish test prioritization and coverage per sprint/release, and report testing progress.
In the extremely fast paced world that today’s IT organizations perform in, it is not unusual for new builds to be measured in hundreds per day rather than several per week. Traditional development methodologies just can’t deliver at this pace. Enter DevOps. While DevOps provides a continuous integration strategy, all too often we only hear “development”, “operations”, and “business”. But what about “QA”? Whether DevOps is a fad or the next Agile, more and more companies are talking about it and trying to adapt it. It is the responsibility of the QA practitioners to make sure that as delivery cycles move from days to minutes we must automate the build, test and deliver processes without losing sight of Quality.
Join Tatyana Kravtsov as she describes DevOps, how DevOps is changing the product development cycle, and how QA must be an enabler not a bottleneck between development and operations.
We examine applications. We exploit applications. We break applications. It’s no wonder tension exists between QA and the rest of the project team. We are pretty close to a project team’s own personal devil (horns, pitchfork, and always trying to make people do things they shouldn’t). We need to distance ourselves from that stereotypical image. Using our roles in Waterfall and Agile we determine the impact our activities can have on various project team members. We identify the possible negative impacts and the changes to implement that improve the relationship between project team members, while at the same time improving the quality of the applications we produce.
Join Bryan and learn how to use Quality Areas to improve interactions and the overall view of QA and its processes.
Can you execute your entire test suite successfully on the first try? Great, then you do not need regression testing. Now, for the rest of us, we need to perform regression testing to ensure the functions and features that worked before the enhancement or bug fix will continue to work after the change is implemented. Regression testing is universal. It applies to all software development lifecycles – from traditional waterfall to continuous build and deployment and everything in between. Using risk based principles you can identify the test cases to include in your regression test suite for proper test coverage. Join Diane as she explains how to plan for and build out a proper regression test suite, while staying on time and in budget.
It’s not a bug, it’s a test environment problem. Environments are costly and data refreshes tedious. As a result, quality assurance professionals make compromises working in environments that do not mirror production which all too often results in false positives and bugs missed.
During the presentation, Helene Astier will discuss how to mitigate the lack of data refreshes by creating more modular test cases and using parameters to dissociate the data from the test cases. Helene will also describe how to dissociate data from automation code to make it more data independent. Additionally, Helene will dive into how to maximize your current environments aligning them to their testing process for better feature testing and more efficient regression testing. Finally, this session will help you understand the potential limitations on testing in less than ideal environments, set appropriate expectations, and “make the case” for more environments and more frequent data refreshes.
How many times have you had to delay your testing start date because the test environment was not ready, or been unable to complete your testing because you had a dependency on an external system, process, or vendor/product? How many times has it just taken too long to build the data sets?
During this session, Chockalingam Gomathisankar describes the growing trend of Service Virtualization. Chockalingam will discuss how Service Virtualization can solve many process issues including virtualizing systems that are not ready to be used, filling the gaps for processes, hardware, software, or support that may never be integrated. In this session, Chockalingam explains the benefits of Service Virtualization and will share some examples of how other companies have been successful using this process. Finally, Chockalingam will challenge you to think of how you can take this back to your own organization for immediate use.
So, what’s bugging you? Maybe it’s those everyday problems you experience as a tester or you’re just plain frustrated! “Bring it on, bring it all on” to this intensely interactive session. Don’t forget to also bring those tips and tricks you’ve found to deal with those daily challenges while still delivering high quality applications. Robert will facilitate the discussion and provide his thoughts and insights from his years of experience in the biz. When it’s done you’ll take practical and tangible advice back to your organization and start proactively adjusting your own processes and environment to deliver on the promise of quality.
Join Robert and learn how to overcome your environment’s problems and limitations. Take concrete strategies back to your workplace.