Unit I -Introduction to Project Management

UpLearn ng
Project Management
 UpLearn ng

Disclamer

Notes are prepared by Uplearning for educational support only.


These are not official university/board materials.


Content is for personal use only — no reposting, reselling, or modification.


Accuracy is not guaranteed; refer to official syllabus & textbooks.


Uplearning is not responsible for academic results or losses.


By using this content, you agree to all rules & terms.

SPPU SECOND YEAR ( 2024 PATTERN )

Join Group
Visit Website
1.1 : PROJECT DEFINITION

1.1.1 What is a Project?

• A project is a temporary endeavor undertaken to create a unique product,

service, or result.
• It has a defined beginning and end in time, with specific objectives and
constraints.
• Projects are different from operations because operations are ongoing and
repetitive while projects are temporary and unique.
• Every project must have clear deliverables that meet specific requirements and
stakeholder expectations.

1.1.2 Characteristics of a Project

• Temporary Nature: Projects have a definite start and end date, unlike
ongoing business operations.
• Unique Deliverables: Each project produces a distinct product, service, or
result that has not been created before in the exact same way.
• Progressive Elaboration: Project details are developed and refined as the
project progresses and more information becomes available.
• Resource Constraints: Projects operate within limited resources including
time, budget, human resources, and materials.
• Specific Objectives: Projects aim to achieve predetermined goals and success
criteria.

1.1.3 Difference Between Project and Operations

Aspect Project Operations

Duration Temporary with defined start and Ongoing and continuous
end
Output Unique product or service Repetitive standardized outputs
Purpose Achieve specific objectives then Sustain business operations
close
Resources Allocated for project duration Permanent organizational
resources
Team Temporary project team Permanent operational team
1.1.4 Examples of Projects
• Developing a new software application or mobile app.
• Constructing a building, bridge, or infrastructure facility.
• Organizing a conference, event, or product launch.
• Implementing an ERP system in an organization.
• Conducting research and development for a new product.
1.2 : PROJECT LIFE CYCLE

1.2.1 Definition of Project Life Cycle

• Project life cycle is the series of phases that a project passes through from
initiation to closure.
• It provides a structured framework to manage and control project activities
systematically.
• The life cycle helps project managers organize work, allocate resources, and
monitor progress effectively.

1.2.2 Phases of Project Life Cycle

Phase 1: Initiation
• The project is formally authorized and the initial scope is defined.
• Project stakeholders are identified and their expectations are documented.
• A project charter is created that formally recognizes the existence of the
project.
• High-level risks, assumptions, and constraints are identified.
• Feasibility study is conducted to determine if the project is viable.
Phase 2: Planning
• Detailed project plans are developed to guide project execution and control.
• Project scope, schedule, cost, quality, resources, and risks are planned in
detail.
• Work Breakdown Structure (WBS) is created to decompose project
deliverables.
• Project management plan is finalized and approved by stakeholders.
• Communication plan, procurement plan, and risk management plan are
established.
Phase 3: Execution
• Project work is performed according to the project management plan.
• Project team members are acquired, developed, and managed.
• Project deliverables are created and quality standards are implemented.
• Stakeholder expectations are managed and communication is maintained.
• Procurement activities are conducted to obtain necessary resources and
services.
Phase 4: Monitoring and Controlling
• Project performance is measured and analyzed against the project
management plan.
• Changes are identified, evaluated, and approved or rejected through change
control process.
• Corrective and preventive actions are taken to keep the project on track.
• Project scope, schedule, cost, quality, and risks are continuously monitored.
• Progress reports are generated and communicated to stakeholders.
Phase 5: Closing
• Project deliverables are formally accepted by the customer or sponsor.
• All project documentation is completed, archived, and handed over.
• Contracts are closed and final payments are processed.
• Lessons learned are documented for future project improvement.
• Project resources are released and the project is formally closed.

1.2.3 Characteristics of Project Life Cycle

• Cost and staffing levels are low at the start: Resources gradually increase
during planning and execution phases.
• Peak during execution phase: Maximum resources and budget are
consumed during the execution phase.
• Drop rapidly near closure: Resources are released as deliverables are
completed and accepted.
• Stakeholder influence is highest at the beginning: Early phases allow more
flexibility to make changes.
• Risk and uncertainty are highest at the start: Decreases as the project
progresses and clarity increases.
1.3 : PROCESSES AND KNOWLEDGE AREAS IN PROJECT
MANAGEMENT

1.3.1 Project Management Processes

• Project management processes are systematic activities performed to achieve

project objectives.
• PMBOK recognizes five process groups that organize project management
activities.

Five Process Groups:

1. Initiating Process Group

• Processes performed to define a new project or phase and obtain
authorization to start.
• Key processes include developing project charter and identifying stakeholders.
2. Planning Process Group
• Processes required to establish the scope, refine objectives, and define actions
to achieve goals.
• Key processes include developing project management plan and creating
WBS.
3. Executing Process Group
• Processes performed to complete the work defined in the project
management plan.
• Key processes include directing project work, managing team, and managing
stakeholder engagement.
4. Monitoring and Controlling Process Group
• Processes required to track, review, and regulate project progress and
performance.
• Key processes include monitoring project work, performing integrated change
control, and controlling scope, schedule, and costs.
5. Closing Process Group
• Processes performed to formally complete or close the project or phase.
• Key processes include closing project or phase and closing procurements.
1.3.2 Ten Knowledge Areas in Project Management

1. Project Integration Management

• Coordinates all aspects of the project and ensures that all elements work
together effectively.
• Key processes include developing project charter, project management plan,
and performing integrated change control.
2. Project Scope Management
• Ensures that the project includes all the work required and only the work
required to complete successfully.
• Key processes include collecting requirements, defining scope, creating WBS,
and controlling scope.
3. Project Schedule Management
• Manages timely completion of the project through proper planning and
control of project timeline.
• Key processes include defining activities, sequencing activities, estimating
durations, and developing and controlling schedule.
4. Project Cost Management
• Plans, estimates, budgets, finances, funds, manages, and controls costs to
complete the project within approved budget.
• Key processes include estimating costs, determining budget, and controlling
costs.
5. Project Quality Management
• Ensures that project deliverables meet the required quality standards and
customer expectations.
• Key processes include planning quality, managing quality, and controlling
quality.
6. Project Resource Management
• Identifies, acquires, and manages resources needed for successful project
completion.
• Key processes include planning resource management, estimating activity
resources, acquiring resources, and managing team.
7. Project Communications Management
• Ensures timely and appropriate generation, collection, distribution, and
storage of project information.
• Key processes include planning communications, managing communications,
and monitoring communications.
8. Project Risk Management
• Conducts risk management planning, identification, analysis, response
planning, and control on a project.
• Key processes include planning risk management, identifying risks, performing
risk analysis, planning risk responses, and controlling risks.
9. Project Procurement Management
• Manages processes to purchase or acquire products, services, or results from
outside the project team.
• Key processes include planning procurement, conducting procurements, and
controlling procurements.
10. Project Stakeholder Management
• Identifies people, groups, or organizations that could impact or be impacted
by the project.
• Key processes include identifying stakeholders, planning stakeholder
engagement, managing stakeholder engagement, and monitoring stakeholder
engagement.

1.3.3 Relationship Between Process Groups and Knowledge Areas

• Each knowledge area contains processes that may fall into different process
groups.
• For example, Scope Management includes processes in Initiating, Planning,
and Monitoring & Controlling groups.
• Understanding this relationship helps project managers organize and execute
project activities systematically.
1.4 : WORK BREAKDOWN STRUCTURE (WBS)

1.4.1 Definition of WBS

• WBS is a hierarchical decomposition of the total scope of work to be carried

out by the project team.
• It breaks down project deliverables into smaller, more manageable
components called work packages.
• WBS organizes and defines the total scope of the project in a structured
manner.
• Each descending level represents an increasingly detailed definition of project
work.

1.4.2 Purpose and Benefits of WBS

• Clarifies project scope: Provides clear understanding of what is included and

excluded from the project.
• Facilitates planning: Helps in estimating cost, time, and resource
requirements accurately.
• Improves communication: Provides common understanding of project scope
among team members and stakeholders.
• Enables better control: Allows monitoring and controlling of project work at
detailed level.
• Assigns responsibilities: Facilitates assignment of work packages to team
members clearly.
• Identifies deliverables: Ensures all project deliverables are identified and
accounted for.

1.4.3 Components of WBS

Work Package
• The lowest level of the WBS where cost and schedule can be reliably
estimated.
• A work package represents a deliverable or work component assigned to a
single person or team.
• It should be small enough to be manageable but large enough to avoid
excessive detail.
Control Account
• A management control point where scope, budget, actual cost, and schedule
are integrated.
WBS Dictionary
• A document that provides detailed information about each WBS component.
• Includes description of work, responsible person, schedule milestones, quality
requirements, and acceptance criteria.

1.4.4 Creating WBS - Decomposition Process

Step 1: Identify Major Deliverables

• Start with the final project deliverable or product at the top level.
• Identify major deliverables and subcomponents required to complete the
project.
Step 2: Decompose into Smaller Components
• Break down major deliverables into smaller, more detailed components.
• Continue decomposition until work packages are defined at manageable level.
Step 3: Verify Completeness
• Ensure that all project work is captured in the WBS.
• Check that lower-level components logically roll up to higher levels.
Step 4: Assign Identification Codes
• Assign unique identifiers to each WBS component for tracking purposes.
• Common coding systems include 1.0, 1.1, 1.1.1 hierarchical numbering.

1.4.5 Types of WBS

1. Deliverable-Based WBS
• Organized around project deliverables and outputs.
• Each branch represents a major deliverable or product component.
• Most commonly used approach as it focuses on what the project will produce.
• Example: For software project - User Interface, Database, Backend Logic,
Testing Documentation.
2. Phase-Based WBS
• Organized around project phases or life cycle stages.
• Each branch represents a phase of the project such as Design, Development,
Testing, Deployment.
• Useful when project phases are distinct and deliverables are phase-specific.
• Example: Initiation Phase, Planning Phase, Execution Phase, Closure Phase.
3. Responsibility-Based WBS (Organizational WBS)
• Organized according to organizational units or teams responsible for the
work.
• Each branch represents work assigned to specific departments or teams.
• Useful for large projects with multiple organizational units involved.
• Example: Marketing Team Tasks, Development Team Tasks, Quality Assurance
Team Tasks.

1.4.6 Rules for Creating Effective WBS

• 100% Rule: The WBS must include 100% of the work defined by the project
scope.
• Mutually Exclusive: Work packages should not overlap; each should
represent distinct work.
• Outcome Oriented: Focus on deliverables and outcomes rather than activities
or actions.
• Appropriate Level of Detail: Decompose to a level where work can be
estimated and managed effectively.
• Use Nouns: WBS elements should be described using nouns, not verbs, as
they represent deliverables.

1.4.7 Example of WBS Structure

Project: E-Commerce Website Development
1.0 E-Commerce Website
1.1 Project Management
1.1.1 Project Planning
1.1.2 Project Monitoring
1.2 Requirements Analysis
1.2.1 User Requirements
1.2.2 System Requirements
1.3 Design
1.3.1 UI/UX Design
1.3.2 Database Design
1.3.3 Architecture Design
1.4 Development
1.4.1 Frontend Development
1.4.2 Backend Development
1.4.3 Database Implementation
1.5 Testing
1.5.1 Unit Testing
1.5.2 Integration Testing
1.5.3 User Acceptance Testing
1.6 Deployment
1.6.1 Server Setup
1.6.2 Application Deployment
1.7 Documentation
1.7.1 User Manual
1.7.2 Technical Documentation
1.5 : INTRODUCTION TO PMBOK
(PROJECT MANAGEMENT BODY OF KNOWLEDGE)

1.5.1 What is PMBOK?

• PMBOK is a globally recognized standard developed by Project Management
Institute (PMI).
• It provides guidelines, best practices, and standardized terminology for project
management.
• PMBOK is not a methodology but a framework that can be adapted to
different project environments.
• The guide is updated periodically to reflect evolving project management
practices.

1.5.2 Purpose of PMBOK

• Standardization: Provides common language and framework for project
management professionals worldwide.
• Best Practices: Documents proven practices that are generally accepted as
good project management practices.
• Knowledge Base: Serves as reference guide for project managers across all
industries and domains.
• Professional Development: Forms the basis for PMI certifications like PMP
(Project Management Professional).

1.5.3 Structure of PMBOK Guide

• Process Groups: Organizes 49 project management processes into 5 process
groups (Initiating, Planning, Executing, Monitoring & Controlling, Closing).
• Knowledge Areas: Organizes processes into 10 knowledge areas based on
subject matter (Integration, Scope, Schedule, Cost, Quality, Resource,
Communications, Risk, Procurement, Stakeholder).
• Process Mapping: Each process is mapped to a specific process group and
knowledge area.
1.5.4 Key Components of PMBOK Framework

Inputs, Tools & Techniques, Outputs (ITTO)

• Inputs: Information, documents, or items required to perform a process.
• Tools & Techniques: Methods, practices, or approaches used to transform
inputs into outputs.
• Outputs: Documents, products, or results produced by a process.
Project Management Plan
• Comprehensive document that describes how the project will be executed,
monitored, and controlled.
• Integrates all subsidiary plans including scope, schedule, cost, quality,
resource, communications, risk, procurement, and stakeholder management
plans.
Project Documents
• Various documents created and used throughout the project such as
requirements documentation, risk register, stakeholder register, issue log, and
lessons learned.

1.5.5 Benefits of Using PMBOK

• Provides systematic approach to managing projects from initiation to closure.
• Improves project success rate by applying proven best practices.
• Facilitates communication among project stakeholders using standard
terminology.
• Helps organizations develop consistent project management practices.
• Supports professional development and career advancement in project
management.

1.5.6 PMBOK Principles (PMBOK 7th Edition)

• Stewardship: Be a diligent, respectful, and caring steward.
• Team: Create a collaborative project team environment.
• Stakeholders: Effectively engage with stakeholders.
• Value: Focus on value delivery throughout the project.
• Systems Thinking: Recognize, evaluate, and respond to system interactions.
• Leadership: Demonstrate leadership behaviors.
• Tailoring: Tailor project approach based on context.
• Quality: Build quality into processes and deliverables.
• Complexity: Navigate complexity throughout the project.
• Risk: Optimize risk responses.
1.6 : PORTFOLIO MANAGEMENT

1.6.1 Definition of Portfolio Management

• Portfolio management is the centralized management of one or more
portfolios to achieve strategic organizational objectives.
• A portfolio is a collection of projects, programs, subsidiary portfolios, and
operations managed as a group.
• Portfolio components are selected and prioritized based on their alignment
with organizational strategy.
• Portfolio management ensures optimal resource allocation across multiple
initiatives.

1.6.2 Difference Between Project, Program, and Portfolio

Aspect Project Program Portfolio
Definition Temporary Group of related Collection of
endeavor to create projects managed in projects, programs,
unique deliverable coordinated way and operations
Scope Narrow and Broad covering Entire organizational
specific multiple projects strategy
Focus Deliver specific Achieve program Achieve strategic
deliverables benefits objectives
Success Meeting scope, Delivery of benefits Return on
Measurement time, cost, quality and capabilities investment and
strategic alignment
Management Detailed planning Coordination and Strategic alignment
Style and control governance and prioritization
Change Project managers Program managers Portfolio managers
work to minimize expect and manage monitor aggregate
changes changes changes

1.6.3 Components of Portfolio Management

Projects
• Individual temporary initiatives undertaken to create specific deliverables.
• Selected for inclusion based on strategic value and alignment.
Programs
• Groups of related projects managed together to obtain benefits not available
from managing individually.
• Coordinated to support strategic objectives.
Operations
• Ongoing organizational activities that sustain the business.
• May be included in portfolio when they impact strategic objectives.

1.6.4 Portfolio Management Process

Step 1: Identification
• Identify all potential projects, programs, and operational initiatives.
• Categorize components based on type, strategic alignment, and business
objectives.
Step 2: Evaluation
• Assess each component against strategic criteria and business value.
• Analyze risks, resource requirements, costs, and expected benefits.
• Score and rank components based on evaluation criteria.
Step 3: Selection
• Select optimal mix of components that maximize strategic value within
resource constraints.
• Balance portfolio to ensure diversification and risk management.
• Approve selected components for resource allocation.
Step 4: Prioritization
• Prioritize approved components based on strategic importance and urgency.
• Allocate resources to high-priority initiatives first.
• Create implementation roadmap for portfolio execution.
Step 5: Authorization
• Formally authorize selected and prioritized components to proceed.
• Allocate budgets, resources, and assign accountability.
Step 6: Monitoring and Control
• Monitor portfolio performance against strategic objectives.
• Track resource utilization, costs, benefits realization, and risks.
• Conduct periodic portfolio reviews to assess alignment and performance.
Step 7: Balancing
• Continuously balance the portfolio by adding, removing, or reprioritizing
components.
• Adjust resource allocation based on changing business priorities.
1.6.5 Benefits of Portfolio Management

• Strategic Alignment: Ensures all initiatives support organizational strategy

and objectives.
• Optimized Resource Utilization: Allocates limited resources to highest value
initiatives.
• Risk Management: Balances portfolio to diversify risks across initiatives.
• Improved Decision Making: Provides visibility into all initiatives for informed
decisions.
• Maximized Value: Selects and prioritizes initiatives that deliver maximum
business value.
• Better Governance: Establishes consistent governance framework across all
initiatives.

1.6.6 Portfolio Management vs Project Management

• Portfolio Management focuses on doing the right projects that align with
strategy.
• Project Management focuses on doing projects right by delivering them
successfully.
• Portfolio managers select which projects to fund while project managers
execute approved projects.
• Portfolio management is strategic while project management is tactical.
1.7 : TRADITIONAL VS MODERN PROJECT MANAGEMENT USING PMBOK
CONCEPT

1.7.1 Traditional Project Management (Waterfall Approach)

Characteristics of Traditional Approach

• Sequential Phases: Project progresses through distinct phases in linear
sequence - Requirements, Design, Development, Testing, Deployment.
• Detailed Upfront Planning: Comprehensive planning is completed before
execution begins.
• Fixed Scope: Project scope is defined completely at the beginning and
changes are controlled strictly.
• Predictive Nature: Assumes that all requirements can be known in advance.
• Documentation Heavy: Emphasizes extensive documentation at each phase.
• Limited Customer Involvement: Customer involvement is primarily at the
beginning and end of the project.

When to Use Traditional Approach

• When project requirements are clear, well-defined, and unlikely to change.
• When the project deliverable is well understood and has been done before.
• When regulatory or contractual requirements demand detailed
documentation.
• For construction, manufacturing, or infrastructure projects with fixed
specifications.

Advantages of Traditional Approach

• Clear structure and well-defined phases make project easy to understand and
manage.
• Detailed documentation provides comprehensive project records.
• Works well for projects with stable requirements and proven technology.
• Easy to measure progress against predefined milestones.

Disadvantages of Traditional Approach

• Inflexible to changes once project is in execution phase.
• Customer sees the final product only at the end, leading to potential
misalignment.
• High risk if requirements are misunderstood initially.
• Not suitable for projects where requirements evolve or technology changes
rapidly.
1.7.2 Modern Project Management (Agile and Adaptive Approaches)

Characteristics of Modern Approach

• Iterative and Incremental: Project is divided into small iterations or sprints

that deliver working increments.
• Adaptive Planning: Planning is done progressively as the project evolves and
more is learned.
• Flexible Scope: Scope can be adjusted based on feedback and changing
requirements.
• Continuous Customer Involvement: Customer is actively involved
throughout the project providing regular feedback.
• Working Software over Documentation: Focuses on delivering working
product rather than comprehensive documentation.
• Collaborative Teams: Emphasizes self-organizing, cross-functional teams with
daily collaboration.

When to Use Modern Approach

• When requirements are uncertain, unclear, or likely to change frequently.
• For software development projects requiring rapid delivery and flexibility.
• When customer needs quick, incremental delivery of value.
• For innovative projects in rapidly changing technology environments.

Advantages of Modern Approach

• Highly flexible and responsive to changing requirements and market
conditions.
• Delivers value incrementally, allowing early realization of benefits.
• Continuous customer feedback ensures product meets actual needs.
• Reduces risk of project failure by validating assumptions early.
• Encourages team collaboration and innovation.

Disadvantages of Modern Approach

• Requires high customer involvement which may not always be feasible.
• Less predictable in terms of final scope, cost, and timeline.
• Requires cultural shift and mindset change in traditional organizations.
 1.7.3 Comparison: Traditional vs Modern Project Management

Aspect Traditional (Waterfall) Modern (Agile)

Approach Predictive and plan-driven Adaptive and iterative
Planning Detailed upfront planning Progressive elaboration
Scope Fixed, changes controlled Flexible, changes welcomed
Customer Limited to start and end Continuous throughout
Involvement
Delivery Single delivery at end Incremental deliveries
Documentation Comprehensive and detailed Minimal, just sufficient
Team Structure Hierarchical with defined roles Self-organizing, cross-
functional
Risk Management Risk identified upfront Continuous risk assessment
Success Measurement Adherence to plan Customer satisfaction and
value
Best For Stable requirements, proven solutions Evolving requirements,
innovation

1.7.4 PMBOK's Perspective on Traditional vs Modern

• PMBOK recognizes that project management is not one-size-fits-all.
• Organizations should tailor their approach based on project context,
requirements, and environment.
• Predictive (Traditional) Life Cycle is appropriate when scope can be defined
early and changes are limited.
• Adaptive (Modern) Life Cycle is suitable when requirements are uncertain
and need to evolve.
• Hybrid Approaches combine elements of both traditional and modern
methods based on project needs.

1.7.5 Hybrid Approach

• Combines traditional and modern practices to leverage benefits of both
approaches.
• Uses predictive planning for well-defined components and adaptive approach
for uncertain areas.
• Example: Infrastructure project may use waterfall for construction while using
agile for software integration.
• Allows organizations to customize project management approach based on
specific project characteristics.
1.7.6 Tailoring Project Management Approach

• Project Complexity: Complex projects with many unknowns benefit from

adaptive approaches.
• Requirement Stability: Stable requirements favor predictive, changing
requirements favor adaptive.
• Organizational Culture: Organization's readiness to adopt new practices
influences approach selection.
• Regulatory Environment: Compliance requirements may necessitate
traditional documentation and controls.
• Team Experience: Team familiarity with specific approaches affects
implementation success.
• Customer Preferences: Customer expectations and involvement capacity
influence approach choice.

1.7.7 Evolution from Traditional to Modern

• Traditional project management evolved from manufacturing and construction
industries.
• Modern approaches emerged from software industry's need for flexibility and
rapid delivery.
• PMBOK has evolved to incorporate both approaches recognizing the value of
flexibility.
• Today's project managers must be proficient in multiple approaches and know
when to apply each.
15 MOST IMPORTANT EXAM QUESTIONS FOR UNIT 1

SHORT ANSWER QUESTIONS (2-5 MARKS)

1. Define a project and list its key characteristics.
2. Differentiate between a project and operations with suitable examples.
3. Explain the five phases of project life cycle.
4. What is Work Breakdown Structure (WBS)? State its purpose.
5. List and explain any five knowledge areas in project management.

MEDIUM ANSWER QUESTIONS (5-10 MARKS)

6. Explain the five process groups in project management with their key
activities.
7. Describe the types of WBS with suitable examples.
8. What is PMBOK? Explain its structure and benefits.
9. Differentiate between Project, Program, and Portfolio with examples.
10. Explain the portfolio management process in detail.

LONG ANSWER QUESTIONS (10-15 MARKS)

11. Explain the project life cycle phases in detail with their characteristics and key
activities.
12. Describe any five knowledge areas in project management and explain how
they contribute to project success.
13. What is Work Breakdown Structure? Explain the process of creating WBS with
a suitable example.
14. Compare and contrast Traditional (Waterfall) and Modern (Agile) project
management approaches. When would you use each approach?
15. Explain portfolio management in detail. Discuss its benefits and how it differs
from project management.
 n i e p
a r p L U in
L e U n g rn
p g n i e a
in r L
UNIT 3 – Blockchain, Cryptocurrencies & DeFi

g a p
(VERY IMPORTANT – CONCEPT + DIAGRAM BASED)

n
Course Combo Pack (notes + At Just

n r e U
MOST GUARANTEED LONG QUESTIONS

n i
1. imp
a
ExplainQ's )

Blockchain

p L
technology with its features and block structure.

₹159
r e ₹199
2. Explain cryptographic techniques used in blockchain.

a L U
3. Explain Smart Contracts and their applications.

g
UNLOCK ALL SUBJECT UNITS

p
4. Explain Decentralized Finance (DeFi) and its advantages.

g in
5. Explain cryptocurrencies
CLICK ON BUTTON TO VISTand their key features.

U
WEBSITE

in n e
 

n r L
VERY IMPORTANT MEDIUM QUESTIONS

g r a p
6. Explain types of blockchain.

in a e U
7. Explain consensus mechanisms (PoW and PoS).

Elective Subject (notes + imp At Just

e L
8. Explain applications of blockchain in finance.

9.

rnQ's
L p
)
 CBDC and its importance.

Explain

p ₹79 ₹49
g
a U n
10. Explain disruptive potential of blockchain in global finance.

e U i
 

L g n
UNLOCK ALL SUBJECT UNITS

r
VERY COMMON DIFFERENCE QUESTIONS

p n a
· Blockchain vsONTraditional database

i
CLICK BUTTON TO VIST WEBSITE

e
· Cryptocurrency vs CBDC

g rn
DeFi vs Traditional finance

n L p
g a p
· PoW vs PoS

in
·

i e
Public vs Private blockchain

n U U
r L
 

rn a p
SHORT QUESTIONS (2 Marks)

e
· Define Blockchain

L U
Define Smart Contract

g
p
· What is DeFi?
Purchase to Access Premium Content

g n r
· What is cryptocurrency?

U · What is hashing?

g in n i e a
n r
· Name any two cryptocurrenciesVERY IMPORTANT MEDIUM QUESTIONS

n r a L
6. Explain algorithmic trading and high-frequency trading.

7.

n i a e p
Explain sentiment analysis and its role in investment decisions.

e
r L U
8. Explain AI-driven portfolio management.

a L p
9. Explain role of AI in digital lending and wealth management.

e p g
10. Explain RegTech and its importance.

L U U i
UNIT 4 – AI, Machine Learning & Financial Analytics

n
g n
(SCORING + EASY THEORY)

r
MOST GUARANTEED LONG QUESTIONS

1.

in a
Explain applications of AI and ML in finance.

g n e
Explain predictive analytics in stock markets and trading

in g in a r p L
n rn L e U g
e a p in
p L U rn
U a
 FOR NOTES & UPDATES FOR NOTES & UPDATES
UpLearning
Click

Click
Want to Purchase or download Notes , vist out website!
ClickTo

Click to
to Join
To Join
Contact us on +919049988617 | contact@[Link]
Join

Join
Stay Connected &(Updated with us...!
Grou Grou

Telegram Channel for SPPU Second Year ( 2024 Pattern ) WhatsApp Group for SPPU Second Year ( 2024 Pattern )
ChanneChanne
© 2025 Uplearning(Uplearning , Maharashtra , Pune([Link]
SPPU SECOND YEAR ( 2024 PATTERN ) SPPU SECOND YEAR ( 2024 PATTERN )
SPPU SECOND YEAR ( 2024 PATTERN )
CLICK ON QR TO VIST WEBSITE
website
vist out
Want to
Purchase or
download Notes