Information Technology Project Management
The relationship between organizational culture and project management
Organizational culture has a great impact on the performance of the project because it influences strategies, structures, systems, cultures, and behavioral processes of the organization. Efficient execution of the project requires planning, organizing, and control that form the basic part of organizational culture.
Types of culture that promote a strong project environment
An effective project must have a strong project team culture. According to Schwalbe (2016), a culture of co-operation between the project management and line management helps strengthen the project environment. Moreover, the effective government creates a positive project environment by making sure the organization’s engagement and interest in the proposed project. On the other hand, an organization culture where work activities emphasize groups, has a strong unit integration, high-conflict tolerance, and employees identify more with the organization promotes strong project environment (Schwalbe, 2016).
Relationship between organizational standards and culture
Project managers cannot overemphasize project standards since a good project manager should have effective management skills. A supportive organizational culture and a strong leadership help create strong organizational standards that help maintain the culture of the organization. On the other hand, the absence of a strong culture leads to poor organizational standards. Therefore, the two elements depend on upon each other for a successful execution of the project.
The Agile Challenge
Challenges to the management of projects using Agile Methodologies and how to overcome them
One of the most common challenges found when using Agile Methodologies in project management is the lack of total test coverage. The continuous integration process leads to frequent changes in the software that makes the project team miss major tests as the system waits to be updated. The challenge could be avoided by using a source code that identifies modules changed during the test to ensure continuous testing. Second, Agile Methodologies does not allow earlier detection of defects in the project system is introducing problems of future coding that are costly and delay the project. Project managers can avoid the challenge through conducting frequent code reviews to allow earlier detection of faults. Thirdly, Agile Methodologies cause inadequate API testing during management of projects. The process of testing requires skilled personnel and many projects lack such professionals leading to the development of wrong or missing APIs. The project manager should use tools that allow testers develop API codes without having the needed experience; hence, ensuring complete testing.
Relevance of traditional waterfall development approaches using the project management point of view
Many project managers recommend the Agile Test development because of its simplicity and efficiency, but some project management teams prefer traditional waterfall development cycle in some incidences. The traditional waterfall development approaches are relevant in project management because of its predictive nature. The approach takes the project through different phases (system analysis, design, implementation, testing, and support) (Schwalbe, 2016). Unlike the Agile Test where the project team has authority to return to the original design stage, the waterfall development approach allows continuous process allowing the project team to work on schedule and produce excellent work. For example, when developing software for the organization the project manager provides the client with budget information and timeline. The client understands what to expect and when to expect it even before the execution begins.
Reference
Schwalbe, K. (2016). Information Technology Project Management (8th, Ed.). Boston, USA:
Cengage Learning
