Basics of IT and Governance PK0-005 Practice Quiz

• A. ESG stands for Environmental, Social, and Governance, a framework that evaluates organizations (and projects) across three dimensions: environmental impact (carbon footprint, resource use), social impact (labor practices, diversity, community), and governance (ethics, transparency, compliance); projects increasingly must consider ESG factors because stakeholders, regulators, and investors expect organizations to operate responsibly beyond just financial returns
• B. ESG stands for Enterprise Software Guidelines, technical standards for software development
• C. ESG stands for Executive Steering Group, the committee that approves project charters
• D. ESG is only relevant to publicly traded companies, private organizations and their projects are exempt

ESG FRAMEWORK IN PROJECT MANAGEMENT: ENVIRONMENTAL (E): how a project affects the natural environment; includes: carbon emissions from project activities; energy consumption; waste generated; resource depletion; ecological impact; GREEN IT considerations (data center energy, e-waste); SOCIAL (S): how a project affects people, employees, communities, and society; includes: diversity and inclusion in the project team; labor practices (fair wages, safe working conditions); community impact of the project deliverable; supply chain labor practices (ethical sourcing); employee well-being and work-life balance; GOVERNANCE (G): how a project is directed and controlled ethically; includes: transparency and honest reporting; regulatory compliance; anti-corruption and anti-bribery; data privacy and security; ethical decision-making; board-level oversight; WHY RELEVANT TO PMs: organizations now face ESG reporting requirements (EU Corporate Sustainability Reporting Directive, SEC climate disclosure rules); investors use ESG scores to make investment decisions; customers prefer organizations with strong ESG performance; regulatory penalties for ESG violations are increasing; project managers must account for ESG factors in project planning, risk assessment, and execution.

• A. Environmental project considerations include: energy efficiency of new server hardware (Power Usage Effectiveness, PUE); renewable energy sourcing for the data center; heat waste and cooling system efficiency; e-waste disposal plan for decommissioned hardware; carbon offset options for unavoidable emissions; compliance with environmental regulations; embodied carbon in new hardware procurement
• B. Environmental considerations are not a project manager's responsibility, only the facilities team handles environmental issues
• C. Environmental factors only apply to construction projects, IT projects have no environmental footprint
• D. Environmental considerations only affect the final product, not the project activities themselves

ENVIRONMENTAL CONSIDERATIONS for data center upgrade: ENERGY EFFICIENCY: Power Usage Effectiveness (PUE) = total data center energy / IT equipment energy; industry average PUE ≈ 1.57; hyperscaler efficiency ≈ 1.1-1.2; specify PUE targets for new hardware in the requirements; servers: choose Energy Star certified hardware; RENEWABLE ENERGY: can the data center be powered by renewable energy (solar, wind)? are Power Purchase Agreements (PPAs) available? HEAT AND COOLING: hot aisle/cold aisle containment reduces cooling waste; free cooling (using outside air or water when temperature allows) reduces energy; waste heat recovery (using server heat for building heating). E-WASTE: where do decommissioned servers go?; responsible e-waste recycling certification (R2, e-Stewards); avoid sending e-waste to developing countries; CARBON FOOTPRINT: calculate the project's Scope 1 (direct), Scope 2 (electricity), and Scope 3 (supply chain) emissions; identify carbon offset opportunities; HARDWARE PROCUREMENT: ask vendors about their manufacturing emissions; consider refurbished or remanufactured equipment to reduce embodied carbon; REGULATORY COMPLIANCE: applicable environmental regulations for IT disposal and energy use.

• A. D&I practices in project team formation and execution: consider diverse candidate pools when requesting team members from functional managers; set inclusive meeting norms (language, time zones, and accessibility); ensure psychological safety (all team members' ideas are heard and valued); provide equitable opportunities (all team members get meaningful assignments, not just senior ones); be aware of unconscious bias in task assignment (ensure junior or underrepresented team members aren't always assigned support roles)
• B. D&I only applies to corporate HR policies, individual project teams are assembled based purely on technical skills
• C. D&I means ensuring all team members have identical assignments regardless of skill, equal work distribution
• D. D&I only applies to gender diversity, other dimensions of diversity are not relevant to project teams

D&I PRACTICES in project team formation and execution: TEAM FORMATION: request team members from diverse talent pools when working with functional managers; if all available candidates are from the same demographic, flag this as a concern; avoid defaulting to 'people I know' (which perpetuates existing homogeneity); consider cognitive diversity, different thinking styles and backgrounds approach problem-solving differently (researchers consistently find that diverse teams produce better solutions for complex problems like healthcare app design); INCLUSIVE MEETING PRACTICES: time zone equity, don't always schedule meetings at times that are inconvenient for one office location; language accessibility, avoid jargon that creates barriers for non-native speakers; active inclusion, solicit input from quieter team members, not just the most vocal; PSYCHOLOGICAL SAFETY: team members should feel safe raising quality concerns, dissenting opinions, or admitting mistakes without fear of retaliation; the PM models this by acknowledging their own mistakes and encouraging candid feedback; EQUITABLE OPPORTUNITY: meaningful project roles and leadership opportunities should be distributed across team members, not concentrated among the most senior; ACCESSIBLE DELIVERABLES: the healthcare app should be designed with accessibility in mind from the start (WCAG compliance for users with visual, motor, or cognitive disabilities); UNCONSCIOUS BIAS AWARENESS: be conscious of patterns in task assignment; if all the visible/presentable work goes to some team members and all the hidden/support work goes to others, that's a bias pattern worth examining.

• A. Integrate compliance requirements as project requirements from the start: identify all applicable regulations (GDPR for EU employees, CCPA for California employees, HIPAA if health data is involved, SOX if financial data is included); engage the legal and compliance team as project stakeholders; add compliance requirements to the requirements document; include compliance testing in the QA plan; build privacy-by-design into the architecture; schedule regulatory review as a project milestone
• B. Compliance is the legal team's responsibility, the PM delivers the system and legal handles compliance after
• C. Compliance requirements are added at go-live during the final testing phase, earlier is too speculative
• D. Only the regulations the PM personally knows about need to be addressed, it's not the PM's job to research regulations

REGULATORY COMPLIANCE INTEGRATION in project planning: IDENTIFY ALL APPLICABLE REGULATIONS: GDPR (General Data Protection Regulation): applies to processing personal data of EU residents; requires: consent management; right to erasure; data minimization; privacy notices; data breach notification; DPA (Data Processing Agreement) with any third-party vendors; CCPA (California Consumer Privacy Act): similar to GDPR for California residents; HIPAA: if the HR system captures health-related data (disability accommodations, medical leave); SOX (Sarbanes-Oxley): if HR data feeds financial controls (payroll, equity compensation); ENGAGE COMPLIANCE AS STAKEHOLDERS: add Data Protection Officer (DPO) or legal counsel to the stakeholder register; compliance requirements must come from people who understand the regulations; REQUIREMENTS INTEGRATION: GDPR-specific requirements: 'Users can request deletion of their personal data within 30 days'; 'Personal data is not retained beyond 7 years'; 'Data is encrypted in transit and at rest'; these go into the requirements document, not in a separate compliance document; PRIVACY-BY-DESIGN in architecture: data minimization (collect only what's needed); purpose limitation (use data only for its stated purpose); storage limitation (automated deletion after retention period); COMPLIANCE TESTING: specific test cases for each regulatory requirement; REGULATORY REVIEW MILESTONE: a phase gate where the legal/compliance team formally reviews and approves the design before development begins.

• A. The PM should maintain the 60-hour weeks, delivery commitments override employee wellbeing
• B. The developer's complaint should be ignored, professional project team members accept whatever hours are required
• C. Social ESG considerations support reducing the unsustainable pace: employee wellbeing is a social responsibility dimension; sustained overwork produces diminishing quality returns, increases defect rates, and increases burnout/attrition risk; alternative approaches (scope reduction, timeline extension, additional resources) should be explored before accepting team burnout as the solution
• D. Wellbeing concerns are HR's responsibility, the project manager should not get involved

SOCIAL ESG AND EMPLOYEE WELLBEING: DIRECT SOCIAL RESPONSIBILITY: employee wellbeing is explicitly a Social ESG factor; organizations that systematically overwork employees are failing on the social dimension of ESG; the PM who enables or mandates unsustainable hours is contributing to this failure; PRODUCTIVITY RESEARCH: 'crunch culture' data shows: productivity peaks at approximately 50 hours per week; beyond 55 hours, productivity per hour DECREASES; after 3-4 weeks of 60+ hours, cumulative output of 60 hours = roughly same as 50 hours (diminishing returns); defect rates increase 15-20% in the fourth week of crunch; ALTERNATIVE APPROACHES (the PM should evaluate): SCOPE REDUCTION: can low-priority features be deferred to Phase 2?; TIMELINE EXTENSION: can the delivery date be extended by 2-4 weeks? (often less costly than burnout-induced quality failures); ADDITIONAL RESOURCES: can a contractor be temporarily added to relieve the critical path bottleneck?; SCOPE NEGOTIATION: can the stakeholder accept a reduced MVP at the original date?; PM RESPONSIBILITY: the PM is not just a deliverer of features, they are responsible for the team's sustainable operation; raising this concern with the sponsor ('we can hit the date but the current pace is unsustainable, here are the options') is professional project management.

• A. Ignore it, the winning vendor technically met all the evaluation criteria
• B. Confront the committee chair privately, personal resolution is more appropriate than formal reporting
• C. This is a conflict of interest and potential corruption issue requiring escalation: the PM should document the concern; report it through the organization's ethics reporting channel (or to the legal/compliance department); the concern must be investigated to determine whether the vendor selection was fair; if the selection was compromised, the procurement may need to be reconsidered, the governance ESG principle of fair, transparent decision-making was violated
• D. Mention it casually at the next team meeting, informal awareness is sufficient for governance issues

GOVERNANCE ESG, CONFLICT OF INTEREST AND ANTI-CORRUPTION: WHAT HAPPENED: vendor selection committee chair received gifts (sports tickets) from a vendor bidder; the chair did not disclose this relationship; this is a CONFLICT OF INTEREST, the chair had a personal interest that may have influenced their evaluation; depending on jurisdiction and organization policy, this may also constitute BRIBERY (vendor provided value to influence a public official or corporate decision-maker). GOVERNANCE ESG OBLIGATIONS: ANTI-CORRUPTION: ESG governance requires honest, unbiased decision-making; personal gifts influencing procurement decisions corrupt this principle; TRANSPARENCY: the decision-making process should be transparent, undisclosed relationships undermine this; FAIRNESS: all vendors must compete on a level playing field, personal relationships create unfair advantages. PM OBLIGATIONS: PMI Code of Ethics requires PMs to report unethical behavior through appropriate channels; DOCUMENT: record what was observed and when; REPORT: use the organization's ethics hotline, compliance department, or ombudsperson; do NOT report to the committee chair directly (they are the subject); ESCALATION: if internal reporting channels are compromised, external reporting (board audit committee, regulatory authority) may be appropriate; INVESTIGATION: the organization should investigate whether the selection was influenced; potentially re-run the procurement with the chair recused; PROTECTION: whistleblower protection laws protect employees who report in good faith.

• A. Select Project Alpha, ROI is always the primary selection criterion and higher ROI wins
• B. Select Beta, ESG always overrides financial considerations in project selection
• C. An ESG-informed evaluation considers multiple dimensions: Alpha has higher financial ROI but only serves business efficiency; Beta has lower financial ROI but contributes to Social ESG (employee wellbeing, mental health, engagement) which may reduce turnover costs (replacing an employee costs 50-200% of annual salary), reduce absenteeism, and increase productivity, when these are quantified, Beta's total value may exceed Alpha's
• D. ESG considerations only apply after a project is selected, they should not influence project selection decisions

ESG-INFORMED PROJECT EVALUATION: ALPHA (Marketing Automation, ROI 180%): FINANCIAL VALUE: strong (180% ROI on direct marketing efficiency gains); ESG DIMENSION: limited, primarily a business efficiency tool; governance benefit from better marketing data quality; TOTAL VALUE: primarily financial; BETA (Employee Well-Being Platform, ROI 95%): FINANCIAL VALUE: 95% direct ROI; SOCIAL ESG VALUE (quantifiable): TURNOVER REDUCTION: if Beta reduces voluntary turnover by 5% (typical effect of well-being programs), and average replacement cost is $50K/employee: 500 employees × 5% turnover reduction × $50K = $1.25M in saved hiring costs annually; ABSENTEEISM REDUCTION: well-being programs typically reduce sick days by 1-2 days per employee annually; PRODUCTIVITY: engagement improvement has measurable productivity correlation; RECRUITMENT: organizations with strong ESG social programs attract talent more easily (important in tight labor markets); ADJUSTED TOTAL VALUE: when these social benefits are monetized, Beta's 'true' ROI may be 150-200%; GOVERNANCE BENEFIT: demonstrates organizational values alignment; SELECTION FRAMEWORK: both financial ROI and ESG value should be evaluated; QUANTIFY ESG VALUE where possible (the approach above); CONSIDER STRATEGIC ALIGNMENT: does the project advance the organization's stated ESG commitments?; CONSIDER ORGANIZATIONAL RISK: ignoring employee wellbeing in a burnout-prone industry is a talent retention risk.

• A. Ethical sourcing only applies to food and clothing industries, electronics procurement is unaffected
• B. Price is the only relevant criterion, ethical considerations drive up costs unnecessarily
• C. Ethical sourcing criteria for electronics procurement: conflict mineral due diligence (Section 1502 of Dodd-Frank requires disclosure of conflict minerals, tin, tantalum, tungsten, gold, from conflict regions); vendor labor practices (no child labor, forced labor, or unsafe working conditions throughout the supply chain); environmental manufacturing practices (RoHS compliance, restriction of hazardous substances; recycling programs); corporate social responsibility certifications; these are relevant because electronics supply chains often involve regions with known labor and conflict issues
• D. Ethical sourcing is enforced by governments, companies have no independent responsibility

ETHICAL SOURCING CRITERIA for electronics/IoT hardware: CONFLICT MINERALS (3TG. Tin, Tantalum, Tungsten, Gold): Dodd-Frank Section 1502 (US) and EU Conflict Minerals Regulation require disclosure and due diligence; these minerals are found in many electronic components (capacitors, circuit boards); some mining operations in conflict regions fund armed groups; VENDOR CRITERION: ask vendors to provide Conflict Minerals Reporting Template (CMRT); prefer vendors with Responsible Minerals Initiative (RMI) certification; LABOR PRACTICES IN SUPPLY CHAIN: ask vendors about their factory auditing programs; look for Social Accountability International (SA8000) certification or equivalents; no child labor (ILO Conventions); reasonable working hours (not forced excessive overtime); safe working conditions; ENVIRONMENTAL MANUFACTURING: RoHS Compliance: Restriction of Hazardous Substances (restricts lead, mercury, cadmium in electronics); WEEE (Waste Electrical and Electronic Equipment) compliance for disposal; manufacturer take-back programs for end-of-life hardware; SUSTAINABILITY CERTIFICATIONS: EPEAT (Electronic Product Environmental Assessment Tool); Energy Star; ISO 14001 (environmental management system). WHY RELEVANT: organizations face reputational risk if their supply chain is linked to labor abuses or conflict funding; regulatory reporting requirements are expanding; investors score organizations on supply chain ESG performance; doing the right thing is an organizational value.