All tutorials count for credit towards CSTP (Certified Software Test Professional) re-certification

All tutorials are from 8:30 - 4:30 PM

Monday, November 12, 2007

M1 Improving Performance through Standards and Processes Barbara Ainsworth
M2 Low Overhead Software Process Improvement Methods Robin Goldsmith
M3 Planning a Successful SPI Project Alan Koch, PMP
M4 Software Quality Assurance Methods and Techniques Dr. Magdy Hanna
M6 Managing Outsource/Offshore Projects Jerry Durant

M1: Improving Performance through Standards and Processes 
Barbara Ainsworth

Introduction:

All of the international standards for IT excellence have one area in common: the full definition of all critical processes and the standards that govern them. ISO 9000, Six Sigma, SPICE and the Capability Maturity Model all begin with process and standards definitions. These fundamentals are well understood and have well-tested practices that any IT department can adopt, no matter the economic sector, size or country. Learn the basic steps to establish the Mission Critical Processes and their standards, procedures and guidelines. Learn a simple model to develop and deploy processes and standards. Learn to measure processes to make sure they are meeting standards. Learn to manage the processes and standards day-to-day and optimize them based on analyzing their efficiency and effectiveness. Learn to leverage your improved results.

Learning Objectives:

This tutorial focuses on the procedures for developing and deploying IT standards successfully. As a result of your participation you will be able to:

  • Understand the relationship of IT standards to international standards
  • Define Mission Critical Processes with internal and external customers
  • Use the New Process Development Model to develop and deploy processes and standards, procedures and guidelines
  • Measure standards usage, effectiveness and efficiency
  • Manage standards usage day-to-day
  • Optimize standards
  • Plan and deploy a standards program

Barbara Ainsworth, PMP, CSQA, CSTE, is Managing Member and Principal Consultant for Process Plus International LLC; a female owned minority company that focuses on IT client process management and improvement utilizing models as foundational frameworks. She serves as a consultant to USA and global IT groups in manufacturing, financial services, insurance, and service organizations to help them meet their organization's business objectives by advancing their IT capabilities. She consults with business and IT senior management for strategic direction, and then works cross functionally, at every level, to achieve the desired results.


Barbara
Ainsworth

M2: Low Overhead Software Process Improvement Methods 
Robin Goldsmith

Introduction:

Software process improvement doesn't have to be synonymous with expensive formalized approaches, such as the Software Engineering Institute's Capability Maturity Model (SEI CMM). This interactive seminar workshop describes it along with seven alternative approaches that can provide significant software productivity and quality improvements without extensive bureaucracy or organization-wide cultural change. Exercises enhance learning by allowing participants to practice applying practical techniques to realistic examples.

Course Outline:

  • “REAL” VS. “PRESUMED” PROCESSES
    • Common emphasis on good practices
    • What a process is and why we care
    • Relation between process and results
    • The only way to change your results
    • Why most process improvements fail
    • Distinguishing “real” from “presumed”
    • When the real process is not recognized
    • Defined and documented processes
    • Silos, stovepipes, and smokestacks
    • Measuring a process to its full end result
    • Real vs. presumed testing process
    • Illusion of speeding up the coding
  • HIGH-OVERHEAD APPROACHES
    • Capability Maturity Models
    • Benefits and advantages
    • Stepwise vs. continuous models
    • Proliferations, e.g., Testing Maturity
    • Activity vs. results
    • Empirical analysis of actual improvement
    • Piece of paper mentality
    • Process imposition vs. process improvement
    • Role of management styles and practices
    • Six Sigma as applied to software
    • Strengths and weaknesses
    • Identifying appropriate measures
    • Religious approaches vs. real improvement
    • Management gaps
  • IMPROVING THE “REAL” PROCESS
    • Key perspective to identify the real process
    • Turning inadequacies into virtues
    • How to measure a process
    • Multivariate process mapping
    • Analyzing handoffs and bottlenecks
    • Evaluating value added
    • Streamlining and eliminating error sources
    • Non-operational “soft” components
    • Emperor's new clothes risk
    • Measuring and improving people processes
  • POWERFUL IMPROVEMENT PRACTICES
    • Making good practices work
    • “They won't let us use this training”
    • Measurement and metrics
    • Fallacies of on-time and in-budget
    • Avoiding main causes of resistance
    • Implementing effective metrics baselines
    • Reviews and inspections
    • Form vs. substance
    • Meaningful early involvement
    • Proactive Testing™
    • Letting testing drive development
    • Scaling risk
    • REAL, business requirements
    • System/software requirements
    • Use cases
    • Problem Pyramid™ tool

Learning Objectives:

  • Recognizing real processes and distinguishing them from presumed processes
  • Avoiding common traps that lead to making only illusory improvements
  • Ways to analyze and measure processes to identify meaningful improvements
  • 7 specific methods for quickly and economically improving software processes

Biography:

Robin Goldsmith 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".



Robin Goldsmith

M3: Planning a successful SPI project 
Alan Koch, PMP

Introduction:

Planning Software Process Improvement (SPI) is just like planning anything else, right? Yes … and no.

The basics of project planning apply just as much to SPI as they do to software development (or putting on a play, or building a skyscraper, or …), but each type of project presents its own special challenges and has its specific risk areas. Those special challenges and risks are what make SPI planning unique.

This one-day tutorial will step through a mature project planning process (ala CMMI/PMBOK) and explore how those mature practices apply specifically to SPI projects. During the exercises, you will apply them to your specific project (a case study project will be provided for students who need one). You will leave this tutorial with a good start on an excellent SPI plan, and the tools and techniques you will need to do good SPI planning from now on.

Outline:

  • Introducing SPI Planning
    • SPI is a project (usually, a group of related projects)
    • Challenges and risks that are specific to SPI projects
    • Overview of the Project Planning process
    • Exercise : Identify your SPI project (or Read the Case Study)
  • Define SPI Project Scope & Process
    • Project Requirements
    • Project Goals & Objectives
    • Project Scope
    • Project Process
    • Exercise : Document SPI project Scope and define SPI Process
  • Identify SPI Deliverables and Artifacts
    • Project deliverables
    • Project internal artifacts
    • Deliverable/Artifact acceptance criteria
    • Exercise : Identify SPI project deliverables and artifacts
  • Estimate Sizes of SPI Deliverables and Artifacts
    • Size as a driver of budget and schedule
    • Choosing size measures
    • Estimating sizes
    • Exercise : Estimate sizes of SPI project deliverables and artifacts
  • Identify SPI Resource Needs
    • Types of resources (People, Facilities, Tools)
    • Resource needs during process definition/change
    • Resource needs during process testing/pilot usage
    • Resource needs during process roll-out
    • Acquiring needed resources
    • Exercise : Identify SPI project resource needs
  • Negotiate Project Constraints
    • List all specific project activities
    • Research historical SPI project productivity
    • Compute budget and schedule
    • Negotiate for project success
    • Exercise : Brainstorm historical data sources and negotiation pitfalls
  • Manage SPI Risks
    • Identify SPI project risks
    • Risk mitigation opportunities
    • SPI contingency options
    • Exercise : Develop an SPI Risk Management Plan
  • Define Project Management Practices
    • Develop an SPI metrics plan
    • Define status checking procedures
    • Develop an Stakeholder Involvement plan
    • Exercise : Define your SPI project management practices
  • Tutorial wrap-up
    • Review SPI project planning highlights
    • Exercise : Define your SPI planning action plan

Learning Objectives:

  • Learn to manage SPI as a project
  • Understand the risks and issues that are unique to SPI projects
  • Identify how those risks and issues affect your current project
  • Begin to take action to address those risks and issues

Biography:

Alan S. Koch, PMP is a consultant, trainer, speaker and writer on effective Project Management methods. For over seven years, he has been President of ASK Process, Inc., a training and consulting company that helps companies to improve the return on their software investment by focusing on the quality of both their software products and the processes they use to development them.

Mr. Koch's 30+ years in software development include:

  • 14 years designing, developing and maintaining software
  • 5 years in Quality Assurance (including establishing & managing a QA department)
  • 10+ years in Software Process Improvement
  • 10+ years in Management.

Mr. Koch holds the ITIL Foundations Certification and has trained many other individuals who have successfully achieved their ITIL Foundations Certifications.


Alan Koch

M4: Software Quality Assurance Methods and Techniques  
Dr. Magdy Hanna

Introduction:

Many software organizations try to achieve software quality by focusing on testing activities that are normally done after the product has been put together by the development team. Every project manager and every test managers know that this is not a very effective way to assure the quality of the application. The reason is that when the testers execute their tests against the application and find bugs, those bug reports go back to the development team, which in turn tries to fix problems under time pressure. And you know the rest of the story: more bugs get created and the cycle continues. More bugs, more bug reports and more bugs. For many years, experts and pioneers in software quality have suggested that software organizations focus more on the front-end of the software lifecycle to build quality into software rather than trying to test for quality at the end. This course covers all quality assurance methods and techniques that aim at achieving this goal of building quality into the software. The course is a must for every project manager, QA manager and test manger.

Outline:

  • Quality Assurance Vs Quality Control
  • Defining processes
  • Implementing Quality Assurance
  • Developing effective standards
  • Inspections and review of artifacts other than code
  • Development and Test lifecycles and methodologies
  • QA concepts, methods and approaches
  • Prominent quality assurance models such as CMM/CMMI, Six Sigma, IEEE standards, TQM, and ISO
  • ROI justification for Quality Assurance
  • Quality Assurance according to W. Edwards Deming
  • Quality Assurance for modern development methodologies: RAD, Agile and eXtreme
  • Independent Verification and Validation

Learning Objectives:

Course participants will learn:

  • The difference between quality assurance and quality control
  • How to effectively plan, execute, and verify plans to deliver quality software
  • How to start an effort to implement process improvement even in small projects
  • How to select between different quality assurance methods to get the most ROI
  • How to implement a cost effective inspection process that works with all types of project and all types of artifacts

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, (www.icspi.com).

Dr. Hanna Also served as Editor-in-Chief of the Journal of Software Test Professionals, a publication of the International Institute for Software Testing, now the Bug Free Zone (www.iist.org/bugfreezone)

As a consultant, Dr. Hanna has helped organizations define and improve their software processes using disciplined software engineering approaches.

As a professor of software Engineering at the University of St. Thomas , he taught graduate courses on several software engineering topics with emphasis on practical software quality techniques.

Dr. Hanna developed new approaches and methods in software engineering including the Software Quality Engineering Methodology (SQEngineer), the Unified Data Model (UDM), and the Data-Driven Object Model (DOM).

Dr. Hanna holds a Ph.D. and a Masters degree in Computer and Information Sciences form the University of Minnesota , a Masters in Operations Research from Cairo University , and B. Sc. in Petroleum Engineering from Suez Canal University , Egypt.


Dr. Magdy Hanna

M5: Gathering Requirements via Business Process Modeling 
Clyneice Chaney

Introduction:

Today's market expects information technology organizations to create systems that meet and support a company's the mission critical business drivers for success. How well a system meets its intended business expectations is key to its success. There is a plethora of tools available that monitors application performance tied to business needs and the impact of its failure on the business. If business drivers are central to a system ‘s performance, then an approach to gathering requirements that encompasses business processes analysis provide benefits to IT organizations. This course introduces Business Area Analysis techniques as a part of the Project scooping and requirements gathering phases. It is based upon using the facilitated session as the means of capturing project information and requirements. Specific tools and techniques that are covered include:

  • Utilizing context diagrams
  • Utilizing actor catalogs
  • Utilizing information flow diagrams
  • Utilizing use case catalogs
  • Estimating requirements gathering utilizing these techniques

Learning Objectives:

  • Understand the role of business area analysis as a technique for requirements gathering
  • Understand how to facilitate a project initialization session utilizing context diagram
  • Understand how to estimate the requirements phase utilizing context diagrams
  • Understand how to plan and conduct Business Area Analysis (BAA) sessions for requirements gathering
  • Understand how to develop information flow diagrams
  • Understand how to estimate analysis and design phase from output of an BAA session

Outline:

  • Business Process & Requirements Overview
  • Project Phase I Facilitation
    • Capturing project context & scope
    • Estimating requirements
  • Project Phase II Elaboration
    • Planning BAA Sessions
    • Conducting BAA Sessions
    • Documenting the Session

Biography:

Clyneice Chaney, Corporate Quality Manager with Project Performance Corporation brings over 20 years of testing, quality assurance and process improvement experience. Clyneice holds certifications from American Society for Quality as a Certified Quality Manager, Quality Assurance Institute's Certified Quality Analyst, and Project Management Institute's Professional Project Manager. She has served on the Board of Examiners for Virginia and Georgia 's State Quality Awards.

Focusing on process improvement and procedure development in the software testing and quality assurance areas, Clyneice has successfully lead process improvement, methodology development, and reengineering projects for organizations wishing to improve their software development, testing processes, and tool implementation.

Clyneice is currently an instructor for the International Institute for Software Testing and has presented technical papers at the Software Engineering Institute: SEPG Conference, American Society for Quality: Quality Manager's conference, Quality Assurance Institute International Testing conference and STAR East Testing and the Quality Assurance conference.


Clyneice Chaney

M6: Managing Outsource/Offshore Projects 
Jerry Durant

Introduction:

One would think that managing a project, whether done locally or offshore, would follow a common framework. Unfortunately, when we turn over construction to others we give up control. All is not lost however since it affords an opportunity to shift attention to critical guidance components and outcome control. Still we must be prepared (and trained) in thinking differently about projects and how they demand a shift in thinking. This course orients participants in this change in focus and how true value contribution and control can be sustained, with successful outcomes.

Outline:

  • Project Component Ownership
    • Client Side Components
    • Outsourcer Provide Components
    • Joint Components
      • Collaboratively Constructed & Owned
  • Project Synchronization – Establishing Balance
    • Client Project Management
    • Merging Your PM with Outsource PM
    • Synchronization of Time & Delivery
    • Defining Delivery
  • Project Metrics
    • Establishing Goals
    • Agreeing Upon Measurement Sources
    • Measurement Reconciliation and Reporting
    • Using Metrics to Support PM
  • Project Communications - Construction/V&V/Delivery Periods
    • Understanding the Client Role
    • Define & Convey Expectations (w/Detail)
    • Ask for What You Want
    • Focus on “What” not “How” (but be inquisitive)
    • Jointly Engineered Communication Model
    • Mistakes in Communications
  • Pre- and Post-Delivery Outsourcer Tasks
    • Project Management
    • Artifact & Component Construction/Qualification/Delivery
    • Application of Professional Expertise
    • Insure Client Input Adequacy
  • Pre- and Post-Delivery Client Tasks
    • Qualified Specifications
    • Inquiry & Dialog Availability
    • Qualification of Received Artifacts & Components
    • Timely and Complete Feedback
  • Harmony through Touchbacks
    • Communication Framework Value
    • Healthy Boundaries
    • Coordination of Effort
    • Real-time Visibility vs. Status Reporting
    • Asking the Question…
  • Recognizing Cultural & Work Differences
    • Paradigm Variances
    • How Much Do You Mandate
    • Impact on End Results
    • Utilizing Differences to Enjoy the Project Experience
  • Managing for Success
    • Meeting Client (your) Obligations
    • Measuring Progress
    • Maintaining Healthy Communications
    • Managing Delivery & Implementation

Biography:

Jerry E. Durant has been involved in Information Technology for over 30 years. During this time he has worked for and represented some of the leading companies throughout the world. These include AT&T, Bell Laboratories, SAS Data Denmark, Ericsson Telecom, Honk Kong Telephone, British Telecom, EG&G, British Telecom, World Bank, AETNA Insurance, Bank of America, Rockwell Automation, Huawei Technologies, Microsoft, Boeing, Puritan Bennett, Eli Lilly, Glaxo, Unisys and Hewlett-Packard to name a few.

Certellus LLC is involved in delivery of software verification & validation, Outsource/Offshore Facilitation, ERP Risk Mitigation, and Security services. In these areas Certellus brings to bear over 45 specialized expert practioners, and collaborative offshore providers in China , Egypt and the Ukraine . Since 1988 Certellus LLC has provided engagement facilitation and advisory services for such leading companies as Shell Oil & Exploration, BP, Lilly, Goodyear Tire and Kübler. Prior to forming Certellus LLC (Certifiable Technologies & OutsourceIT!Solutions Ltd.) , Jerry was a senior member of technical staff (Division Director) - Software V&V for AT&T Information Systems and a principal at Software Quality Engineering.

Jerry authored The Testing Tools Reference Guide© published by SingleSource, and authored the first training program on the subject entitled “Test Automation Workshop™” (offered through Software Quality Engineering). He has taught throughout the World in both public and private settings to over 2000 technical professional. Practical, applicable and effective are words that participants have used to characterize their training experience. Jerry has been intimately involved in the use and validation of commercial data repositories and has helped companies extend the practical application of it's use. This has involved the sharing of data from such sources as SAP, PeopleSoft, LotusNotes, SPSS & SAS statistical systems, and utilizing a wide array of commercial database packages (eg. SQL, Oracle, DB2, IMS, and Adabase).

Jerry has a M.S. in Computer Science from NH College Graduate School, B.S. in Management from NH College and an A.S. in Accounting from Hesser College . In addition, he has been recognized in Who's Who in Technology and Who's Who in Global Enterprise for his many contributions in the Information Technology sector.


Jerry Durant

Thursday Friday Program at a Glance