CSI ZG511 EC-2R FIRST SEM 2023-2024 IT Infrastructure Projects and Processes.doc Delete | Exams Computer Science

Birla Institute of Technology & Science, Pilani

Work Integrated Learning Programmes Division

First Semester 2023-2024

Mid-Semester Test

(EC-2 REGULAR)

Course No. : CSI ZG511

Course Title : IT Infrastructure Projects and Processes

Nature of Exam : Closed Book

Weightage : 30%

Duration : 2 Hours

Date of Exam : 22nd September -2023 (FN)

Note to Students:

1. Please follow all the Instructions to Candidates given on the cover page of the answer book.

2. All parts of a question should be answered consecutively. Each answer should start from a

fresh page.

3. Assumptions made if any, should be stated clearly at the beginning of your answer.

4. All questions are Scenario based and type of answer expected also to be scenario with Bullet

points highlighted

Q.1 You are the Project manager and doing a Software Development project. You and Senior

manager of Finance were discussing about the costing of the project and benefits and also

to arrive on ROI as per the business case justified. Few discussions were going on, and at

the same time both financial and non-financial benefits have been also being identified.

As the project manager for the software development project aimed at creating a website for

selling network-related projects, it's essential to collaborate closely with the Senior Manager of

Finance to ensure alignment with the company's financial goals. Here's how we can proceed with

the discussions regarding costing, benefits identification, and ROI calculation:

Costing of the Project:

1. Detailed Cost Estimation:

Gather detailed estimates for development resources, software licenses,

infrastructure costs, and any other relevant expenses.

Consider both one-time expenses (e.g., initial development) and recurring

expenses (e.g., maintenance, hosting).

Explore potential cost-saving measures and efficiencies to optimize project

expenditures without compromising quality.

2. Breakdown of Costs:

Categorize costs into different segments to better understand where resources are

allocated.

Examples of cost breakdown could include development costs, licensing fees,

infrastructure setup, marketing expenses, and ongoing maintenance.

3. Cost-Saving Measures:

Identify areas where costs can be minimized through efficient resource allocation,

negotiation of vendor contracts, or leveraging open-source software solutions.

Identification of Benefits:

1. Financial Benefits:

No. of Pages = 2

No. of Questions = 5

Partial preview of the text

Download CSI ZG511 EC-2R FIRST SEM 2023-2024 IT Infrastructure Projects and Processes.doc Delete and more Exams Computer Science in PDF only on Docsity!

Birla Institute of Technology & Science, Pilani Work Integrated Learning Programmes Division First Semester 2023- Mid-Semester Test (EC-2 REGULAR) Course No. : CSI ZG Course Title : IT Infrastructure Projects and Processes Nature of Exam : Closed Book Weightage : 30% Duration : 2 Hours Date of Exam : 22nd^ September -2023 (FN) Note to Students:

Please follow all the Instructions to Candidates given on the cover page of the answer book.
All parts of a question should be answered consecutively. Each answer should start from a fresh page.
Assumptions made if any, should be stated clearly at the beginning of your answer.
All questions are Scenario based and type of answer expected also to be scenario with Bullet points highlighted Q.1 You are the Project manager and doing a Software Development project. You and Senior manager of Finance were discussing about the costing of the project and benefits and also to arrive on ROI as per the business case justified. Few discussions were going on, and at the same time both financial and non-financial benefits have been also being identified. As the project manager for the software development project aimed at creating a website for selling network-related projects, it's essential to collaborate closely with the Senior Manager of Finance to ensure alignment with the company's financial goals. Here's how we can proceed with the discussions regarding costing, benefits identification, and ROI calculation: Costing of the Project:
1. Detailed Cost Estimation:  Gather detailed estimates for development resources, software licenses, infrastructure costs, and any other relevant expenses.  Consider both one-time expenses (e.g., initial development) and recurring expenses (e.g., maintenance, hosting).  Explore potential cost-saving measures and efficiencies to optimize project expenditures without compromising quality.
2. Breakdown of Costs:  Categorize costs into different segments to better understand where resources are allocated.  Examples of cost breakdown could include development costs, licensing fees, infrastructure setup, marketing expenses, and ongoing maintenance.
3. Cost-Saving Measures:  Identify areas where costs can be minimized through efficient resource allocation, negotiation of vendor contracts, or leveraging open-source software solutions. Identification of Benefits:
4. Financial Benefits: No. of Pages = 2 No. of Questions = 5

 Collaborate with stakeholders to identify potential financial benefits such as increased revenue from online sales, cost savings from streamlined processes, and improved operational efficiency.  Quantify financial benefits wherever possible, using market research, historical data, or industry benchmarks to make realistic projections.

Non-Financial Benefits:  Identify non-financial benefits such as enhanced brand reputation, improved customer satisfaction, and competitive advantage in the market.  While these benefits may be more challenging to quantify, they contribute significantly to the overall value proposition of the project. ROI Calculation:
Calculation Methodology:  Calculate the Return on Investment (ROI) by comparing the project's expected benefits to its costs over a specific time period.  Express ROI as a percentage by dividing the net benefits (benefits minus costs) by the project costs and multiplying by 100.
Consideration of Factors:  Take into account factors such as project timeline, discount rates, and potential risks or uncertainties that could impact ROI.  Conduct sensitivity analysis to assess how changes in key variables may affect the project's financial outcomes and overall ROI. Risk Assessment:
Identification of Risks:  Discuss potential risks and uncertainties that could impact the project's costs, benefits, and overall ROI.  Common risks may include technical challenges, changes in market conditions, or unexpected regulatory changes.
Risk Mitigation Strategies:  Develop risk mitigation strategies to address identified risks and minimize their potential impact on the project.  These strategies may include contingency planning, insurance coverage, or diversification of resources. Decision Making:
Informed Decision-Making:  Utilize the ROI analysis and risk assessment findings to inform decision-making regarding project funding, resource allocation, and strategic priorities.  Collaborate closely with the Senior Manager of Finance and other stakeholders to ensure alignment with the company's financial objectives and long-term business goals. By following these steps and engaging in thorough discussions and analyses, we can ensure that the software development project remains financially viable, delivers measurable benefits, and aligns with the company's strategic objectives.

Non-Financial Benefit Description Improved Customer Satisfaction Features such as easy product search, detailed descriptions, and smooth checkout processes contribute to improved customer satisfaction. The website provides a seamless shopping experience, strengthening customer relationships and encouraging repeat purchases. Increased Market Visibility An online presence through the website expands the company's reach beyond traditional marketing channels. It showcases products and services to a wider audience, including potential customers unreachable through traditional methods, increasing brand awareness. Enhanced Customer Engagement The website serves as a platform for direct interaction with customers, enabling feedback, inquiries, and support requests. Interactive features such as live chat and social media integration facilitate engagement and communication, building stronger relationships. Streamlined Business Processes Automation of sales, order management, and customer support processes leads to increased operational efficiency. By reducing manual intervention and streamlining workflows, the website frees up resources, allowing employees to focus on more strategic tasks. Competitive Advantage A well-executed website provides the company with a competitive edge in the market. Superior online shopping experience, innovative features, and value-added services differentiate the company from competitors, attracting customers and sustaining growth. Q.2 As part of your project planning you and project team along with your Quality team are discussing/brainstorming on preparing the Project Quality plan as your project is very complex and risky and also quality activities are of special importance for your project. (a) From the outcome of the above discussion a detailed planning of quality management process is getting prepared, what are the critical 6 steps which have to be taken consideration as of QM Planning process? (A minimum of 6) (3 marks)

Define Quality Objectives:  Clearly define the quality objectives and requirements for the project, ensuring they are specific, measurable, achievable, relevant, and time-bound (SMART).  Example: Ensure that the software development project delivers a bug-free product within the specified timeline, meeting all customer requirements.
Identify Quality Standards:  Identify applicable quality standards, guidelines, and regulations relevant to the project domain, including industry-specific quality standards, regulatory compliance requirements, and organizational quality policies.  Example: Adhere to ISO 9001 quality management standards to ensure consistency and effectiveness throughout project execution.
Plan Quality Assurance Activities:  Develop a comprehensive plan for quality assurance activities aimed at preventing defects and ensuring compliance with quality requirements throughout the project lifecycle. This may include quality audits, inspections, reviews, and process improvements.  Example: Conduct regular code reviews, automated testing, and peer inspections to prevent defects and ensure adherence to quality standards.
Plan Quality Control Activities:

 Develop a plan for quality control activities focused on detecting and correcting defects during project execution, including defining quality control processes, metrics, and checkpoints. Implement mechanisms for timely feedback and corrective actions.  Example: Implement a testing framework with defined test cases and acceptance criteria to detect and correct defects during development.

Establish Quality Metrics:  Define key performance indicators (KPIs) and quality metrics to measure project performance and assess the effectiveness of quality management efforts. Identify relevant metrics related to product quality, process performance, and customer satisfaction. Regularly monitor and analyze these metrics to track progress and identify areas for improvement.  Example: Measure code quality using metrics such as code coverage, code complexity, and defect density to assess project performance.
Document Quality Management Plan:  Document the Project Quality Management Plan detailing all quality-related processes, procedures, roles, and responsibilities, serving as a roadmap for ensuring quality throughout the project lifecycle. Ensure effective communication and update the plan as needed.  Example: Create a comprehensive Quality Management Plan outlining quality- related processes, roles, and responsibilities for all project stakeholders. (b) As per Quality team and project committee meeting what are the various techniques that teams will be using for quality Management planning: (A minimum of 6) (3 marks) In quality management planning, teams employ various techniques to ensure that quality objectives are met throughout the project lifecycle. Here are six techniques commonly used for quality management planning:
Benchmarking:  Benchmarking involves comparing project processes, performance, and outcomes against industry standards or best practices. By identifying areas for improvement and adopting successful practices from other projects or organizations, teams can enhance the quality of their project deliverables.
Quality Function Deployment (QFD):  Quality Function Deployment is a structured approach used to translate customer requirements into specific technical requirements and design characteristics. By systematically prioritizing customer needs and aligning them with project objectives, teams can ensure that their deliverables meet customer expectations and quality standards.
Risk Analysis and Management:  Risk analysis and management techniques, such as Failure Mode and Effects Analysis (FMEA) or Risk Priority Number (RPN), help identify potential risks and uncertainties that may affect project quality. By proactively addressing these risks and implementing mitigation strategies, teams can minimize the likelihood of quality-related issues arising during project execution.
Quality Audits:  Quality audits involve systematic examinations of project processes, procedures, and deliverables to verify compliance with quality standards and requirements. By conducting regular audits at various stages of the project lifecycle, teams can identify non-conformities, discrepancies, or areas needing improvement and take corrective actions as necessary.

 After implementation, the software undergoes testing to ensure that it meets the specified requirements and functions correctly. Testing includes unit testing, integration testing, system testing, and user acceptance testing.

Deployment:  Once testing is complete and the software is deemed ready for release, it is deployed to the production environment for users to access and utilize.
Maintenance:  After deployment, the software enters the maintenance phase, where updates, bug fixes, and enhancements are made as needed to ensure ongoing functionality and usability. Example: Consider a project to develop a new e-commerce website. In the waterfall model:  The project starts with gathering requirements from stakeholders, such as the types of products to be sold, user account features, and payment processing requirements.  Once requirements are gathered, the system design phase begins, where the overall architecture of the website, including database structure, user interface design, and navigation flow, is planned and documented.  Developers then implement the design by coding the website's front-end and back-end functionalities based on the design specifications.  After implementation, the website undergoes testing, including functionality testing, usability testing, and performance testing, to ensure it meets quality standards.  Once testing is complete and any issues are resolved, the website is deployed to the production environment for users to access and make purchases.  Finally, the website enters the maintenance phase, where updates and enhancements are made based on user feedback and changing business requirements. In summary, the waterfall model follows a sequential approach to project management, with each phase completed before moving on to the next. While it provides a clear structure and detailed planning upfront, it may lack flexibility for accommodating changes or iterations during development. (b) Y-Project manager’s case study is more about a project method wherein the motto is value stream impacting positively by eliminating waste from key processes and optimization of verticals, technologies and domain assets, please identify what project model is being used and explain in detail with example. (3 marks) Based on the provided description, Project Manager Y is using the Agile project management methodology for their project. Explanation of Agile Project Management Methodology: Agile is an iterative and flexible approach to project management that emphasizes delivering value to customers through continuous collaboration, adaptation to change, and iterative development. Agile methodologies, such as Scrum, Kanban, and Extreme Programming (XP), focus on breaking down project work into small, manageable increments called iterations or sprints. Agile principles include:
Customer Collaboration Over Contract Negotiation:

 Agile prioritizes collaboration with customers and stakeholders throughout the project to ensure that their needs are met and that the delivered product provides value.

Responding to Change Over Following a Plan:  Agile embraces change and welcomes feedback from customers and stakeholders, allowing teams to adapt and adjust their plans and priorities based on changing requirements or market conditions.
Delivering Working Software Frequently:  Agile encourages delivering working software or product increments frequently, typically at the end of each iteration or sprint, to gather feedback and validate assumptions early in the development process.
Empowering Teams and Individuals:  Agile promotes self-organizing teams and empowers individuals to make decisions and take ownership of their work, fostering collaboration, creativity, and innovation. Example: In the case study presented by Project Manager Y:  Value Stream Impact: The Agile methodology focuses on delivering value to customers by continuously delivering working software or product increments. By breaking down project work into small iterations or sprints, the team can prioritize and deliver features that provide the most value to customers early in the development process.  Eliminating Waste: Agile emphasizes identifying and eliminating waste from key processes. Through techniques such as sprint retrospectives, the team reflects on their processes and identifies opportunities to improve efficiency, reduce rework, and optimize workflows.  Optimization of Verticals, Technologies, and Domain Assets: Agile teams often use practices such as cross-functional collaboration, test-driven development (TDD), and continuous integration (CI) to optimize vertical slices of functionality. By leveraging appropriate technologies and domain-specific knowledge, Agile teams can deliver high- quality, valuable features incrementally. In summary, Project Manager Y's case study demonstrates the application of Agile principles and practices to positively impact the value stream by eliminating waste from key processes and optimizing verticals, technologies, and domain assets. Q.4 You the project manager and your QMS team having various discussion to prepare the Project Risk Management Plan. There were several rounds of discussion on various topics which includes to develop a risk assessment matrix wherein to prioritize all potential risks with level of severity identified. (a) Risk matrix is being used for identifying and preparing for project risks, but the risk matrix itself doesn’t solves the Risks identification and prioritization. What could be the challenges of risk matrices, identify and write with example (A minimum of 6) (3 marks) A risk matrix is a visual tool used in risk management to assess and prioritize risks based on their likelihood and impact. It is typically represented as a matrix or table, with the likelihood of the risk occurring on one axis and the potential impact or severity of the risk on the other axis. The

(b) Quality team was helping you as you are new project manager how to calculate risk in a risk matrix. Capture the steps here that you have documented in your notes to calculate risk of your project using Probability and Severity risk matrix. Explain in detail each step and prepare a sample Project risk matrix (3 marks) Certainly! Below are the steps to calculate risk in a risk matrix using probability and severity, along with a sample project risk matrix: Steps to Calculate Risk in a Risk Matrix:

Identify Risks:  The first step is to identify potential risks that could affect the project. Risks can arise from various sources, including technical challenges, resource constraints, external factors, and changes in project scope.
Assess Probability:  Evaluate the likelihood or probability of each identified risk occurring. Probability can be assessed based on historical data, expert judgment, or qualitative assessment. Common probability categories include low, medium, and high.
Assess Severity:  Assess the potential impact or severity of each identified risk on the project objectives. Severity is typically evaluated in terms of the consequences or effects of the risk event, such as financial losses, schedule delays, or reputational damage. Severity categories may include low, medium, and high.
Assign Probability and Severity Ratings:  Based on the assessments of probability and severity, assign ratings or scores to each risk. These ratings can be numerical values or descriptive labels, such as 1 to 5 or low, medium, and high.
Plot Risks on the Risk Matrix:  Using the assigned probability and severity ratings, plot each risk on the risk matrix. The likelihood axis represents the probability, while the impact axis represents the severity. Risks are placed at the intersection of their probability and severity ratings.
Analyze Risk Exposure:  Analyze the position of each risk on the risk matrix to determine its overall risk exposure. Risks located in the high probability and high severity quadrant are considered the most critical and require immediate attention and mitigation efforts.
Develop Risk Response Strategies:  Based on the risk exposure analysis, develop appropriate risk response strategies for managing and mitigating identified risks. Strategies may include risk avoidance, risk mitigation, risk transfer, or risk acceptance, depending on the nature and severity of the risks. Sample Project Risk Matrix: Below is a sample project risk matrix illustrating how risks can be plotted based on their probability and severity ratings:

Probability / Severity Low (1-2) Medium (3-4) High (5) Low (1-2) Low Medium High Medium (3-4) Low High High High (5) Medium High High In this sample risk matrix:  Risks with low probability and low severity are considered low risk and may require minimal attention.  Risks with high probability and high severity are considered high risk and require immediate mitigation efforts.  Risks falling in between are assessed based on their probability and severity ratings to determine appropriate risk response strategies. This sample risk matrix provides a visual representation of project risks and helps project managers prioritize their risk management efforts effectively. Q.5 Project Managers X, Y, Z of the various different companies but part of the Same Organization was attending an offshore Project Management summit. During that Summit each one of them were presenting Case studies which they are currently use and the success stories 5.Q.A Z-Project manager’s case study is more about a project method wherein project’s overall architecture was ready along with new cost drivers, counting rules, equation and it uses Unadjusted Function Points. The project model is derived from the main project model which uses basic regression formula on historical project data and its characteristics Please identify what project model would have been used and explain in detail? what are the various critical handling situation wherein this project model would have helped Z-Project manager to have a successful Project (2+4=6 marks) Based on the description provided, the project model used by Z-Project Manager is likely Function Point Analysis (FPA) with the incorporation of Unadjusted Function Points (UFP) and regression analysis for estimating project effort. Explanation of Function Point Analysis (FPA) with Unadjusted Function Points (UFP): Function Point Analysis (FPA) is a widely used technique for estimating the size and complexity of software development projects. It quantifies the functionality provided to the user based on five types of function points: External Inputs (EIs), External Outputs (EOs), External Inquiries (EQs), Internal Logical Files (ILFs), and External Interface Files (EIFs). These function points are adjusted based on complexity factors to calculate the size of the project. Unadjusted Function Points (UFP) represent the raw count of function points without considering any complexity adjustments. They provide a baseline measure of the size of the project's functionality. Regression Analysis is a statistical technique used to analyze the relationship between variables and make predictions based on historical data. In the context of project management, regression analysis can be used to estimate project effort based on historical project data and characteristics.

CSI ZG511 EC-2R FIRST SEM 2023-2024 IT Infrastructure Projects and Processes.doc Delete, Exams of Computer Science

Partial preview of the text

Download CSI ZG511 EC-2R FIRST SEM 2023-2024 IT Infrastructure Projects and Processes.doc Delete and more Exams Computer Science in PDF only on Docsity!