Teamwork Among Stakeholders

Many aspects of the classic development process cause stakeholder relationships to degenerate into mutual distrust, making it difficult to balance requirements, product features, and plans. A more iterative process, with more-effective working relationships

Artifacts

Software

Vision

Document

JeT^

Release Specifications

Figure 15-3. Organization of software components resulting from a modern process between stakeholders, allows trade-offs to be based on a more objective understanding by everyone. This process requires that customers, users, and monitors have both applications and software expertise, remain focused on the delivery of a usable system (rather than on blindly enforcing standards and contract terms), and be willing to allow the contractor to make a profit with good performance. It also requires a development organization that is focused on achieving customer satisfaction and high product quality in a profitable manner.

The-transition from the exchange of mostly paper artifacts to demonstration of intermediate results is one of the crucial mechanisms for promoting teamwork among stakeholders. Major milestones provide tangible results and feedback from a usage point of view. As Table 15-2 shows, designs are now guilty until proven innocent: The project does not move forward until the objectives of the demonstration have been achieved. This prerequisite does not preclude the renegotiation of objectives once the demonstration and major milestone results permit further understanding of the tradeoffs inherent in the requirements, design, plans, and technology.

In Table 15-2, the apparent results may still have a negative connotation. A modern iterative process that focuses on demonstrable results (rather than just briefings and paper) requires all stakeholders to be educated in the important distinction between apparently negative results and evidence of real progress. For example, a design flaw discovered early, when the cost to resolve it is tenable, can often be viewed as positive progress rather than as a major issue.

Software Architecture

Requirements Set

CAPABILITY CAPABILITY

CAPABILITY Fx Fy Fz

MECHANISMS MECHANISMS MECHANISMS

MECHANISMS MECHANISMS MECHANISMS

Example Modern Connottions

JeT^

Release Specifications

Figure 15-3. Organization of software components resulting from a modern process

Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook


Post a comment