|
|
Software Quality Metrics as Agents for Change What is the purpose of software quality metrics and what values do they provide to the organization? What metrics not only report on and but also help drive changes and improvements in software quality? Based on his work at EMC, Jim Bampos discusses the metrics they use to predict software quality at ship time and the key quality questions to ask customers after ship. Find out what it takes to roll out a successful metrics program and the results you can expect, including quality ownership across the organization and improved customer satisfaction. Watch out for unintended consequences and wrong behavior that can result from a metrics program. Learn from Jim the key steps to ensure that your organization adopts the metrics program and that people are held accountable for the data and results.
|
James Bampos, EMC Corporation
|
|
|
Leading Cultural Change When Implementing Process Improvements When we are part of an improvement initiative such as CMMI®, Six Sigma, or Agile practices, we often focus on the technical aspects and pay little attention to the people and cultural issues. Major change produces a significant disruption of expectations whether the change is perceived as positive or negative. So, you need a defined process to help ensure that your improvement initiative achieves its goals. Jennifer Bonine presents the Organizational Change Management (OCM) process to help you manage the human aspects of implementing major, complex changes. She describes eight human risk factors that can sabotage process improvement programs. Learn from Jennifer how OCM can help you deal with people’s reactions to change and provide you with a change implementation architecture.
|
Jennifer Bonine, Express Scripts
|
|
|
Lean Software Contracts Agile development is great, but it cannot possibly be for you because your software development is done under a contract-outsourced or under an internal service agreement. Right? Wrong! Similar to the way automobile manufacturers have embraced lean manufacturing, you can escape the deadly waterfall development process even in contracted development environments. Lean manufacturing companies have learned over the past twenty years that trust with suppliers lies in specific actions and expectations, not in interpersonal relationships. They understand the "game" of outsourced contracting and know how to structure relationships and write contracts so that both sides are motivated to contribute to the common good. Join Mary Poppendieck, an expert in lean software development, to explore ways to change the contracting game in software development for the better.
|
Mary Poppendieck, Poppendieck LLC
|
|
|
Describing Software Requirements with User Stories All projects start with needs or requirements. How those requirements are documented and expressed has a tremendous affect on the rest of the project. The technique of expressing requirements as "user stories" is one of the most broadly applicable techniques introduced by eXtreme Programming (XP). However, user stories are a valuable approach on all time-constrained projects, not just those using XP. Although user stories originated in the Agile processes, they are useful even if you are not planning to employ Agile development. In this session, Mike Cohn will help you identify and write good user stories and understand the six attributes of all good stories. Explore how user role modeling can help when gathering the initial stories for a project.
|
Mike Cohn, Mountain Goat Software
|
|
|
Agile Software Development: The Home of 31 Flavors You've heard of eXtreme Programming (XP) and perhaps Scrum. How about Crystal Clear, Adaptive Software Development, Dynamic Systems Development Method, Rational Unified Process for Agile Development, and Feature Driven Development? These are some of the many variations of Agile development methods. Join Jeff McKenna as he explores the many flavors of Agile development methods and explains the similarities and differences. Find out what aspects of Agile development can help your organization’s development team in its particular environment. If you are considering Agile development and need to decide in which direction to go, this session is for you. Although a one-hour session cannot provide all the information you will need, you can explore what is common-the philosophy, the values, the characteristics-and what is different-the methods, the coverage, the costs-about different Agile approaches.
|
Jeff McKenna, Agile Action
|
|
|
Software Factories: Hype or Hope for Real Advancement? The new concept of Software Factories, as proposed by Microsoft, promises to elevate software development to the next level. Siemens is working with Microsoft to apply these approaches with the goal of improving product maintenance, quality, and time to market. Gunther Lenz explains the common elements and, more importantly, the differences between the Software Factories model and Model Driven Architecture (MDA), as proposed by the Object Management Group (OMG). Learn how UML 2.0, Domain Specific Languages, platform independence, product line development, and synchronization between models can all enter into the development process. Take away an in-depth understanding of the concept of Software Factories while leaning differences between Software Factories and MDAs.
|
Gunther Lenz, Siemens Corporate Research, Inc.
|
|
|
Model Driven Architecture (MDA) - What's in it for Developers and Testers? According to the Object Management Group (OMG), the benefits of Model Driven Architecture (MDA) are significant to businesses and developers alike: reduced overall product life costs, faster development, better application quality, rapid deployment of new technology, and a higher ROI on new technology. In short, the hype is that MDA enables system integration strategies that are better, faster, and cheaper. However, the MDA approach represents a fundamental change in the way software is developed, and it revolutionizes how you allocate test resources and how you create system tests. Timothy Korson outlines the MDA process and then suggests ways to change quality assurance activities to mesh with the MDA development style. Take away a realistic view of the current state of MDA practices compared to the MDA promise and vision, offered by the OMG.
|
Timothy Korson, QualSys Solutions
|
|
|
Agile and Adaptive Project Management - The Declaration of Interdependence Whereas the Agile Software Development Manifesto is a short and sweet list of principles for developers, the Declaration of Interdependence for Agile Project Management is more of a mouthful. The Declaration of Interdependence was written to provide concrete guidance for software projects and projects in general with applicability to general management. In constructing it, a dozen senior consultants, designers, and managers-project, product, and line-validated that it covered their individual core operating frameworks. In this talk, noted software designer, manager, and methodologist Alistair Cockburn, a co-author of both documents, unravels the six rules of operation in the Declaration of Interdependence. In the Declaration, project managers agree to increase ROI, deliver reliable results, expect uncertainty, unleash creativity and innovation, boost performance, and improve effectiveness.
|
Alistair Cockburn, Humans and Technology, Inc.
|
|
|
Controlling Performance Testing in an Uncontrolled World Think about it ... You are responsible for performance testing a system containing over 5 billion searchable documents to an active user base of 2.6 million users, and you are expected to deliver notification of sub-second changes in release response and certification of extremely high reliability and availability. Your n-tier architecture consists of numerous mainframes and large-scale UNIX
servers as well as Intel processor-based servers. The test environment architecture is distributed across large numbers of servers performing shared functions for a variety of products competing for test time and resources during aggressive release cycles. Because it is impractical and too costly to totally isolate systems at this scale, capacity and performance test engineers produce high quality
|
Jim Robinson, LexisNexis
|
|
|
Making Test Data More Agile Flexible, reusable, and restorable test data for both the unit and system level is an absolute necessity for testers working on Agile development projects. For teams following a more traditional development process, Agile approaches for handling test data can enhance testing efforts as well. Discussing Agile testing approaches, such the ObjectMother pattern, Peter Schuh explains how testers design tests and test frameworks to survive the ever-changing data structures found in Agile projects. Learn how an Agile process allows testers to get much more mileage out of test data sets during and after the initial development project. Leave with a set of practices and techniques to apply directly to Agile development projects or modify for their current development environment.
- The many dimensions of application test data
- Produce and maintain better tests and test data with Agile approaches
|
Peter Schuh, Peter Schuh
|
