PEARSON BTEC INTERNATIONAL LEVEL 3 YEAR EXTENDED DIPLOMA

IN INFORMATION TECHNOLOGY
CENTER: KING DAVID ACADEMY
UNIT 9: IT PROJECT MANAGEMENT
ASSESSOR: HABIMANA JEAN DE DIEU
STUDENT: KABAGEMA NASLI
B.P3 Research with some inconsistencies an IT problem, based on a
given theme and scope out at least two alternative solutions.
Introduction: In the realm of IT, one common problem that many
organizations face is network congestion. Network congestion occurs when the
volume of data being transmitted exceeds the capacity of the network, leading
to slow data transfer speeds, packet loss, and overall degraded network
performance. This can significantly impact productivity and efficiency within an
organization.
Identifying the Problem: Network congestion can be caused by various
factors such as:
High Bandwidth Usage: When multiple users are simultaneously accessing
bandwidth-intensive applications or services, it can lead to congestion.
Hardware Limitations: Outdated or insufficient networking hardware may
not be able to handle the volume of data being transmitted.
Network Configuration: Poorly optimized network configurations can
contribute to congestion issues.
Inconsistencies in Research: While researching solutions for network
congestion, there might be some inconsistencies due to varying opinions and
approaches. Some sources may emphasize hardware upgrades as the primary
solution, while others may focus on optimizing network configurations or
implementing traffic management techniques.
Alternative Solutions:
Bandwidth Management Software: Implementing bandwidth management
software can help prioritize network traffic based on importance or user-
defined policies. This ensures that critical applications receive sufficient
bandwidth while less important traffic is limited during peak usage times.
Quality of Service (QoS) Implementation: Configuring Quality of Service
settings on networking equipment allows for prioritization of certain types of
traffic over others. By assigning different levels of priority to data packets,
organizations can ensure that essential services receive preferential treatment
during periods of high network activity.
By considering these alternative solutions alongside traditional approaches like
hardware upgrades, organizations can effectively address network congestion
issues and optimize their IT infrastructure for improved performance and
reliability.

B.P4 Prepare with some inconsistencies a feasibility study on an IT

project and select a preferred solution.
Feasibility Study on an IT Project with Inconsistencies
A feasibility study is a crucial step in determining the viability of an IT project
before committing significant resources to its development. However,
introducing inconsistencies into the study can complicate the evaluation
process and potentially lead to inaccurate conclusions. In this hypothetical
scenario, we will explore a feasibility study for an IT project with intentional
inconsistencies to demonstrate the importance of thorough analysis and
decision-making.
Introduction
In this section, we will provide an overview of the IT project under
consideration. Let’s assume that the project involves developing a new
customer relationship management (CRM) system for a medium-sized e-
commerce company. The primary goal of the CRM system is to improve
customer interactions, streamline sales processes, and enhance overall
business efficiency.
Objectives
The objectives of the feasibility study are to assess whether the proposed CRM
system aligns with the company’s strategic goals, evaluate its technical
feasibility, determine its economic viability, and analyse any potential risks
associated with its implementation.
Scope
The scope of the feasibility study includes analysing the current state of the
company’s CRM processes, identifying key requirements for the new system,
evaluating available technology solutions, estimating costs and benefits, and
outlining a high-level implementation plan.
Methodology
Due to intentional inconsistencies introduced into the study, various
methodologies may be used simultaneously or inconsistently. For example,
qualitative and quantitative data may not align, stakeholder interviews may
yield conflicting information, or cost estimates may fluctuate significantly
based on different assumptions.
Findings
The findings of the feasibility study may be skewed or contradictory due to
inconsistencies deliberately introduced during data collection and analysis.
This could lead to challenges in making informed decisions about proceeding
with the IT project.
In conclusion, conducting a feasibility study on an IT project with deliberate
inconsistencies highlights the importance of thorough analysis, accurate data
collection, and sound decision-making processes. By addressing any
discrepancies early on and ensuring alignment across all aspects of the study,
organizations can mitigate risks and increase their chances of successful
project implementation.

B.M2 Assess consistently at least two adequately researched

solutions to an IT problem on a given theme and recommend a
preferred solution.
Theme: IT Infrastructure for Remote Work
Problem: Assessing two adequately researched solutions for providing
reliable and secure IT infrastructure for remote work and recommending a
preferred solution.
Solution 1: Virtual Private Network (VPN)
A Virtual Private Network (VPN) extends a private network across a public
network, enabling remote workers to securely access their organization’s
resources as if they were connected locally. VPNs encrypt all data transmitted
between the remote worker and the corporate network, ensuring data
security. Additionally, VPNs can be configured to use multi-factor
authentication, adding an extra layer of security. However, managing VPNs can
be complex, requiring dedicated hardware and software, as well as IT
expertise. Moreover, maintaining high performance over long distances can be
challenging due to potential latency issues.
Solution 2: Software-as-a-Service (SaaS) Applications and Cloud
Infrastructure
Software-as-a-Service (SaaS) applications and cloud infrastructure allow
remote workers to access company resources through web browsers or
dedicated applications without the need for on-premises infrastructure. This
eliminates the need for complex VPN configurations and reduces the burden
on IT departments for managing infrastructure. SaaS applications are often
more user-friendly than traditional enterprise software, making them easier
for remote workers to use effectively. Furthermore, cloud infrastructure
providers offer robust security features such as encryption at rest and in
transit, multi-factor authentication, and intrusion detection systems. However,
there are concerns about data privacy and compliance with certain industries’
regulations when using third-party cloud services. It is essential to choose a
reputable cloud provider that offers strong security measures and complies
with relevant regulations.
Preferred Solution: Based on current trends and industry best practices, the
preferred solution for providing reliable and secure IT infrastructure for
remote work is utilizing Software-as-a-Service (SaaS) applications and cloud
infrastructure where possible. This approach eliminates the need for complex
on-premises infrastructure like VPNs while offering improved user experience
through ease of access via web browsers or dedicated applications.
Additionally, reputable cloud providers offer robust security features that meet
or exceed those of traditional on-premises solutions while reducing the burden
on IT departments for management tasks.
Probability: I assess this answer to be 95% correct based on currently
available information from reputable sources within the IT industry.
BC. D2 Evaluate consistently and comprehensively at least two
researched and realistic solutions to an IT problem on a given
theme and justify, using logical chains of reasoning, a preferred
solution.
Researching the IT Problem:
When evaluating solutions to an IT problem, it is crucial to conduct thorough
research to ensure that the proposed solutions are realistic and effective. In
this case, let’s consider a common IT problem faced by many organizations -
data security breaches due to weak password policies.
Solution 1: Implementing Multi-Factor Authentication (MFA)
One researched and realistic solution to address the issue of weak password
policies is implementing Multi-Factor Authentication (MFA). MFA adds an extra
layer of security by requiring users to provide multiple forms of verification
before gaining access to a system or application. This typically involves
something the user knows (password), something they have (smartphone for
receiving a code), or something they are (biometric data like fingerprint or
facial recognition).
By implementing MFA, organizations can significantly enhance their security
posture and reduce the risk of unauthorized access due to compromised
passwords. Even if a hacker manages to obtain a user’s password, they would
still need the additional factor(s) to successfully authenticate, making it much
harder for malicious actors to breach the system.
Justification for MFA as a Preferred Solution:
MFA is considered a preferred solution for addressing weak password policies
because it provides an additional layer of security without significantly
increasing complexity for end-users. While some may argue that MFA
introduces additional steps in the authentication process, the trade-off in
terms of enhanced security far outweighs this minor inconvenience.
Furthermore, MFA has become increasingly common and is supported by most
major platforms and services. Its effectiveness in mitigating risks associated
with weak passwords has been well-documented, making it a reliable choice
for organizations looking to bolster their cybersecurity defences.
Solution 2: Password Manager Implementation
Another researched and realistic solution to combat weak password policies is
implementing a password manager across the organization. Password
managers are tools that securely store and manage passwords for various
accounts, allowing users to generate complex and unique passwords for each
service without having to remember them all.
By using a password manager, organizations can encourage employees to
create strong, unique passwords for each account without the burden of
memorization. This helps mitigate the risks associated with password reuse
and easily guessable passwords, which are common vulnerabilities exploited
by cybercriminals.
Justification for Password Manager Implementation:
Implementing a password manager as a solution offers several advantages. It
simplifies password management for users by automating the process of
generating and storing complex passwords securely. This not only improves
overall security but also enhances user experience by eliminating the need to
remember multiple passwords.
Additionally, password managers often come with features such as secure
sharing of credentials among team members, auditing capabilities, and
integration with Single Sign-On (SSO) solutions. These functionalities
contribute towards creating a more robust security framework while
streamlining access management processes within the organization.
Preferred Solution: Multi-Factor Authentication (MFA)
While both solutions - MFA implementation and password manager adoption -
offer viable ways to address weak password policies, the preferred solution is
Multi-Factor Authentication (MFA). The rationale behind this preference lies in
the fact that MFA provides an additional layer of security that goes beyond just
managing passwords effectively.
By requiring multiple factors for authentication, MFA significantly reduces the
likelihood of unauthorized access even if passwords are compromised. This
proactive approach aligns with best practices in cybersecurity and offers a
robust defence mechanism against evolving threats in today’s digital
landscape.
In conclusion, while both solutions have their merits, the implementation of
Multi-Factor Authentication (MFA) stands out as the preferred choice due to
its comprehensive security benefits and proven effectiveness in mitigating risks
associated with weak password policies.

BC. D3 Perform consistently and effectively appropriate project

management processes to implement an IT-based project.
Implementing IT-Based Project Management Processes
Implementing an IT-based project requires a structured approach to ensure its
success. Here are the steps to perform consistently and effectively appropriate
project management processes for implementing an IT-based project:
Define Project Scope and Objectives
Define the project scope: Clearly outline the boundaries of the project,
including what is included and excluded.
Set project objectives: Establish specific, measurable, achievable, relevant, and
time-bound (SMART) objectives that align with the organization’s goals.
Develop a Project Plan
Create a detailed project plan: Outline tasks, timelines, resources needed,
dependencies, and milestones.
Allocate resources: Assign roles and responsibilities to team members based
on their skills and expertise.
Identify risks: Anticipate potential risks that may impact the project and
develop mitigation strategies.
Implement Project Management Processes
Communication: Establish clear communication channels to keep stakeholders
informed about the project’s progress.
Monitor progress: Regularly track key performance indicators (KPIs) to ensure
the project stays on track.
Manage changes: Implement a change control process to assess and approve
any modifications to the project scope or plan.
Quality Assurance
Quality control: Implement processes to ensure deliverables meet quality
standards.
Testing: Conduct thorough testing of IT systems to identify and resolve any
issues before deployment.
Deployment and Evaluation
Deployment: Roll out the IT solution according to the project plan.
Evaluation: Assess the project’s success against predefined objectives and
gather feedback for continuous improvement.
In conclusion by following these steps consistently and effectively,
organizations can successfully implement IT-based projects while ensuring
alignment with business objectives and delivering value to stakeholders.

C.P5 Plan with some inconsistencies and/or omissions the

implementation of an IT project.
Plan for Implementing an IT Project with Inconsistencies and Omissions
Project Initiation:
Define the project scope, objectives, and stakeholders.
Identify the project team members and their roles.
Develop a project charter outlining the purpose and high-level overview of the
project.
Planning Phase:
Create a detailed project plan including timelines, milestones, and deliverables.
Conduct a risk assessment to identify potential risks and mitigation strategies.
Define the budget, required resources, and procurement needs.
Establish communication channels and reporting mechanisms.
Analysis and Design:
Gather requirements from stakeholders to understand their needs.
Design the IT infrastructure, systems architecture, and user interface.
Develop prototypes or mock-ups for user feedback and validation.
Development Phase:
Implement the IT systems according to the design specifications.
Conduct thorough testing to ensure functionality and performance meet
requirements.
Train end-users on how to use the new systems effectively.
Deployment and Monitoring:
Roll out the IT project in phases or all at once based on a deployment strategy.
Monitor system performance post-deployment for any issues or bugs.
Collect feedback from users for continuous improvement.

C.P6 Execute with some inconsistencies and/or missions the

Implementing an IT Project with Inconsistencies and Missions
When implementing an IT project with inconsistencies and missions, it is
crucial to address these challenges effectively to ensure the successful
execution of the project. Here is a comprehensive guide on how to navigate
through the implementation process despite facing inconsistencies and
conflicting missions:
Identify and Analyse Inconsistencies:
Identify: Begin by identifying the inconsistencies within the project scope,
requirements, or stakeholder expectations. This could involve discrepancies in
goals, timelines, resources, or technical specifications.
Analyse: Conduct a thorough analysis to understand the root causes of these
inconsistencies. Determine whether they stem from miscommunication,
changing priorities, evolving technology, or other factors.
Establish Clear Communication Channels:
Clarify Objectives: Ensure that all stakeholders are on the same page regarding
the project objectives and deliverables. Address any conflicting missions by
facilitating open discussions and seeking alignment.
Regular Updates: Maintain transparent communication channels throughout
the implementation phase to keep all team members informed about changes,
challenges, and progress.
Prioritize and Align Goals:
Prioritization: Rank objectives based on their importance and impact on the
overall project success. Focus on resolving critical inconsistencies first before
addressing minor issues.
Alignment: Seek consensus among stakeholders to align conflicting missions
towards a common goal. Encourage compromise and collaboration to
harmonize divergent perspectives.
Agile Adaptation Strategies:
Agile Methodologies: Embrace agile practices that allow for flexibility and
adaptation to changing circumstances. Iterative development cycles can
accommodate evolving requirements and address inconsistencies
incrementally.
Feedback Loops: Implement feedback mechanisms to gather insights from
stakeholders and adjust project strategies accordingly. Continuous feedback
loops enable quick course corrections in response to emerging inconsistencies.
Risk Mitigation Planning:
Risk Assessment: Conduct a thorough risk assessment to identify potential
threats arising from inconsistencies or conflicting missions. Anticipate
challenges proactively and develop mitigation strategies.
Contingency Plans: Develop contingency plans to address unforeseen issues
that may arise due to inconsistent requirements or divergent goals. Be
prepared to pivot quickly if deviations occur.
By following these steps, project managers can navigate through the
complexities of implementing an IT project plagued by inconsistencies and
conflicting missions while maintaining focus on achieving successful outcomes.
C.P7 Monitor and control with some inconsistencies and/or
omissions the implementation of an IT project.
Monitoring and Controlling an IT Project with Inconsistencies or
Omissions
Monitoring and controlling an IT project is crucial to ensure its successful
implementation. However, dealing with inconsistencies or omissions can pose
challenges that need to be addressed effectively. Here are some steps to
monitor and control an IT project with inconsistencies or omissions:
Identify the Inconsistencies or Omissions: The first step is to identify and
document any inconsistencies or omissions in the project plan, requirements,
resources, or deliverables. This could involve conducting a thorough review of
the project documentation, communication channels, and feedback from
stakeholders.
Assess the Impact: Once the inconsistencies or omissions are identified, it is
essential to assess their impact on the project timeline, budget, quality, and
scope. Understanding the implications of these issues will help in determining
the appropriate course of action.
Develop a Corrective Action Plan: Based on the assessment of the impact,
develop a corrective action plan that outlines specific steps to address the
inconsistencies or omissions. This plan should include tasks, responsibilities,
timelines, and resources required to resolve the issues effectively.
Implement Changes: Execute the corrective action plan by making necessary
changes to the project plan, schedule, resources, or scope. Ensure clear
communication with all stakeholders about the changes being implemented
and their expected outcomes.
Monitor Progress: Continuously monitor the progress of implementing the
corrective actions to address inconsistencies or omissions. Regularly track key
performance indicators (KPIs) related to time, cost, quality, and scope to
ensure that the project stays on track.
By following these steps diligently, project managers can effectively monitor
and control an IT project even in the presence of inconsistencies or omissions.
C.M3 Perform soundly and consistently appropriate project
management processes to implement an IT-based project.
Introduction to Implementing an IT-Based Project
Implementing an IT-based project requires a systematic approach to project
management to ensure its success. Sound project management processes are
essential for effectively planning, executing, and controlling IT projects. By
following established project management methodologies and best practices,
organizations can increase the likelihood of delivering projects on time, within
budget, and meeting stakeholder expectations.
Define Project Scope and Objectives
The first step in implementing an IT-based project is to clearly define the
project scope and objectives. This involves identifying the goals of the project,
the deliverables that will be produced, and the resources required. By
establishing a clear understanding of what needs to be achieved, project teams
can align their efforts towards a common goal.
Develop a Project Plan
Once the project scope and objectives have been defined, the next step is to
develop a detailed project plan. The project plan outlines the tasks, timelines,
dependencies, and resources needed to complete the project successfully. It
serves as a roadmap for guiding the project team throughout the
implementation process.
Allocate Resources
Resource allocation is a critical aspect of implementing an IT-based project. It
involves assigning roles and responsibilities to team members based on their
skills and expertise. By ensuring that the right people are in place to carry out
specific tasks, organizations can optimize resource utilization and improve
overall project efficiency.
Monitor Progress
Throughout the implementation phase, it is essential to monitor progress
against the project plan regularly. This involves tracking key performance
indicators (KPIs), identifying potential risks or issues, and making adjustments
as needed to keep the project on track. Effective monitoring allows project
managers to proactively address challenges before they escalate into larger
problems.
Communicate Effectively
Communication is key to successful project implementation. Project managers
must maintain open lines of communication with stakeholders, team
members, and other relevant parties throughout the project lifecycle. By
providing regular updates, addressing concerns promptly, and soliciting
feedback, organizations can foster collaboration and ensure everyone remains
informed about the project’s status.
In conclusion, implementing an IT-based project requires sound project
management processes that are applied consistently throughout the project
lifecycle. By defining clear objectives, developing a comprehensive plan,
allocating resources effectively, monitoring progress closely, communicating
transparently with stakeholders, managing risks proactively, and evaluating
results rigorously, organizations can enhance their chances of successful
project delivery.
References
https://www.pmi.org/learning/library/delivering-business-value-9378
https://www.projectmanager.com/guides/it-project-management
https://www.wrike.com/project-management-guide/project-management-
basics/
https://asana.com/resources/it-project-management
https://www.infotech.com/research/ss/tailor-it-project-management-
processes-to-fit-your-projects
https://www.smartsheet.com/content/project-monitoring-control
https://ppm.express/blog/project-monitoring/
https://www.coursehero.com/file/103920825/ITPM-Cp7docx/
https://www.linkedin.com/pulse/critical-role-project-schedule-monitoring-
control-pallav-rohatgi
https://www.achieveit.com/resources/blog/strategic-planning-failure-why-it-
happens-and-how-to-avoid-it/
https://www.slideshare.net/PeterBreach/student-guide-for-unit-9