Showing posts with label interface. Show all posts
Showing posts with label interface. Show all posts

Thursday, October 2, 2008

Managing Communication Interfaces

One of the most important aspects of project planning is communication. As a project manager, you must define needed interactions between project teams and project support groups as part of the project planning process. To do this, you need to understand where communication occurs. Areas of communication, called interfaces, generally fall into one of three categories: organizational, technical, and interpersonal.

Organizational interfaces
An organizational interface is a communication interface among organizational units. Communication between organizational units is affected by the:
  • Individuals that make up organizational units - Good communication between individuals is essential to project success. Miscommunications and disagreements between individuals can cause delays in your project.
  • Overall unit goals - When units within an organization have similar goals, everyone can work together to meet those goals. When the goals of organizational units conflict with one another, each unit's effort works against the others.
  • Different managerial styles within each unit - Difference in managerial styles from department to department can cause confusion, frustration, and miscommunications.
  • Decisions made outside the immediate organization - Decisions made by governments, interest groups, and competitors can influence your project and must be communicated.
Technical interfaces
Technical interfaces are the formal and informal reporting relationships among different technical disciplines.

Technical interfaces occur within and between project phases. They can occur in products, facilities, and hardware, in other words, in anything that is non-people related.

The technical interface falls into two categories: physical and performance. The physical interface is between interconnecting parts of the system. The performance interface is between various functional or product subsystems. These categories contain both good interfaces and problems with interfaces.

For example, MercuryRising has an excellent technical support team that is familiar with the hardware and software within the various departments. Quick response time to computer problems ensures little disruption time on projects and makes meeting deadlines easier.

The office supplier for MercuryRising has software to let them know what and how much of a product is being used daily. This tells them exactly when and how much to deliver. Such precision aids project delivery.

Project managers can help to ensure project success by managing technical interfaces.

Interpersonal interfaces
The interpersonal interface deals with formal and informal reporting relationships among different individuals working on a project.

Differences in personality, skill level, and communication style can create issues as a project team begins to work together. Typically, as the number of people involved in a project increases, so does the potential for problems with communication. A project may involve:
  • different organizations
  • organizational departments (Accounting, R&D)
  • groups (special interest)
  • subgroups
  • individuals
To enable effective communication at the interpersonal interface, you must carefully plan your project reporting relationships and keep the communication lines open to accommodate everyone involved.

For your project to succeed, you must remove barriers to communication through interface management—a constant juggling of communication issues.

A good project plan outlines individual, technical and organizational responsibilities and authority. It enables you to simultaneously manage the three interfaces and maintain the flow of communication.

If you effectively use the inputs to organizational planning, you can avoid most conflicts. Your projects will run more smoothly, and your project will have the best chance for success.

Tuesday, July 3, 2007

The Design Phase of an IT Project

The purpose of the design phase of an IT project life cycle is to plan out a system that meets the requirements defined in the analysis phase. In the design phase, the project team defines the means of implementing the project solution—how the product will be created. To do this, the project team uses the inputs and tools to conduct the key activities, create the outputs, and meet the milestones for this phase.

The purpose of the design phase is to provide the project team with a means for assessing the quality of the solution before it has been implemented, when changes are still easy to make and are less costly. This phase includes the following elements.
  • The inputs required for this phase are the corporate standards, business process prototype, and requirements analysis.
  • Only standardized tools found in all offices, such as word processing software, spreadsheets, and presentation software, are used in the design phase.
  • The key activities for the design phase are to review the end user interface design, create the technical design, and perform the quality verification and validation.
  • The single output for the design phase is the design document.
  • The milestones for the design phase are the architecture assessment deliverable, design sign-off, and lifecycle assessment complete deliverable.
During the design phase, the project manager enlists the help of the designer, the technical architect, and a representative of the end users. The key activities that must be conducted during the design phase are listed below.

1. Review the end user interface design.
Before the project manager can conduct the first key activity, the designer uses the project's storyboards to create the end user interface in terms of appearance, layout, and interaction techniques as seen by the end users.

The PM evaluates the design to ensure that it meets the users' needs and the corporate standards. The PM then meets with the designer and explains what's wrong and what's missing from the proposed design. If the PM is not satisfied with the design, the designer applies the necessary corrections, and the PM reviews it again.

When a PM looks at a design, he or she compares it to the inputs listed below. This evaluation is important because the developer will not be able to properly test the completed product during the testing phase if the design doesn't meet these requirements. If testing can't be conducted properly, the product can't move into the rollout phase.
  • User needs. Does the design include each of the user requirements? Are each of the user requirements correctly incorporated into the design?
  • Corporate standards. Does the design include all the standards that specify products or technologies that the development team will use? Are the standards properly implemented in the design?
2. Create the technical design.
Although PMs do not conduct the last two key activities of the design phase, it is important that they understand each activity. The designer and technical architect conduct the technical design activity to decide how they will implement the project design. By using the requirements specifications input as a guide, they create a document that includes the sections listed below. The technical design is then given to the PM to serve as the blueprint for the project.
Framework. The framework is a design that can be reused on a software development project. For example, the text entry field used on a user interface framework can be reused in a database design.
  • Coding standards. Programmers have to follow these rules to ensure consistency in the programming code since usually more than one programmer will work on a project. A sample coding standard might read, "Do not use capital letters for file names when coding."
  • Task breakdown. Development is divided into tasks created separately and then integrated into a final product. Task breakdown makes it easier for a PM to assign work during the construction phase. For example, three tasks might be the user interface, the database, and the help feature.
  • Project timeline. A timeline for completion is estimated for each task required to complete the project. For example, it will take four days to create the user interface, three days for the database, and two and a half days for the help feature, for a total of nine and a half days.
3. Perform the quality verification and validation.
As in the technical design activity, the project manager does not actually have a part in conducting the final key activity of the design phase, except to receive a sign-off form. During quality verification and validation, end users and technical personnel verify and validate that the proposed design meets the user and quality requirements.
Upon completion of the review, an approval form is given to the project manager, indicating approval of the completed system design. This sign-off then becomes one of the milestones for the design phase.

Remember, it's easier and less costly to make changes in the design phase, before you implement the actual solution for the project. Take your time and design it right!