Object Oriented Project Management with UML

(Publisher John Wiley & Sons, Inc.) Author(s) Murray Cantor ISBN 0471253030 Publication Date 08 01 98 The program manager must bridge that gap and ensure that the development plan is both executable and serves the business need. There is often room for discussion. For example, the executives or customers might be willing to forgo some feature once they understand the cost and risk it brings to the project. It is your job to resolve these issues. To do this, you must understand both the...

Divide and Conquer

The way to defeat complexity is through the tried-and-true tactic of divide and conquer. You defeat code complexity by dividing a large system into a set of modules with smaller state spaces and easily understood transitions. This brings you back to encapsulation and modularity. In object-oriented technology, the modules are objects and subsystems. If you strive for and achieve a package design that is modular at the class and package levels, the state transitions can be easily followed. The...

Lifecycle Model Principles

The choice of a lifecycle model is driven by the economics of your situation. The fundamental goal of any project manager is to deliver the project in the most economical way possible, minimizing time and effort. Many of the early techniques of software management were developed in the 1970s, a time when coding was inefficient, and economics called for minimizing coding and compilation cycles. In such an environment, refraining from coding until the design was approved, or using your team to...

Project Management Aspects of the Waterfall Model

It is easy to understand why managers adopted the waterfall model. Teams complete the required activities in a natural order. By paying attention to the activities, defects are found early, when they are relatively inexpensive to fix. The goal is equally simple Complete the required activities. The model, too, is easy to plan and staff. You assign requirements analysis to system engineers who hand off requirements documents to the software architects. They in turn hand off specifications to the...

Schedule Planning

Both the master schedule and the macroschedule should be maintained in a project management tool as a single project file, which is created by entering the WBS into the tool and assigning start and end dates, or durations and dependencies. If you choose the latter, the tool will compute the dates for you. Next, add the program milestones then identify which items are part of the master schedule and which belong to the more detailed macroschedule. Tools such as Microsoft Project let you identify...

Work Breakdown Structure WBS

In Chapter 1, I pointed out that when faced with any large, complex system you should break it into manageable pieces. The Work Breakdown Structure WBS consists of the complete list of tasks and subtasks required to complete the program. The elements of a WBS are discrete tasks or work packages that can be separately planned and budgeted. Examples of WBS items might include writing the test plan or user interface development. Develop a WBS where most of the tasks are of three-months duration....

Monthly Status Report

On a monthly basis, the development lead or project manager assembles and presents a status report at the monthly program review. In addition, the next level of management in your organization conducts a monthly review of all of the programs in his or her organization. The report is designed to assess the overall status, progress, and stability of the development. The report serves two functions Early detection and assessment of program risks. An opportunity to communicate the risks early so...

Setting the Microschedule

It follows that you must coordinate the class method implementation so that the use cases become integrated. The ideal way to organize this phase s activity is to 1. Plan the order of use-case implementation. 2. Derive the order of class method implementation to meet the use-case implementation plan. 3. Sort out the dependencies and resource leveling of the class method implementation and schedule the implementation of the classes based on the effort and the dependencies. 4. Reset the use-case...