• No results found

Software Development. Project Management

N/A
N/A
Protected

Academic year: 2021

Share "Software Development. Project Management"

Copied!
21
0
0

Loading.... (view fulltext now)

Full text

(1)

Software Development

Project Management

(2)

Project Management Tools

Project management software has the capacity to help plan, organize, and manage resource pools and develop resource estimates.

Depending on the sophistication of the software, it can manage estimation and

planning, scheduling, cost control and budget management, resource allocation,

collaboration software, communication, decision-making, quality management and documentation or administration systems.

(3)

Today, numerous PC & browser based project management software exist and they are finding their way into almost every type of business.

(4)

Software project management

Software project management is the art and science of planning and leading software projects.

It is a sub-discipline of project

management in which software projects are planned, implemented, monitored and controlled.

(5)

History

In the 1970s and 1980s, the software industry grew very quickly, as computer companies quickly recognized the relatively low cost of software production compared to hardware production and circuitry.

To manage new development efforts,

companies applied the established project management methods, but project schedules slipped during test runs, especially when

confusion occurred in the gray zone between the user specifications and the delivered

(6)

To be able to avoid these problems, software project management methods focused on matching user requirements to delivered products, in a method known now as the waterfall model.

Today software project management

methods are still evolving, but the current trend leads away from the waterfall model to a more cyclic project delivery model.

(7)

Software development process

A software development process is concerned primarily with the production aspect of

software development, as opposed to the technical aspect, such as software tools.

These processes exist primarily for supporting the management of software development, and are generally skewed toward addressing

business concerns.

Many software development processes can be run in a similar way to general project

(8)

Examples

Risk management is the process of measuring or assessing risk and then developing

strategies to manage the risk.

Requirements management is the process of identifying, eliciting, documenting, analyzing, tracing, prioritizing and agreeing on

requirements and then controlling change and communicating to relevant stakeholders.

(9)

Change management is the process of identifying, documenting, analyzing,

prioritizing and agreeing on changes to scope (project management) and then controlling changes and communicating to relevant stakeholders.

Software configuration management is the process of identifying, and documenting the scope itself, which is the software product underway, including all sub-products and

changes and enabling communication of these to relevant stakeholders.

(10)

Release management is the process of identifying, documenting, prioritizing and agreeing on releases of software and then controlling the release schedule and

(11)

Project planning, monitoring and control

The purpose of project planning is to

identify the scope of the project, estimate the work involved, and create a project schedule.

Project planning begins with requirements that define the software to be developed. The project plan is then developed to describe the tasks that will lead to completion.

(12)

The purpose of project monitoring and

control is to keep the team and management up to date on the project's progress.

If the project deviates from the plan, then the project manager can take action to correct the problem.

Project monitoring and control involves status meetings to gather status from the team.

When changes need to be made, change control is used to keep the products up to date.

(13)

Gantt Chart

A Gantt chart is a type of bar chart,

developed by Henry Gantt in the 1910s, that illustrates a project schedule.

Gantt charts illustrate the start and finish dates of the terminal elements and summary elements of a project.

Terminal elements and summary elements comprise the work breakdown structure of the project.

(14)

Modern Gantt charts also show the dependency (i.e., precedence network) relationships between activities.

Gantt charts can be used to show current schedule status using percent-complete shadings and a vertical "TODAY" line as shown here.

(15)
(16)

Although now regarded as a common charting technique, Gantt charts were considered revolutionary when first introduced.

This chart is also used in information

technology to represent data that have been collected.

(17)

PERT Chart

The program (or project) evaluation and review technique, commonly abbreviated PERT, is a statistical tool, used in project management, which was designed to analyze and represent the tasks involved in

completing a given project.

First developed by the United States Navy in the 1950s, it is commonly used in

conjunction with the critical path method (CPM).

(18)

PERT is a method to analyze the involved tasks in completing a given project,

especially the time needed to complete each task, and to identify the minimum time needed to complete the total project.

The first step to scheduling the project is to determine the tasks that the project requires and the order in which they must be

(19)

The order may be easy to record for some tasks (e.g. When building a house, the land must be graded before the foundation can be laid) while difficult for others (There are two areas that need to be graded, but there are only enough bulldozers to do one).

Additionally, the time estimates usually reflect the normal, non-rushed time.

Many times, the time required to execute the task can be reduced for an additional cost or a reduction in the quality.

(20)
(21)

Activity 3.1

Create a project plan for your culminating activity. This must include all aspects of the planning, from scope of the project, an estimate of the work involved, and a

project schedule.

Create a Gantt chart as well. Leave the delivery dates blank (for now). You should be able to estimate how long you will

spend on each individual part.

Save your work as john_s_3_1_Plan

(where john_s is replaced by your name) under the appropriate folder for your class in the DropOff folder on the X: drive

References

Related documents

More specifically, the following information is required as input data: beam span; number, magnitudes and locations of concentrated loads; location of the specific point of

+ California State Health Facility Surveyor Training, Sacramento CA, 12 weeks, 1999 + Minimum Data Set (MDS) / Resident Assessment Instrument (RAI), 1996 and 1998 + Provision

It identifies six processes: software planning, software development, software verification, software configuration management, software quality assurance

There are two ways to insert your references into Latex: the first is to store them in an external file and then link them via a command to your current document and use a

As a consequence, driven out from the two propositions stated above, we argue that the market value of the company and the voting pattern observed in its corporate meetings can

Coffee suggests four problems as the likely causes of this systemic breakdown: agency problems within the gatekeeper firms themselves, im- perfect competition

During GMO detection and quantification, it is important to use samples that are representative of the market and the different situations that may be encountered in a

In terms of importation, while this theory might not help explain variation in where gangs emerge, we are particularly interested in how the wider role of social and political