|
|
Requirements-Based Testing: An Overview In this article, the author discusses how to deliver more function, in less time, and with fewer resources while maintaining a high level of quality. He details how poorly written requirements can lead to major system errors. This paper also explains why good requirements are a critical part of any successful project.
|
Gary Mogyorodi, BIT, Inc.
|
|
|
IS and IT Benchmarking: Current Status Are you having trouble making a business case for benchmarking at your organization? Mark Czarnecki delivers his benchmarking expertise in a presentation designed to help participants impact their corporate culture as well as their benchmarking abilities. He reviews the current status of information systems and technology benchmarking, and he explains current benchmarking theory. The presentation also covers generalized database sources for benchmarking.
|
Mark Czarnecki, The Benchmarking Network, Inc.
|
|
|
Process Improvement in Large Organizations: Walking the Maze Every problem-solving activity in an organization requires some learning. Both the stakeholders and the
facilitators of the organization need to learn as they go through change. This paper describes our first
experiences with facilitating process improvement and problem solving by focusing on congruence, building trust
relationships, systems thinking and lots of "letting go."
|
Nynke Fokma, Moebius Consultancy and Erwin van der Bij, Lucent Technologies
|
|
|
Warp 6, Mr. Sulu: The Future of Software Development As a manager, you have many readings which help you monitor your course. Choosing a direction is a different matter. Like the crew of any Star Trek episode, you may have to make a decision based on the unknown. The best choice may not be based on what you know-but what is possible. For years we have built software in roughly the same way. Becky Winant discusses an emerging new discipline sitting on the horizon-complete with higher-level communication tools, practical knowledge capture, and advanced simulation software-that is poised and ready to change the face of software development as we know it.
|
Becky Winant, Esprit Systems Consulting, Inc.
|
|
|
Gaps, Traps, and Overlaps: Communication Flaws and How to Fix Them In some organizations, communication flaws are rampant and muddled messages are the norm. Success in software efforts is often hindered by communication that is incomprehensible, ambiguous, misdirected, ill-timed--or lacking when it is most needed. The result? Rocky relationships, topsy-turvy teamwork, precarious projects, and crazed customers. The situation is not hopeless, though. In fact, making changes is surprisingly easy. In a presentation that is both serious and light-hearted, Naomi Karten shares ideas, experiences, and advice to help you detect, correct, and prevent some of the most common communication snafus.
|
Naomi Karten, Karten Associates
|
|
|
The Story Software Defects Tell about Project Management We often evaluate and design software processes and activities as if putting them on lists and schedules will automatically make them happen. Yet software development also includes complex human interactions that must be planned and managed in order to gain best results, or to even survive. Drawing upon over one hundred candid engineers' comments from twenty root-cause analysis brainstorming sessions of frequently occurring defects, Bob Grady reveals fascinating insights into project management backgrounds, methods, training, and weaknesses. Into these insights, he weaves the use of personality preferences with project management methods to help you avoid common pitfalls in ways that engineers themselves prefer.
|
Robert Grady, Hewlett-Packard Co., Retired
|
|
|
Successful Projects-10 Keys to a Proper Beginning One of the primary keys to project success is orchestrating a proper beginning. In order to do this effectively, you must define the project mission, vision, and reason for being; get a handle on requirements; take the time to load the team properly; do the prerequisite work in gaining focus and clarity; and decide on the development methods and strategies. In this presentation, learn the five keys to forming your team and the five keys to successfully starting a project.
|
Robert Galen, Network Appliance, Inc.
|
|
|
Software Requirements: When They Think They Know What I Want… and They Don't Pat Medvick presents tales of successful and unsuccessful attempts at gathering requirements from scientists-highlighting the inherent problems and possible solutions. Learn how to gather requirements from multi-site domain experts. Discover ways to develop a flexible software design that permits requirements gathering throughout software development.
|
Pat Medvick, Pacific Northwest National Laboratory
|
