Study Document
Project Management for Information Technology
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.
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 by mission and focused on components (Schwalbe, 2014, p.…
Sample Source(s) Used
Works Cited
Bolman, L. G., & Deal, T. E. (2008). Reframing organizations. Retrieved from www.slideshare.net: http://www.slideshare.net/PhilVincent1/fourframe-model
Method123. (n.d.). Project Management Life Cycle. Retrieved from www.method123.com: http://www.method123.com/project-lifecycle.php
Schwalbe, K. (2014). Information technology project management (Rev. 7th ed.). Boston, MA: Cengage Learning.
Related Documents
Study Document
Project Management: Information Technology
Project Management Importance of Aligning IT projects with corporate strategy IT is an integral part of business operations, helping organizations to, among things, enhance their productivity, standardize processes, reduce operational costs, and implement business strategies. It is crucial, therefore that IT projects align with the organization's corporate strategy, and that the two are synchronized towards the accomplishment of organizational goals. Lack of synchronization between projects and business strategy has been identified as
Study Document
Information Systems Project Management Information
Multinational management challenges regarding project work refer to its complexity, scope, and risks. Specialists have observed that large it projects provide important advantages to joint ventures. This is related to the development of global teams. The indicators in these cases have been identified as technical difficulties, evolving solutions, innovation, and others. The challenges of large it projects are addressed by several types of management approaches, in accordance with the characteristics of
Study Document
Managing Information Technology - Set
The vision Oracle has is one of unifying all of their enterprise applications into their Fusion architecture and creating a single unifying Service oriented Architecture (SOA) was first announced in 2006 (Krill, 13). Since that time Oracle has continually strived to create an SOA in Fusion that would appeal to its corporate customers. The proposed Fusion SOA platform has been designed to be robust and scalable enough to encompass enterprise-level
Study Document
IT Project Manager Information Technology Is a
IT Project Manager Information Technology is a very wide area that needs technical expertise and up-to-date knowledge on the latest innovations and developments. Technology is very dynamic and the technology developers are unveiling more user friendly systems on a daily basis making Information Technology Industry very competitive. Through the use of Technology, information sharing has become an easy task as news on the latest technological advancements is shared with the rest
Study Document
An Analysis of Project Management
Project Management Grey Sloan Memorial Hospital was founded in 1982 and has since then offered medical services to the public. The health care organization is located in central Washington DC and has been one of the renowned hospitals in the region. However, in the past six months, the health care organization has experienced a great influx of critical and acute patients needing medical treatment. The chief of general surgery has since
Study Document
Managing Information Systems Introduction in
Furuholt, (2006) argues that lack of management engagement to the acceptance of information systems has been a barrier to the implementation of information systems. The issues are even common with organizations in the developing countries where management does not give enough priority to the information systems implementation. Importantly, implementation of information systems requires management support since management will need to approve fund that would be used for IS implementation.