Home      Contact       Sponsors/Exhibitors       Download Brochure
2008 Tutorials

The following is a brief description of the half-day tutorials presented at this symposium on Monday, October 13, 2008. The morning tutorials will start at 8:00 AM sharp and the afternoon tutorials will start at 12:45 PM and finish at 4:30 PM. Registration begins at 7:15 AM. For more detailed information on each tutorial click on the tutorial title.

MORNING TUTORIALS:

Aligning Software Development Projects With Business Needs – A Simple & Effective Requirements Definition Methodology

Tarun Talwar, Mindspan Systems Inc

 

The number of software projects that fail due to poor requirements definition is staggering. The need for methodical requirements specification is underscored by a basic fact - if a project team does not do a good job of identifying what is needed, it will not be able to deliver the desired results no matter how skilled it is in the how part (the technical know-how). This tutorial will introduce a comprehensive and proven methodology to capture the business requirements and get them validated by the business users, which has evolved through years of experience and incorporates several best practices.

Making Process Improvement Work - A Concise Action Guide for Software Managers and Practitioners

Neil Potter, The Process Group

Process improvement too often reflects a significant disconnect between theory and practice. This workshop bridges the gap - offering a straightforward, systematic approach to planning, implementing, and monitoring a process improvement program. ??With examples based on our extensive experience, this workshop shows how to define goals that directly address the needs of your organization, use improvement models appropriately, and devise a pragmatic action plan. In addition, it reveals valuable strategies for deploying organizational change, and delineates essential metrics for tracking your progress. Class materials provide examples of an action plan, a risk management plan, and a mini-assessment process.

Rules of Engagement

Pat Ferdinandi, Strategic Business Decisions

Ever wonder why more than 36% percent of proprietary software fails? The answer is that defects and cost-overruns are a result of poorly defined requirements. If you calculated this percent of the project’s cost, how much could have been avoided if your staff were trained on what information needs to be captured and how to engage the business community in developing better requirements. This program concentrates on the real front-end of any project … talking with business personnel to get the information needed to define the results you want. Save time and money on your project but most important is to get the output your business needs in the time frame you need it.

Driving Software Process Improvement Through System Testing

Nathan Petschenik, STS Consulting

To achieve success in system testing, technical excellence is necessary but it’s not sufficient. Equally important are skills to influence project team behavior to prevent defects from reaching system test in the first place. Participants will learn leadership techniques that can increase productivity, improve software quality, and reduce costs This includes participating in a Role Awareness seminar that can help identify and break down barriers and impediments to software quality on your project. Participants will also learn how system test teams can use measurements to help project team members—both testers and developers—get better at their jobs

Agile Project Management

Chris Sims, Technical Management Institute

On a software project, uncertainty is certain. The customer will change their mind, a 'must have' feature will be discovered, deadlines will move, or an unexpected competitive threat will need to be countered. The agile approach to project management allows the team to easily adjust to these changing conditions in order to produce the most valuable software possible.

This workshop teaches the fundamentals of agile project management, and is recommended for everyone who will be involved in an agile project. We will explore the key roles, responsibilities, interactions, and processes that make a successful agile project happen.

AFTERNOON TUTORIALS:

The Recursive Nature of Requirements Development

Tim Kasse, Kasse Initiatives LLC

Collecting and understanding requirements is the necessary but not necessarily sufficient start of a successful project. Large projects involving systems and software components are required to collect and analyze requirements using a more incremental or recursive approach. The SEI’s CMMI-DEV v1.2 illustrates this point.

The Analyze and Validate Requirements specific goal addresses the necessary analysis to define, derive, and understand the requirements. This specific goal is intended to assist the specific practices in the first two specific goals. 

The processes associated with the Requirements Development process area and with the Technical Solution process area may interact recursively with one another. Analyses are used to understand, define, and select the requirements at all levels from competing alternatives. Analyses occur recursively at successively more detailed layers of a product’s architecture until sufficient detail is available to enable detailed design, acquisition, and testing of the product to proceed. 

PPQA Role in Analyzing & Evaluating Metrics Programs

Lori Montanari Gottshall, Software Management Solutions, Inc.

This tutorial reviews the skills that Software Quality Practitioners must have to objectively evaluate their organization's quality program. Specific measurements are needed to establish goals, track progress, prioritize efforts, and report to management. Measurements for both product and process quality will be examined. 

The attendees will be introduced to terminology and theory, lecture will include examples, and exercises will be worked to reinforce learning. A final section will focus on how the PPQA professional gains insight to overall organizational quality through defect analysis and defect removal effectiveness calculations. Ample time will be allowed for discussion of real life situations.

Effective Project Retrospectives and Intuitive Risk Management

F. Michael Dedolph, Computer Sciences Corporation

This is a hands-on tutorial, combining two group-oriented techniques into an integrated mechanism for improving future project performance. The session will teach people how to gather useful lessons learned by conducting an effective project retrospective. The lessons are transformed into learnings in the form of specific process improvements, issues, and risks related to future work. An introduction to intuitive risk management will help participants view risk differently, and will provide methods for sustaining and extending the initial risk list over time. Used collectively, these methods will energize risk management, and complement more formal risk techniques.

Software Cost Estimating Fundamentals

Joseph Ingemi, PRICE Systems, L.L.C.

Many software development projects are delivered late and over budget. These projects often do not meet the original requirements, have an unacceptable number of defects, and may not even function properly. This three-day course is designed to show participants how to estimate the costs and schedules of software development projects in order to avoid large overruns.

This course presents practical techniques and tools to estimate, plan, and complete high quality projects that are on budget and schedule.  

Combining RUP and Agile in software development

Michael Kaufman, Advanced Business Automation & Palani Enterprises

Participants will learn how to execute project plans based on RUP or Agile methodologies. They will know what common to the both and what differentiates them apart. There will be example of when and how both methodologies can be combined within a project plan and what it can accomplish.  

 

______________________________
SM SEI, SCAMPI, SCAMPI Lead Assessor, and SCAMPI Lead Appraiser are service marks of Carnegie Mellon University.
®CMMI and CMM are registered in the US Patent and Trademark office by Carnegie Mellon University.