 |
 |
 |
 |
 |
||||
Mary Poppendieck Monday, Sept. 14th Time: 12:15 - 1:15 Mistake-Proof The Development Process Registration Code: MEL |
Joan Redwing Tuesday, Sept. 15th Time: 12:15 - 1:15 Agile Testing: How to Conquer Your Software Quality Concerns Registration Code: TEL |
Dr. Magdy Hanna |
Robin Goldsmith Thursday, Sept. 17th Time: 12:15 - 1:15 Quality is Key to Prospering from Bad Times Registration Code: HEL |
Matt Engstrom Friday, Sept. 18th Time: 12:15 - 1:15 Utilizing Agile Methods to Gain Greater Predictability and Less Risk on Large Scale Projects Registration Code: FEL |
Mary Poppendieck
Presentation: Mistake-Proof The Development Process
Time: 12:15 - 1:15
Registration Code: MEL
Concepts:
In 1968 Edsger Dijkstra said: “If you want more effective programmers, you will discover that they should not waste their time debugging – they should not introduce bugs to start with.” Every software development methodology ever invented has tried to meet Dijkstra's challenge, but precious few have succeeded. Why?
Two different groups of people – developers and testers – look at the same specification, at different places and different times. And they come up with slightly different interpretations of the details of the verbiage. These interpretations are not compared against each other for a long time, so slight differences get buried under complexity as the code base grows.
This is not a mistake-proofing process – this is a defect-injection process.
Instead of trying to make the requirements specification yet more precise, spending ever more time inspecting it for ambiguities, maybe it's time to admit that this approach is doomed to failure. It is time to have a single arbitrator of the meaning of the specification – and that arbitrator has to be QA. QA either writes the tests that embody their interpretation of the spec – or else they write the spec itself in the form of tests – before coding begins . Then developers don't have to guess what the spec means; they write the code to pass the tests.
This is not cheating; it is mistake-proofing the process.
Mary Poppendieck has been in the Information Technology industry for over thirty years. She has managed software development, supply chain management, manufacturing operations, and new product development. She spearheaded the implementation of a Just-in-Time system in a 3M video tape manufacturing plant and led new product development teams, commercializing products ranging from digital controllers to 3M Light Fiber™.
Mary is a popular writer and speaker, and coauthor of the book Lean Software Development , which was awarded the Software Development Productivity Award in 2004. A sequel, Implementing Lean Software Development , was published in 2006. A third book, Leading Lean Software Development , will be published in October, 2009.
Joan Redwing
Presentation: Agile Testing: How to Conquer Your Software Quality Concerns
Time: 12:15 - 1:15
Registration Code: TEL
Concepts:
People who attend this session will learn specific techniques to mitigate software quality assurance risks with agile software development. These techniques include:
- Negotiating requirements and builds
- Accomplishing structured testing in tight time frames
- Automation “holy grails” versus reality
- Increasing the profile of the tester on the agile team
- Meeting audit obligations with lighter documentation
Biography:
Joan is the Director of SQA at Pearson Vue based in Bloomington , Minnesota. She holds a Six Sigma Black Belt from GE and is also a Certified Scrum Master. She started in SQA alongside Linda Hayes – using one of the first generation automation tools (AutoTester) in the early 1990's. By the late 1990's Joan published articles on her achievements in Test Automation in Computerworld, ClientServer Magazine, and PCWeek/E-week. In the 2000's, Joan shifted her attention to test environment and workflow improvements in software testing with lean and agile methods. By using lean/agile methods, Joan was able to reduce GE's test cycle time by 45% and reduce production defects by 25%. Lastly, Joan has maintained her original passion for testing tools and has been successful with Fitnesse, Junit/Jmeter, Bugzilla among other shareware tools in addition to the top-shelf products like HP's and IBM's testing suites.
Dr. Magdy Hanna
Presentation: Scenario-Based Development and Testing
Time: 12:15 - 1:15
Registration Code: WEL
Concepts:
The quality of your release is only as good as the quality of requirements and the quality of your test design. No matter how highly skilled your developers are, poor require ments will always lead to poor test design, which will only put out bad releases. This presentation will provide an overview of the scenario-based development and testing process that is based on the use of models. This process has proven to reduce the number of defects found by the test team as well as the end user.
Outline:
- The problem with traditional development test lifecycle
- The Scenario-Based development and testing process
- Scenario Development from vague requirement statements
- Model-based scenario development
- Use Case scenarios
- Decision Table scenarios
- State Transition scenarios
Biography:
Dr. Hanna is a recognized educator, speaker and consultant in several areas of software engineering. His distinguished seminars on various topics have been highly rated by software professionals. Dr. Hanna's experience with software goes back to the mid 1970's when he worked as a developer at the NCR center in Cairo , Egypt . Over the last thirty years, Dr. Hanna has worked in all aspects of software projects and processes in all capacities.
Dr. Hanna is the founder, CEO and Chairman of the International Institute for Software Testing, (www.iist.org) the leading educational and professional development organization that provides education-based certifications to software test and quality professionals around the world.
Dr. Hanna is the founder and Chairperson of the International Conference on Practical Software Quality and Testing, (www.PSQTconference.com) and founder and Chairperson of the International Conference on Software Process Improvement, (ww.icspi.com).
Robin Goldsmith
Presentation: Quality is Key to Prospering from Bad Times
Time: 12:15 - 1:15
Registration Code: HEL
Concepts:
Those who find the opportunities in even the deepest recession not only are more likely to survive but actually can prosper. For instance, studies have shown that organizations which strengthen their marketing in tough times emerge well ahead of competitors who react typically by cutting back. Tight times highlight the fact that IT cannot afford to continue its traditional wasteful ways of paying to create, find, and fix so many defects. Attend this timely webinar to learn how learning and applying practical proven software quality practices provide low-cost high-ROI payback both immediately and long-term.
Biography:
Robin Goldsmith JD is internationally recognized as an authority on business engineering and software acquisition/development quality, testing, and productivity. He is a frequent speaker at leading conferences and formerly International Vice President of the Association for Systems Management. Robin is the author of the book:" Discovering REAL Business Requirements for Software Project Success".
Matt Engstrom
Presentation: Utilizing Agile Methods to gain Greater Predictability and Less Risk on Large Scale Projects
Time: 12:15 - 1:15
Registration Code: FEL
Concepts:
Building quality into a software development effort is a common goal among most software development efforts. Unfortunately, the changing nature of requirements can often turn the delivery of quality engineering services (testing, software configuration management, etc.) from "build it in" to 'test it in" thus making the project less efficient and introducing more risk. Utilizing agile methods for software development provides better flexibility in the process as requirements or business needs change, but it is often difficult to do this on large projects.
At Thomson Reuters we've applied agile principles to a large scale software development effort and been able to maintain "build it in" quality standards by applying agile principles to the deliver of testing and software configuration management services. Incorporating the delivery of these services as and sometimes before code is developed provides for better predictability of results as well as lower risk when the software is released. This is realized in maximized development productivity, immediate feedback on the impact of changes to the system and the discovery of more defects as code is written. In this discussion we'll talk about how we went about doing this and what you can do to get similar results.
Biography:
Matt Engstrom has been with Eagan, Minnesota based West, a Thomson Reuters company for 14 years in a variety of technology roles. Matt's years of experience in software development and testing utilizing traditional waterfall techniques provided the basis for pioneering the use of agile methods to deliver a quality product. In his current role as Director, Quality Engineering Development, Matt is responsible for the design, development and implementation of quality services for new products developed utilizing the latest technologies.
