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...
Using the PackageLevel Analogy Method to Size the Simulator Project
As you approach the simulator project, you assess your overall situation. Fortunately, you work for a mature development organization, and your processes, procedures, and development and design tools are in place. You access the staff you need in-house, and so can depend on a level of competence, not only in software design and implementation, but also in the use of the tools. There is no need to train new employees. You will do your development in a combination of C and Java. Your architect...
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...