Project Management for Information Technology

Total Length: 890 words ( 3 double-spaced pages)

Total Sources: 3

Page 1 of 3

Information Technology -- Project Management

Functional structure is the classic hierarchy of a CEO, departmental managers reporting to the CEO, and skilled employees in each department (Schwalbe, 2014, p. 49). This is favorable for its flexible use of personnel with specialized skills from each department but unfavorable because each department is focused on its own needs, with low project motivation and awkward intra-departmental coordination.

Project structure has project managers report to the CEO (Schwalbe, 2014, p. 50). Each project manager has staff grouped for a specific project. This is favorable because the project is the focus, and employees are specially assembled, have specific tasks and answer only to their project manager but is unfavorable because there may be duplication of work in different project teams, lack of loyalty to the organization and lack of job continuity.

Matrix structure is a hybrid (Schwalbe, 2014, p. 51), with classic departmental managers but also a department of project managers, with employees reporting to both. This is favorable because the project is the focus, yet specially-skilled employees from different departments can be used, company resources can be balanced and there is greater job continuity but is unfavorable because of the tensions, shared resources, and conflicting ideas/directives from department heads.

Stuck Writing Your "Project Management for Information Technology" ?



2. Compare and contrast the predictive and adaptive product life cycle models. 200 words

A predictive life cycle means a project's scope can be clearly determined and the completion schedule and cost can be precisely anticipated (Schwalbe, 2014, pp. 59-60). The project team spends a good deal of time clarifying system requirements and producing a design. The IT project team may take considerable time developing working software. Models of predictive life cycles include: waterfall, based on stable requirements and having definite, linear points of analysis, design, construction, testing and support; spiral, recognizing the iterative development of software, easily allowing for changes, revisions and their clarification using the original requirements; incremental build, focusing on progressive development of functioning software, with each release adding capabilities; prototyping, which tailors software for heavily involved users; and RAD, using a progressing prototype with significant user involvement to quickly develop a high quality software system (Schwalbe, 2014, pp. 60-1).

Adaptive software development life cycle is based on the belief that requirements cannot be clearly defined in the early stages. Here, risks are expected, incorporated and addressed with more freedom to develop components and functionality for a specific group. These types of projects use target dates within the life cycle, are driven.....

Show More ⇣


     Open the full completed essay and source list


OR

     Order a one-of-a-kind custom essay on this topic


sample essay writing service

Cite This Resource:

Latest APA Format (6th edition)

Copy Reference
"Project Management For Information Technology" (2016, June 07) Retrieved June 30, 2025, from
https://www.aceyourpaper.com/essays/project-management-information-technology-2160076

Latest MLA Format (8th edition)

Copy Reference
"Project Management For Information Technology" 07 June 2016. Web.30 June. 2025. <
https://www.aceyourpaper.com/essays/project-management-information-technology-2160076>

Latest Chicago Format (16th edition)

Copy Reference
"Project Management For Information Technology", 07 June 2016, Accessed.30 June. 2025,
https://www.aceyourpaper.com/essays/project-management-information-technology-2160076