Choose the date of which you would like to view the schedule of speakers and topics from the drop down box on the top or bottom right hand corner of the page. CLICK ON the name of the speaker to instantly view his or her bio.
CLICK HERE to navigate back to the QAAM conference home page.
CLICK HEREfor a printable version of the schedule WITHOUT abstracts of the scheduled presentations, or
CLICK HERE for a printable version WITH abstracts.
What to Test from a Security Perspective: An Introduction to Security Testing for the QA Professional
The software quality domain is undergoing a significant transformation as the importance of security as a dimension of quality becomes more and more important. Driven by an increasing awareness of the vulnerability of software to attack and the enormous impact that its exploit can lead to (e.g. the recent TJX case), more and more software development organizations are working to integrate security assurance into their SDLC. Looking to build on that which they already know, many organizations are adding this responsibility to the QA role. Unfortunately, while it is easy to understand the idea of security as an element of quality, there historically has been very little training or knowledge resources available for QA professionals to practically understand effectively take up this responsibility. This presentation will strive to alleviate some of the confusion and consternation of the QA professional attempting to get a handle on the apparent black art of software security and what it will mean to them. The presentation will discuss the concerns and issues of software security, how they fit against and integrate with existing quality processes, will briefly introduce several new security-focused QA activities that can seamlessly integrate as touchpoints along any SDLC and will suggest some resources for further exploration of these topics.
Software Quality Professionals in Information Technology For many years the position of quality in a software organization related to testing. With the introduction of the CMM® (predecessor to the CMMI®) and such certifications as the Quality Assurance Institute’s (QAI) Certified Quality Analyst (CQA) and the American Society for Quality’s (ASQ) Certified Software Quality Engineer (CSQE), software organizations recognized the process facet of the Software Quality Professional. IT organizations are in a similar quandary. There are very few requisitions for IT Quality Professionals. Positions that have quality related responsibilities are often referred to as data analysts, customer care specialists, customer advocates, or change managers. Since ISO 20000 harmonizes with ISO 9001 and the recent revision to ITIL® has a service quality management component, it will not be long before an IT Quality Professional will come into existence.
This session examines some of the parallels and differences between software and IT by comparing the bodies of knowledge between the Software and IT Quality Professional. This examination will demonstrate that the principles and concepts between the two are very close and with some work the Software Quality Professional can easily fit into the IT world. The presentation is based on Mr. Moreau’s chapter in the upcoming release of G. Gordon Schulmeyer’s 4th edition of the Software Quality Assurance Handbook.
Understanding and Managing Work Break Down Structures (WBS) for Determining Project Progress What is a Work Breakdown Structure (WBS)? Why should your project have a WBS? How can managers leverage the benefits of using a WBS? This session will present the basics about Work Breakdown Structures - who, what, where, when, why, and how - emphasizing the application of WBS concepts to the management of information technology. Based on the Project Management Institute's Practice Standard for Work Breakdown Structures - Second Edition, this interactive presentation will provide grounding in WBS basics for new managers, and key pointers in using a WBS for more experienced managers.
Introduction to Work Breakdown Structures (WBS):
WBS: What is it?
WBS: Why use it?
WBS: How to create it?
WBS: Quality checklists
WBS: Create your own!
WBS: Last words on how to implement effectively on a project.
Assuring Certainty in Minimizing Risk
Overview: This Paper focuses on Best Practices followed in Reducing the Business Risk, Highlighting the unique practices observed in successful testing, paper stresses the importance of repeatable processes to improve the effectiveness of testing and there by minimize the risks. Explaining the concept through case studies, demonstrating the importance of structures and process. Methodology minimizes project risk and enables us to streamline testing delivery to achieve customer satisfaction. This paper is based on our experience in testing of a Product Data Management application of one of the global market leader in automotive systems and facility management and control
The Business Case for Automated Testing
The Challenge: Typically, more than 60% of the overall effort in developing and delivering software products is spent on testing. Test time and cost is expected to continue to increase as the complexity of software applications is continuing to grow and as is the desire to deliver products more quickly. This presentation discusses the use of test automation to help reduce test efforts and testing costs. The presentation will focus on describing how the test automation increases the efficiency of the testing team, allows last minute releases to be tested quicker, and reduce the cost of testing overall. From a test engineer's perspective, automation should increase efficiency, reduce tedious data entry, allow for increased analytical time, and provide career enhancing skills. This presentation will describe the business case for test automation.
Pull the Plug Sooner Than Later: Don't Exceed Your Risk ThresholdThe Challenge: Few, if any PM’s want to admit project failure. Even fewer want to admit failure early in the project, ignoring all of the warning signs that say “success is not going to happen despite 24 x 7 heroic efforts.” We have all heard that failure is not an option.
However, thousands of projects tell a different story. Over half of all projects started do fail, and another third are completed with less than full functionality or deviate from their original budget or schedule.
Most managers realize that stopping a doomed project sooner than later may have substantial benefits, including budget savings, resource re-assignments and a sharper organizational focus on goals that can be accomplished.
Overview: How can a PM stop a project that cannot achieve its stated goals? There are several ways:
a) Develop scenarios that show stoppage may be advantageous to the organization
b) Determining benefit / savings ratios obtained from stopping the project
c) Evaluating the negative stakeholder impact of continuing forward with the project
d) Propose alternative projects that may have greater value or a successful completionUsing a case study approach derived an actual project, the audience will participate during the presentation through a series of votes about how the PM should manage the situation, with the session ending in a positive or negative note, depending on audience decisions. Learning outcomes include increased knowledge about risk identification, and knowing its better to pull the plug sooner than later.
Solving the Requirements Problem: The Final Frontier
The requirements problem plagues the software industry. The first problem is making sure you have the right requirements and the second problem is making sure you have built the right thing well. There is no future in building the wrong thing, faster, better and cheaper. I will present data gathered from 1,000s of projects from 100s of different organization and identify the root cause of the requirements problem. David will provide concrete suggestions on how to solve the requirements problem.
Project Size Estimation and Measurement Techniques
There are many tried and true estimating processes, procedures, tools, etc. that will produce a valid estimate for a project. However, an estimate is just that, an estimate. An estimate in and of itself does little for a project manager other than providing an order of magnitude of the size. What project managers really need is a tool that will help them manage their project. One area of estimating that is often overlooked is the basis of the estimate (BOE). This presentation will focus on two aspects of a BOE 1) how to develop a BOE that can be used as a tool for project managers 2) how a project manager can use a BOE to control scope and predict outcomes early instead of reacting problems.
Here are the learning objectives:
Estimating tools, models, etc. do not obviate the need for a fundamentally sound estimating process
Estimate effort using an objective and quantifiable basis of effort (BOE)
Use a BOE to identify potential project problems before the problem becomes apparent through earned value
Conduct variance analysis using the BOE
4:30 pm - 6:30 pm
CONFERENCE RECEPTION
Sponsored by QAI
Choose the date of which you would like to view the schedule of speakers and topics from the drop down box on the top or bottom right hand corner of the page. CLICK ON the name of the speaker to instantly view his or her bio.
CLICK HERE to navigate back to the QAAM conference home page.
CLICK HEREfor a printable version of the schedule WITHOUT abstracts of the scheduled presentations, or
CLICK HERE for a printable version WITH abstracts.
8:00 am - 9:00 am