Here is the complete, exhaustive study guide for Software Project Management (BCA 363).
Every single non-MCQ question from your provided exam papers has been extracted, merged
for repetitions, and formatted exactly to your point rules.
(Press Ctrl + P to save this section as a PDF!)
📊 THE ULTIMATE BCA 363: SOFTWARE
PROJECT MANAGEMENT STUDY GUIDE
🟢 SECTION A: 1-Mark Definitions (2 Points Each)
Q: What is a communication plan? (Repeated 3 times)
1. A communication plan outlines how project information will be distributed to
stakeholders.
2. It defines who receives what information, when, and through which specific
communication channels.
Q: Define PDM (Precedence Diagram Method). (Repeated 3 times)
1. PDM is a visual network diagramming technique using boxes (nodes) to represent project
activities.
2. It connects these nodes with arrows to show the logical sequential dependencies
between tasks.
Q: List out the phases in scrum. (Repeated 2 times)
1. The Scrum framework generally consists of Sprint Planning, Daily Scrum, Sprint Review,
and Sprint Retrospective.
2. It begins with creating a Product Backlog and ends with a potentially shippable product
increment.
Q: Define Backward Pass Method. (Repeated 2 times)
1. It is a critical path calculation technique used to determine the latest start and finish
times for project activities.
2. It works by moving backward through the network diagram from the project's end date.
Q: What is Dependency? (Repeated 2 times)
1. A dependency is a logical relationship where the start or completion of one task relies on
another task.
2. Examples include Finish-to-Start (FS) and Start-to-Start (SS) relationships.
Q: What is staffing in project management? (Repeated 2 times)
1. Staffing involves acquiring, deploying, and retaining the right human resources for a
project.
2. It ensures team members have the appropriate technical and soft skills required to
complete their assigned tasks.
Q: Define activity scheduling. (Repeated 1 time)
1. Activity scheduling is the process of determining the exact start and finish dates for
individual project tasks.
2. It ensures resources are allocated efficiently to meet the overall project deadline.
Q: List the attributes of a project. (Repeated 1 time)
1. A project is temporary (has a defined start and end), unique, and requires coordinated
resources.
2. It operates under constraints of time, cost, and scope (the project management triangle).
Q: What is cost estimation? (Repeated 1 time)
1. Cost estimation is the process of predicting the financial resources needed to complete
a project.
2. It accounts for labor, materials, equipment, and potential risk contingencies.
Q: What is a sprint? (Repeated 1 time)
1. A sprint is a short, time-boxed period (usually 1-4 weeks) in Agile where a specific set of
work must be completed.
2. Sprints provide a regular cadence for delivering iterative product increments to the client.
Q: Define timeline. (Repeated 1 time)
1. A timeline is a visual representation of project events and tasks arranged chronologically.
2. It provides a clear overview of the project's schedule from initiation to formal closure.
Q: What is an activity? (Repeated 1 time)
1. An activity is a distinct, scheduled component of work performed during the course of a
project.
2. Activities consume time and resources and produce measurable deliverables.
Q: What is a time band? (Repeated 1 time)
1. A time band represents a specific allocated period within which a particular task or phase
must occur.
2. It helps managers track if activities are being completed within acceptable schedule
limits.
Q: Define portfolio management. (Repeated 1 time)
1. Portfolio management is the centralized administration of one or more project portfolios
to achieve strategic objectives.
2. It focuses on selecting, prioritizing, and controlling projects to maximize return on
investment.
Q: What is project planning? (Repeated 1 time)
1. Project planning is the phase where the project scope, objectives, and course of action
are thoroughly defined.
2. It results in a comprehensive project management plan that guides execution and
control.
Q: What is risk management? (Repeated 1 time)
1. Risk management is the systematic process of identifying, analyzing, and responding to
project risks.
2. Its goal is to maximize the probability of positive events and minimize the impact of
negative ones.
Q: What is a slip chart? (Repeated 1 time)
1. A slip chart is a visual project tracking tool used to compare the planned schedule against
actual progress.
2. It helps managers easily identify which specific tasks are slipping behind their original
deadlines.
Q: Define iterations. (Repeated 1 time)
1. Iterations are repetitive cycles of development used in Agile methodologies.
2. Each iteration refines the product, adding new features based on continuous user
feedback.
🟡 SECTION B: 3-Mark Questions (6 Points Each)
Q: Differentiate between predictive process and empirical process. (Repeated 4 times)
1. A predictive process (like Waterfall) assumes that the project can be planned entirely in
advance.
2. It relies on historical data and defined steps to predict exact timelines and budgets.
3. Predictive processes work best when requirements are crystal clear and technology is
well understood.
4. An empirical process (like Scrum) acknowledges that software development is inherently
unpredictable.
5. It relies on the three pillars of transparency, inspection, and adaptation to guide the
project dynamically.
6. Empirical processes work best in complex, rapidly changing environments where learning
occurs through trial and error.
Q: Write a note on PMBOK. (Repeated 3 times)
1. PMBOK stands for the Project Management Body of Knowledge, curated by the Project
Management Institute (PMI).
2. It serves as the internationally recognized standard and foundational guide for project
management professionals.
3. It divides project management into five distinct process groups: Initiating, Planning,
Executing, Monitoring, and Closing.
4. It further categorizes management practices into ten knowledge areas, such as Scope,
Cost, and Quality.
5. It provides a common vocabulary and standardized best practices for managers across
all industries.
6. It is not a rigid methodology, but rather a flexible framework that can be adapted to
specific projects.
Q: Explain how to manage people / select staff. (Repeated 3 times)
1. Managing people involves understanding organizational behavior, motivation, and team
dynamics.
2. It requires effective leadership, clear communication, and conflict resolution skills to
maintain high morale.
3. Selecting staff begins with a clear definition of the roles and technical skills required for
the project.
4. Managers must assess candidates based on both hard skills (coding, design) and soft
skills (teamwork, communication).
5. The selection process often includes reviewing resumes, conducting technical interviews,
and administering ability tests.
6. Once selected, staff must be properly onboarded, trained, and aligned with the project's
overall goals.
Q: Describe the importance of activity scheduling. (Repeated 3 times)
1. Activity scheduling provides a clear, sequential roadmap for the entire project team to
follow.
2. It ensures that finite resources (personnel, equipment) are allocated at the exact time
they are needed.
3. It highlights dependencies, showing which tasks must be completed before others can
legally or logically begin.
4. It identifies the critical path, allowing managers to know exactly which delayed tasks will
delay the whole project.
5. It establishes a baseline that allows stakeholders to monitor progress and identify
schedule slips early.
6. It facilitates better communication and coordination between different departments
working on the same project.
Q: Describe CPN (Constructing Precedence Networks) with an example. (Repeated 2
times)
1. CPN is a method of creating a project schedule network diagram using the
Activity-on-Node (AON) format.
2. Each rectangular node represents a specific project activity, displaying its ID and
duration.
3. Directional arrows connect the nodes to illustrate the logical sequence and
dependencies of work.
4. It easily accommodates four types of dependencies: FS, SS, FF, and SF.
5. It eliminates the need for "dummy activities" which were common in older Arrow
Diagramming Methods (ADM).
6. Example: Node A (Gather Requirements) connects to Node B (Design UI) via a
Finish-to-Start arrow.
Q: Compare Agile and Non-Agile (Traditional) projects. (Repeated 2 times)
1. Non-Agile projects follow a rigid, sequential "Waterfall" approach where phases do not
overlap.
2. Agile projects use an iterative and incremental approach, delivering software in small,
usable cycles (sprints).
3. Non-Agile requires exhaustive, finalized documentation and fixed requirements before
any coding begins.
4. Agile welcomes changing requirements even late in development to maximize customer
competitive advantage.
5. Non-Agile features heavy upfront planning, making it difficult to pivot if market conditions
change.
6. Agile relies on continuous customer collaboration, daily team meetings, and frequent
feedback loops.
Q: Explain cost control in project management. (Repeated 2 times)
1. Cost control is the practice of monitoring project expenses to ensure they align with the
approved budget baseline.
2. It involves measuring the actual costs incurred against the planned costs at regular
intervals.
3. It uses techniques like Earned Value Management (EVM) to forecast final project costs
based on current performance.
4. Project managers must identify the root causes of any cost variances (overspending or
underspending).
5. It requires implementing a formal change control system to prevent unauthorized scope
creep from inflating costs.
6. Effective cost control prevents project failure by ensuring financial resources are not
depleted prematurely.
Q: Discuss the project Life Cycle in detail. (Repeated 2 times)
1. The project life cycle represents the series of phases a project passes through from start
to finish.
2. Initiation Phase: The project is defined, feasibility is assessed, and the project charter is
formally approved.
3. Planning Phase: Detailed schedules, budgets, risk plans, and resource allocations are
fully developed.
4. Execution Phase: The actual work is performed by the team to create the project
deliverables.
5. Monitoring and Controlling: Progress is tracked against the plan, and corrective actions
are taken if necessary.
6. Closure Phase: Deliverables are handed over to the client, contracts are closed, and
lessons learned are documented.
Q: What is health and safety management? (Repeated 2 times)
1. Health and safety management involves identifying and mitigating workplace hazards to
protect project personnel.
2. In software management, it primarily focuses on ergonomic issues, mental health, and
preventing burnout.
3. It requires ensuring proper workstation setups (chairs, monitors) to prevent repetitive
strain injuries.
4. Managers must monitor workload to prevent excessive overtime that leads to severe
stress and fatigue.
5. A safe environment promotes higher productivity, reduces absenteeism, and minimizes
costly employee turnover.
6. Organizations have legal and ethical obligations to comply with occupational health and
safety regulations.
🟠 SECTION C: 4-Mark Questions (8 Points Each)
Q: What are the Roles and Responsibility of an agile/software development team?
(Repeated 5 times)
1. Agile teams are cross-functional, meaning they contain all the skills necessary to deliver
the product (developers, testers, designers).
2. They are self-organizing, meaning the team decides how to accomplish the work rather
than being told by a manager.
3. The Product Owner: Responsible for maximizing product value and strictly managing
the Product Backlog.
4. The Product Owner represents the customer's voice and defines the absolute
acceptance criteria for user stories.
5. The Scrum Master: Acts as a servant-leader, ensuring the team understands and follows
Agile theory and practices.
6. The Scrum Master physically removes impediments or roadblocks that are slowing the
development team down.
7. The Development Team: Responsible for physically building the software, writing code,
and testing features.
8. The team must deliver a potentially releasable, high-quality product increment at the end
of every single sprint.
Q: What is a Gantt chart? Explain with example. (Repeated 4 times)
project management concept
1. A Gantt chart is a widely used horizontal bar chart that visually represents a project
schedule over time.
2. The vertical axis on the left lists all the specific activities or work packages required for
the project.
3. The horizontal axis across the top represents the project timeline (days, weeks, or
months).
4. Each activity is represented by a horizontal bar whose length corresponds directly to the
task's duration.
5. The left end of the bar marks the task's start date, while the right end marks its expected
finish date.
6. Gantt charts easily display overlapping tasks, allowing managers to see what work is
happening simultaneously.
7. Modern software allows linking these bars with arrows to visually represent task
dependencies (e.g., Task B starts when Task A ends).
8. Example: A bar for "Database Design" runs from Week 1 to Week 3, followed immediately
by a bar for "Database Implementation" from Week 3 to Week 5.
Q: Write a detailed note on build or buy decision. (Repeated 2 times)
1. The "build or buy" decision is a strategic choice regarding whether to develop software
internally or purchase commercial off-the-shelf (COTS) software.
2. Building (Custom Development): Allows for a tailored solution that fits the
organization's unique business processes perfectly.
3. Building provides absolute control over the source code, intellectual property, security,
and future feature upgrades.
4. However, building is generally much more expensive, time-consuming, and carries higher
development risks.
5. Buying (COTS): Offers immediate deployment, significantly reducing the time required
to implement a solution.
6. Buying is usually cheaper upfront and includes professional support and maintenance
directly from the vendor.
7. However, buying may require the organization to alter its business processes to fit how
the purchased software works.
8. Organizations must analyze total cost of ownership, strategic value, and internal technical
capability before deciding.
Q: Explain types of dependency in detail. (Repeated 2 times)
1. Dependencies define the logical sequence in which project activities must be executed.
2. Finish-to-Start (FS): The most common type; Task B cannot start until Task A has
completely finished. (e.g., You cannot test code until it is written).
3. Start-to-Start (SS): Task B cannot start until Task A has started. They can run
concurrently. (e.g., Code writing and unit test writing can start at the same time).
4. Finish-to-Finish (FF): Task B cannot finish until Task A has finished. (e.g., Writing a user
manual cannot finish until the software coding finishes).
5. Start-to-Finish (SF): Rare type; Task B cannot finish until Task A has started. (e.g., The old
server cannot be shut down until the new server starts up).
6. Mandatory Dependencies: Inherent to the work being done, also called "hard logic"
(e.g., you must build a database before you query it).
7. Discretionary Dependencies: Defined by the project team based on best practices, also
called "soft logic".
8. External Dependencies: Involve relationships between project activities and external,
non-project activities (e.g., waiting for App Store approval).
🔴 SECTION D: 5-Mark Questions (10 Points Each)
Q: Define WBS and explain its types with the help of a diagram. (Repeated 4 times)
1. WBS (Work Breakdown Structure) is a hierarchical, deliverable-oriented decomposition of
the total project scope.
2. It breaks down massive, complex projects into smaller, easily manageable components
called "work packages."
3. The primary goal is to make cost estimation, scheduling, and resource allocation highly
accurate.
4. It provides a clear visual representation (drawn like an organizational family tree chart) of
all required project deliverables.
5. The 100% Rule applies: the WBS must capture all work required, and absolutely nothing
outside the WBS is part of the project.
6. Phase-based WBS: Divides the project sequentially by its lifecycle phases (e.g., Level 1 is
Design, Level 2 is Coding, Level 3 is Testing).
7. Deliverable-based WBS: Divides the project based on the tangible physical products
produced (e.g., Database Module, User Interface, Network API).
8. Responsibility-based WBS: Organizes work strictly based on the specific internal teams,
departments, or external vendors executing the tasks.
9. Geographical-based WBS: Used for distributed or international projects, dividing work
based on the location of execution (e.g., US Team, India Team).
10.The absolute lowest level of any WBS tree contains specific activities that can be reliably
assigned to individual team members.
Q: What is the Oldham Hackman job characteristic model? Explain with example.
(Repeated 4 times)
1. The Oldham-Hackman model proposes that specific job characteristics directly impact
employee motivation and satisfaction.
2. It suggests that enriching jobs naturally leads to higher performance and lower turnover
in software teams.
3. Skill Variety: The degree to which a job requires diverse activities and utilizes multiple
skills (e.g., a developer who designs, codes, and tests).
4. Task Identity: The extent to which a job involves completing a whole, identifiable piece of
work from start to finish.
5. Task Significance: The degree to which the job has a substantial, meaningful impact on
the lives or work of other people.
6. Autonomy: The level of freedom, independence, and discretion the employee has in
scheduling and performing their work.
7. Feedback: The extent to which carrying out the work provides direct, clear information
about performance effectiveness.
8. The model states that these characteristics lead to three critical psychological states:
meaningfulness, responsibility, and knowledge of results.
9. A high Motivating Potential Score (MPS) occurs when these five characteristics are
maximized in a project role.
10.Example: Giving a programmer autonomy to choose their own coding framework and
letting them see the user's positive feedback dramatically increases their motivation
compared to micro-management.
Q: Explain Forward and Backward Pass Techniques in detail. (Repeated 4 times)
1. These mathematical techniques are core computational components of the Critical Path
Method (CPM) for project scheduling.
2. The Forward Pass is used to determine the Earliest Start (ES) and Earliest Finish (EF)
times for every single project activity.
3. It moves sequentially from the start of the network diagram to the end, cumulatively
adding the duration of each activity.
4. This pass ultimately calculates the absolute minimum time required to complete the
entire project.
5. During a forward pass, if an activity has multiple predecessor tasks, you must select the
largest early finish time to move forward.
6. The Backward Pass calculates the Latest Start (LS) and Latest Finish (LF) times without
delaying the overall project deadline.
7. It moves backward from the end of the diagram to the start, subtracting the duration of
each activity.
8. During a backward pass, if an activity has multiple successor tasks, you must select the
smallest late start time to move backward.
9. By combining the data from both passes, project managers calculate the "float" or "slack"
of each individual activity ($Float = LS - ES$).
10.Activities with exactly zero float are identified as part of the critical path, meaning any
delay in them directly delays the final delivery date.
Q: Explain Software Configuration Management (SCM) in detail. (Repeated 3 times)
1. SCM is the discipline of managing and controlling changes in the evolution of software
systems throughout the lifecycle.
2. It ensures that the software product remains consistent, reliable, and reproducible
despite constant updates by multiple developers.
3. Version Control: SCM utilizes tools (like Git) to track every single version of source code,
allowing teams to revert to previous states if bugs are introduced.
4. Configuration Identification: The process of defining and naming every baseline
component (code, documents, data) so they can be securely tracked.
5. Change Control: A formal process where all proposed changes to the system are
submitted, reviewed, and approved before being implemented.
6. This prevents unauthorized "scope creep" and ensures all changes align with the project's
strategic goals and budget.
7. Configuration Status Accounting: Maintaining detailed records of the status of all
proposed changes, answering "what happened, why, and when?"
8. Configuration Auditing: Periodically checking the software baseline to ensure that it
accurately matches the approved requirements and design.
9. SCM is absolutely crucial in Agile environments where frequent, rapid changes and
continuous integration are the standard.
10.Without SCM, large teams face chaotic integration issues, lost code, and unmanageable
software bugs during deployment.
Q: What is PERT? Explain with an example. (Repeated 3 times)
PERT chart or PERT diagram is a tool used to schedule, organize, and map out tasks within a
project. PERT stands for program evaluation and review technique
1. PERT stands for Program Evaluation and Review Technique, a statistical tool used in
complex project scheduling.
2. It is specifically designed to analyze and represent the tasks involved in completing a
project where time durations are highly uncertain.
3. Unlike CPM (which uses one fixed duration), PERT calculates a weighted average using
three different time estimates for every task.
4. Optimistic Time (O): The absolute shortest time a task could take if everything goes
perfectly without any roadblocks.
5. Pessimistic Time (P): The absolute longest time a task could take assuming worst-case
scenarios and severe delays.
6. Most Likely Time (M): The best estimate of the time required under normal, realistic
working conditions.
7. The PERT Expected Time (TE) formula heavily weights the most likely scenario: $TE = (O +
4M + P) / 6$.
8. This weighted average provides a much more statistically realistic timeline than simply
guessing a single number.
9. PERT uses network diagrams (nodes and arrows) to visualize the sequence of events and
identify the critical path based on these expected times.
10.Example: A coding task has O=2 days, M=4 days, P=12 days. The Expected Time is $(2 + 16
+ 12)/6 = 30/6 = 5$ days. This accounts for the heavy risk of delay without throwing off the
schedule.