Problems with software projects

One way of deciding what ought to be covered in 'software project management' is to consider what problems need to be addressed. Traditionally, management has been seen as the preserve of a distinct class within the organization. As technology has made the tasks undertaken by an organization moa* sophisticated, many management tasks seem to have become dispersed throughout the organization there are management systems rather than managers. Nevertheless, the successful project will normally have...

The scheduling sequence

(ioing from an ideal activity plan to a costcd schedule can be represented as a sequence of steps, rather like the classic waterfall life-cycle model. In the ideal world, we would start with the activity plan and use this as the basis for our risk assessment. The activity plan and risk assessment would provide the basis for our resource allocation and schedule from which we would produce cost schedules. In practice, as we have seen by looking at Amanda's project, successful resource allocation...

Further exercises

Take a look at Amanda's project schedule shown in Figure 8.7. Identify those activities scheduled to last more than three weeks and describe how she might monitor progress on each of them on a fortnightly or weekly basis. 2. Amanda's Ciantt chart at the end of week 17 (Figure 9.5) indicates that two activities are running late. What effect might this have on the rest of the project How might Amanda mitigate the effects of this delay 3. Table 9.2 illustrates Amanda's earned value calculations...

Activities covered by software project management

Software Project Activities Covered

A software project is concerned not only with the actual writing of software. In fact, where a software application is bought in 'off-the-shelf, there might be no software writing as such. This is still fundamentally a software project because so many of the other elements associated with this type of project are present. Usually, there are three successive processes that bring a new system into being I. The feasibility study This is an investigation to decide whether a prospective project is...

The project as a system

A project is concerned with creating a new system and or transforming an old one and is itself a system. Systems, subsystems and environments A simple definition of the term system is 'a set of interrelated parts'. A system will normally be part of a larger system and w ill itself comprise subsystems. Outside the system there will be the system's environment. This w ill be made up of things that can affect the system but over w hich the system has no direct control. In the case of Brightmouth...

What Is Brightmouth College In Managing Contracts

The order you put these projects is. of course, to a large degree subjective. Here is 1.1 Examples of one example of a possible ordering. projects 1. Kuilding the Channel Tunnel Almost everybody puts this one first. The huge scale of the task, the relative novelty of the project, all the different specialisms involved and the international nature of the project make it special. 2. Writing an operating system 'This is a prime example of a software development project. 3. Amending a financial...

Sequencing and scheduling activities

Throughout a project, we will require a schedule that clearly indicates when each of the project's activities is planned to occur and what resources it will need. We shall be considering scheduling in more detail in Chapter 8. but let us consider in outline how we might present a schedule for a small project. One way of presenting such a plan is to use a bar chart as shown in f igure 6.6. 'The chart shown has been drawn up taking account of the nature of the development process (that is....

Conclusions To Software Project Management

estimates are really management targets collect as much information about previous projects as possible use more than one method of estimating top-down approaches will be used at the earlier stages of project planning while bottom-up approaches will be more prominent later on be careful about using other people's historical productivity data as a basis for your estimates, especially if it comes from a different environment (this includes COCOMO ) document your method of doing estimates and...

Software effort estimation techniques

Barry Bochm. in his classic work on software effort models, identified the main ways of deriving estimates of software development effort as algorithmic models - which use 'effort drivers' representing characteristics of the target system and the implementation environment to predict effort expert judgement - where the advice of knowledgeable stall is solicited analogy - where a similar, completed, project is identified and its actual effort is used as a basis for the new project Parkinson -...