ISY2004 | Management | The Ten Knowledge Areas Of Project Management

2. Scope Management Knowledge Area:

This knowledge area aims to define the IS project scope. The Scope management knowledge area in IS project possesses six activities. These are planning of scope management, collecting information, determining the scope, designing WBS, confirming, and controlling the scope.

3. Schedule Management Knowledge Area:

The purpose of Schedule Management knowledge area is to finish the project on time with consistency. It has seven activities among which one belongs to the controlling and monitoring the process group while the remaining six are related to the planning stage. These are: planning of schedule management, describing processes, sorting activities, determining activity resources, determining activity times, creating the schedule and managing the schedule (Martinelli, and Milosevic, 2016).

4. Cost Management Knowledge Area:

Cost Management Knowledge Area in IS project aims to carry out the project within the estimated budget. This knowledge area possesses four activities which are developing cost management, computing costs, preparing the budget, and managing the costs.

5. Quality Management Knowledge Area:

The purpose of this knowledge area in IS project is to meet out the objectives of project’s quality. It has three activities which are planning of management process, carrying out the quality assurance plan, and monitoring the quality process.

6. Resource Management Knowledge Area:

This knowledge is also called as Human Resource Management Knowledge Area, having four activities which aim to conduct people management of IS project resources. These activities are recruiting the project team, building a project team and managing that project team.

7. Communications Management Knowledge Area:

In IS project management, a certain amount of internal and external communication is essential among the team, which is done through communication management processes (Barki et al., 2010). The activities involved in this area are planning the communications management, managing communications, and controlling communications.

8. Risk Management Knowledge Area:

This knowledge area in IS projects aims to minimize the impact of risks on the project once these are estimated. The activities included in this area are planning the risk management, forecasting risks, doing qualitative risk analysis, doing quantitative risk analysis, and developing risk responses.

9. Procurement Management Knowledge Area:

The primary objective of this knowledge area in IS project is to coordinate and manage the acquisition activities in the project. It has four activities namely, procurement planning, managing procurements, organizing and controlling of procurement, and procurement closing.

10. Stakeholder Management Knowledge Area:

The purpose of this knowledge area in IS project is to identify and manage the needs and wants of the stakeholders during the project lifecycle. It contains 4 activities which are recognizing the stakeholders, managing stakeholders, monitoring their expectations, and controlling stakeholder management plan.

Threats related to improving quality in IS projects

In IS project, the occurrence of quality related threats are very common. For example, when the project software is crashed out or generates inaccurate results, the quality becomes poor. The threats created by low quality projects are higher in the projects which deal with intangibles like business process transformation software. These threats include:

Budget Constraints:

In a IS development project, quality results are the ultimate goal. Budgets assist the managers analyze the quality impact of project by estimating the associated costs. When the budget is limited, the effectiveness of the project is decreased which hamper the project quality.

Lack of Team Flexibility:

Team flexibility refers to the collective ability of team to work effectively. Flexibility enables the project team to explore the problems and find new ways to resolve it. If there is no such flexibility, the quality of the project is hampered.

Requirements and specifications:

When all the requirements and specifications are not met out while developing a IS project, it becomes more likely that it would generate poor quality outcomes.

Peer review of code:

Ineffective code reviews and pair programming are a big threat to IS project quality. Having improper design and coding guidelines leads to low quality output.

PM Plan

Project Management Plan refers to the documents which are necessary to execute the project. These documents define, prepare, and coordinate the different planning activities for the successful execution (Tarhini et al., 2018). In this IS project development, following activities are designed till the closure of the project, which is also called Work Breakdown Structure:

WBS:

The following WBS is prepared to breakdown the project team work into manageable tasks to simplify the project execution.

Gantt chart

A Gantt chart refers to a bar diagram that represents a project schedule (Marchewka, 2014). The following Gantt chart illustrates the tasks to be performed in the IS development project.

Project Quality Management Plan

Quality Management is an important part of PM plan, which is used to ensure that all the aspects related to project quality are met effectively. Since large IS projects are inherently risky and complex, these are managed by many project managers at different stages of completion (Freeman et al., 2010). Following is the IS Project Quality Management Plan which is designed to mitigate the quality related threats:

The following table illustrates the roles and responsibilities of the IS project team to monitor, control and ensure the quality management:

Risk Management Plan

Since IS project’s is activities are associated with sophisticated technology and high level of knowledge, the risks on such projects are necessary to be eliminated to develop an effective IS. Following is the Risk Management Plan for IS project development:

Relevance of Project Quality Management in leading Global Teams

Cultural and Legal Issues

The impact of global cultures in the project management process has been a constant target for the project managers. According to Hofstede, one of the famous scholars of this subject argues that the internationalization of business does not essentially results in the globalization of culture and hence, basic management solutions may not be of use in specific cultural contexts (Kerzner, and Kerzner, 2017). Thus, for making the project management solutions valuable, the project manage is required to take into account cultural differences that prevail in the human societies. Other authors also stated that culture acts as a mental programming formed by patterns of feeling and actions that each individual has.

On the other hand, legal issues are the other aspect considered while managing global team in a project. These issues include Country-specific regulations, political conditions, environmental laws, and established standards (Kirsch, 2010). As a result, the project manager and the team are required to learn about the legal rules, issues, and guidelines of all the countries affecting the project.

In IS projects, project quality management helps the project manager in providing adequate standards and managing global teams in the following ways:

Managing Cultural issues:

• Dealing with power groups and functional barriers
• Eliminating information retention by supporting transparency and open communication
• Overcoming skeptical behavior, fatalism, and lack of severity in the team
• Developing shared vision and objectives throughout the global teams
• Encouraging the participation and buy-in of global operational team members
• Understanding of various races for improved team

Managing Legal issues:

• Understanding the legal conditions of different countries properly
• Planning project activities in accordance to the country-specific laws
• Communicating to the project team members from time to time regarding any changes in the legal framework of any country where the project activities are highly affected
• Developing the solutions and take actions within the legal framework
• Taking approval from the relevant law before implementing any policy for the project

Conclusion

On the basis of the above report it can be concluded that in order to complete an IS project, it becomes necessary to implement the project plan and assign responsibilities effectively. The different knowledge areas should be considered while designing project activities. Furthermore, when the project team operates at the global level, the relevant cultural and legal challenges should be analyzed to make the project a success. 

References

Turner, R. and Ledwith, A. (2018) Project Management in Small to Medium?Sized Enterprises: Fitting the Practices to the Needs of the Firm to Deliver Benefit, Journal of Small Business Management, 56(3), pp.475-493.

Martinelli, R.J. and Milosevic, D.Z. (2016) Project management toolbox: tools and techniques for the practicing project manager. USA: John Wiley & Sons.

Freeman, R.E., Harrison, J.S., Wicks, A.C., Parmar, B.L. and Colle, S.D. (2010) Stakeholder Theory: The State of the Art. UK: Cambridge University Press.

Kirsch, L.S. (2010) Portfolios of control modes and IS project management, Information systems research, 8(3), pp.215-239.

Kerzner, H. and Kerzner, H.R. (2017) Project management: a systems approach to planning, scheduling, and controlling.USA: John Wiley & Sons.

Marchewka, J.T. (2014) Information technology project management. USA: John Wiley & Sons.

Barki, H., Rivard, S. and Talbot, J. (2010) An integrative contingency model of software project risk management, Journal of management information systems, 17(4), pp.37-69.

Tarhini, A., Yunis, M. and El-Kassar, A.N., (2018) Innovative sustainable methodology for managing in-house software development in SMEs, Benchmarking: An International Journal, 25(3), pp.1085-1103.