Application Lifecycle Management

Conference Presentations

Mentors, Models, and the Making of Managers: Special Panel Discussion

Each of us has a story about how we came to be managers in software organizations. Many of us became managers because we were good developers. Some of us studied management in school. A few of us were groomed and mentored by the companies we work for, and some were tapped for management because we were the only warm body available. But now that we're here, what does it take to become an effective manager? Is being mentored and developed as a manager considered a luxury? Join this interactive panel and discuss the real-life issues and challenges of developing ourselves-and others-as software managers.
Moderator: Esther Derby ( Esther Derby Associates, Inc.)
Read My Lips: No New Models!

These days, it seems everyone who wants to make a mark in the software world feels the need to invent a new model or methodology. While such models provide useful frameworks for structuring our thinking and practices, enough already! Karl Wiegers contends we don't need any more new and improved models for software engineering. Rather, we need to encourage a majority of developers to consistently and effectively apply the practices that have already been shown to work.
Karl Wiegers, Process Impact
Thinking About People, Process, and Product: A Principle that Works at Work

All projects involve the three P's: people, process, and product. People includes everyone who influences the project. Process is the steps taken to produce and maintain software. Product is the final outcome of the project. To keep these three in harmony, you must observe who is trying to do what to deliver what. Usually, two of the three P's are mandated, and the third one is chosen appropriately. Although this is common sense, it is not common practice. Dwayne Phillips discusses the issues and challenges that affect us all on every project. Learn about the ideas and questions to consider to help you work through these issues.
Dwayne Phillips, U.S. Department of Defense
eXtreme Programming Meets Measurement

With the Internet explosion creating new "e-somethings" daily, and society embracing X-anything, it should come as no surprise that eXtreme Programming is the latest concept to hit IT. Forget the visions of IT managers projecting themselves off a cliff with bungee cords and a laptop-eXtreme Programming is more mainstream than renegade, offering a mixture of old and new, tried and true all bundled into one. Learn what eXtreme Programming is all about and how it differs from other development methodologies. Discover what can and should be measured in an eXtreme Programming environment and how to fit X-Measures in with a regular measurement program.
Carol Dekkers, Quality Plus Technologies, Inc.
System Architectures-An International Viewpoint

The software engineering industry has invented a wide variety of architectures and technologies for building applications, yet all of these architectures have some common features and issues. One such common issue is internationalization. No matter how you build your application, it will more than likely be viewed and used by people from different cultures, nationalities, and backgrounds. This presentation gives you a lighthearted tour of the common application architectures. Examine how some of these architectures make internationalization and globalization easier, harder, or just plain peculiar. If you have always wondered what an n-tier architecture is or how it plays internationally, thie session is for you!
Benson Margulies, Basis Technology
Extreme Programming and CMM

This presentation explains the Capability Maturity Model and Extreme Programming, compares the two, and shows how they can be compatible.
Mark Paulk, Software Engineering Institute
Managing Concurrent Software Releases in Development and Test

There is an ever-growing need to provide complex software products to customers on a short development schedule. Additionally, the customers need to be able to count on release dates for planning purposes. Instead of investing in an entirely new tool set that solves the configuration management issues associated with supporting concurrent development and support, existing tools can be used. This paper focuses on how to adapt and in some cases enhance an existing set of well-known tools to enable Lucent to excel in the market place. To this end, this project chose to implement the Fixed Interval Feature Delivery (FIFD) model of software development.
David Shinberg, Lucent Technologies
A Disciplined Approach to High Velocity Software Development

When faced with the challenge of shortening delivery cycles, the old economy manufacturing companies utilized disciplined quality techniques to reduce scrap and rework and improve productivity. Software developers in the new economy face a similar challenge to accelerate development to meet critical time-to-market business goals brought about by the Internet. Unfortunately, many are abandoning disciplined methods in lieu of a risky "hack and test" approach with potential disastrous consequences for customers and developers. Learn of one company's transformation from ad hoc development to a disciplined and quantitatively managed enterprise. Discover why such a transformation is absolutely essential for high velocity software development.
Girish Seshagiri, Advanced Information Services, Inc.

Pages

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.