PROJECT MANAGEMENT SHEET
.What is slack? How is it calculated? What is Critical Path of
1 5. What are different types of quality assessments?
1
a PERT Network? Types include peer reviews, walkthroughs, inspections, audits, and
Slack is the amount of time a task can be delayed without affecting testing. These ensure that the software meets quality standards
the project deadline. It is calculated as: Slack = Latest Start – and user expectations.
Earliest Start; the critical path is the longest duration path in a
PERT network with zero slack. 6. What are the three key elements of Agile Methodology?
1
The three key elements are iterative development, customer
. What is a Project? What is its difference with routine work?
2 collaboration, and adaptive planning. These ensure flexibility and
A project is atemporary endeavorwith a defined scope, timeline, rapid delivery.
and resources to deliver a unique product/service. Unlike routine
work, a project has adefinite start and endand isnon-repetitive. 1 7. What are the four pillars of Agile methodology?
The four pillars are Individuals and Interactions over Processes
3 What are the causes of Project Trade Off? and Tools, Working Software over Comprehensive Documentation,
Project trade-offs arise due to conflicts betweenscope, cost, time, Customer Collaboration over Contract Negotiation, and
and quality. Changes in stakeholder priorities orresource Responding to Change over Following a Plan.
constraintsalso cause trade-offs.
18. What is Program Increment in Feature Driven
4. What is Risk Reduction Leverage? Development?
Risk Reduction Leverage (RRL) is a metric to evaluate the Program Increment (PI) is a timeboxed period during which
cost-effectivenessof a risk mitigation strategy. It is calculated as features are designed, developed, and integrated. It aligns multiple
(Risk Exposure before – after) / Cost of mitigation. teams toward shared business objectives.
.What is Responsibility Matrix?
5 9 Under which conditions Extreme Programming is
1
A Responsibility Matrix (RACI Matrix) defines the roles and Applicable?
responsibilities of project stakeholders. It ensures clarity in task XP is ideal when requirements change frequently, and the team
ownership using categories like Responsible, Accountable, needs continuous feedback. It suits small to medium projects with
Consulted, and Informed. close customer interaction.
.What is a Work Breakdown Structure?
6 1. What are the five values defining the agile mindset?
2
Work Breakdown Structure (WBS) is a hierarchical decomposition The five Agile values are Communication, Simplicity, Feedback,
of the total project scope into smaller, manageable components. It Courage, and Respect. These guide team behavior and
helps in planning, scheduling, and cost estimation. decision-making.
. What are the criteria for completeness of WBS?
7 2. What is “User Story” in Agile?
2
WBS should include 100% of project deliverables and be detailed A User Story is a short, simple description of a feature from the
enough for accurate estimation and assignment. It must follow the end-user's perspective. It helps define requirements and
mutually exclusive and collectively exhaustive (MECE) principle. acceptance criteria.
.What are the objectives of Joint Project Planning?
8 3.What is “Backlog” in Agile?
2
The objectives are to establish project scope, schedule, risks, Backlog is a prioritized list of work items, including features, bugs,
roles, and deliverables. It promotes collaboration and mutual and tasks. It is managed by the Product Owner and evolves as the
understanding among stakeholders. project progresses.
. What are the activities of Resource Allocation?
9 4. What is the difference between AON and AOA network
2
Resource Allocation includes identifying, assigning, and scheduling diagram?
resources based on availability and project needs. It also involves AON (Activity on Node): Activities are shown on nodes and arrows
resolving conflicts and balancing workload. represent dependencies.
AOA (Activity on Arrow): Activities are shown on arrows and nodes
0. What are the reasons for project cost overrun?
1 represent events.
Cost overrun occurs due to poor planning, inaccurate estimation, Key Differences:------------->
scope creep, and resource mismanagement. External factors like AON allows for more complex relationships like Start-to-Start,
inflation or delay in approvals also contribute. Finish-to-Finish.
AOA often requires dummy activities to show dependencies.
1. Describe the Project Cost Management Process?
1 AON is used in modern project tools like MS Project.
Project Cost Management involves cost estimating, budgeting, and AOA is based on PERT, and more suited for academic use.
control to ensure the project stays within approved budget. It AON is generally easier to understand and modify.
includes planning cost management, determining budget, and
monitoring costs. 5. What are the characteristics of a Project?
2
→Unique Purpose: Every project delivers a unique product or
12. What are the components of project management plan? service.
Key components include scope statement, schedule, cost baseline, →Temporary: Has definite start and end dates.
quality plan, risk plan, communication plan, and resource plan. →Progressive Elaboration: Detailed planning evolves as the
These elements guide project execution and monitoring. project progresses.
→Limited Resources: Operates under constraints of time, budget,
13. What is the importance of Software Product Quality? and manpower.
High software quality ensures customer satisfaction, fewer defects, →Cross-functional Team: Requires diverse skill sets and
and lower maintenance costs. It leads to better performance, departments.
security, and reliability.
4. What is DMAIC?
1
DMAIC stands for Define, Measure, Analyze, Improve, and
Control, a Six Sigma methodology. It is used for process
improvement and quality control.
6. What is resource levelling? Why is it required?
2 3. Describe the different project estimation techniques?
3
Resource levelling is the process of adjusting project schedules to →Expert Judgment:
resolve resource conflicts. It ensures optimum utilization of ->Based on experience from similar projects.
resources without overloading. ->Quick but subjective.
Importance:------------------> →Analogous Estimating:
→Avoids resource over-allocation. ->Compare with past similar projects.
→Maintains realistic timelines. ->Less accurate but fast.
→Prevents burnout and enhances productivity. →Parametric Estimating:
→Helps in rescheduling non-critical tasks. ->Use statistical models (e.g., cost per LOC or hour).
→Ensures project continuity during resource shortages. ->More accurate than analogous.
→Bottom-Up Estimating:
7. Describe the framework for dealing with the risk
2 ->Estimate each task individually and sum.
associated with Software project? ->Highly accurate but time-consuming.
A structured Risk Management Framework includes: →Three-Point Estimating:
→Risk Identification: List potential risks. ->Based on Optimistic (O), Pessimistic (P), and Most Likely (M):
→Risk Analysis: Assess probability and impact. Estimate=(O+4M+P)/6
→Risk Prioritization: Use Risk Exposure = Probability × Impact.
→Risk Response Planning: Avoid, mitigate, transfer, or accept ->Accounts for uncertainty.
risks.
→Risk Monitoring: Continuously track and revise risk plans. 4. Describe the four core values of Agile software
3
development as stated by Agile Manifesto.
28. What is Basic Principle of Project Cost Management? →Individuals and Interactions over processes and tools
To ensure that the project is completed within the approved budget. Encourages collaboration, adaptability.
Principles:------------------> →Working Software over comprehensive documentation
→Cost Estimation: Predict resources and expenses. Focus on functioning code as the primary measure of progress.
→Budgeting: Aggregate costs to establish baseline. →Customer Collaboration over contract negotiation
→Cost Control: Monitor and manage changes. Emphasizes client feedback and involvement.
→Apply Earned Value Management (EVM). →Responding to Change over following a plan
→Align costs with scope and schedule. Adaptable to dynamic requirements and feedback
9. What are Schedule Compression techniques? Describe
2 5. Describe any five Agile principles out of 12 principles
3
them. described by the authors of Agile Manifesto.
Used when a project must be completed in less time without →Customer Satisfaction: Deliver valuable software early and
changing scope. continuously.
Techniques: →Welcome Changing Requirements: Even late in development.
→Crashing: Add more resources to critical path activities. →Frequent Delivery: Working software delivered in short cycles.
→Fast Tracking: Perform activities in parallel instead of →Sustainable Development: Maintain a constant pace indefinitely.
sequentially. →Face-to-Face Communication: Most efficient method of
→Resource Optimization: Reallocate available resources conveying information.
efficiently. Each principle supports flexibility, efficiency, and customer-centric
→These techniques often increase cost or risk. development.
0. What is Project Quality Management?
3 6.What are the challenges of management of Agile Backlog?
3
It ensures that the project meets stakeholder expectations and Describe them.
defined quality standards. Challenges:-------------------->
Components: →Prioritization Conflicts: Multiple stakeholders may have
→Quality Planning: Identify quality requirements. conflicting priorities.
→Quality Assurance: Process-focused, prevents defects. →Scope Creep: Frequent changes may expand the scope beyond
→Quality Control: Product-focused, detects defects. control.
→Uses tools like Pareto Chart, Control Chart, Fishbone Diagram →Unclear User Stories: Poorly written stories lead to confusion
during development.
1.What are Boehm’s top ten risks in software development
3 →Dependency Management: Stories may depend on others,
projects? affecting sprint planning.
Risks:-----------------------------------> →Backlog Size Management: Large backlogs become hard to
→Personnel shortfalls →Unrealistic schedules and budgets groom and refine regularly.
→Developing wrong functions →Developing wrong user interface →Stakeholder Involvement: Requires continuous collaboration
→Gold plating (extra features) →Continuing stream of which may not always be feasible.
requirements changes →Shortfalls in external components
→Real-time performance shortfalls →Straining computer science 7.Describe the requirements of Agile. What is Backlog in
3
capabilities →Lack of stakeholder involvement Agile? What are the challenges of backlog management in
Agile?
2. What are the responsibilities and skills of a Software
3
Project Manager? equirements in Agile:
R
Responsibilities:-----------------------> →Captured as User Stories (Who, What, Why).
→Planning: Define scope, schedule, budget, and resources. →Prioritized in the Product Backlog.
→Team Management: Assign tasks, resolve conflicts, ensure →Must be negotiable, testable, and valuable.
productivity.
→Risk Management: Identify, assess, and mitigate project risks. acklog in Agile:
B
→Stakeholder Communication: Regular updates, manage →A dynamic, prioritized list of features, bugs, tasks.
expectations. →Split into Product Backlog (owned by Product Owner) and Sprint
→Documentation:Maintain reports, logs, and project records. Backlog (planned for a sprint).
Skills:-------------------------------> →Continuously groomed and refined.
→Leadership & Communication: For motivation and clarity. Challenges in Backlog Management:
→Technical Knowledge: Understand development tools and “” See from above answer
lifecycle.
→Problem Solving & Decision Making: For handling project issues.
→Time & Risk Management: For on-time, quality delivery.
8. What is Extreme Programming (XP)? Describe the Values
3
of Extreme Programming.
Definition:
XP is an Agile methodology focused on technical excellence, rapid
feedback, and customer satisfaction through frequent releases.
XP Values:
→Communication: Team members collaborate constantly.
→Simplicity: Do the simplest thing that works.
→Feedback: Continuous feedback through testing and customer
reviews.
→Courage: Speak truth, discard failing solutions, refactor
fearlessly.
→Respect: Team members respect roles and contributions.
XP promotes clean code, fast delivery, and adaptive planning.
9. Describe the XP Life Cycle.
3
Phases:-------------------------->
→Exploration: Customer writes user stories, team estimates cost
and effort.
→Planning: Release plan created based on priority stories and
velocity.
→Iterations to Release: Short iterations (1–3 weeks), tested
working software delivered.
→Production: System goes live, bugs are fixed, performance is
monitored.
→Maintenance: Continue iteration cycles to add features or fix
issues.
→Death: Project ends when no changes are needed or product is
retired.
0. Describe the Scrum Model of Agile Methodology. What are
4
the roles of Scrum Master and Product Owner in Scrum?
Scrum Model:
→Framework for iterative and incremental development.
→Development occurs in sprints (1–4 weeks).
→Daily Scrum meetings for progress updates.
→Product Backlog: List of all features.
→Sprint Backlog: Selected items for current sprint.
Scrum Roles:
→Scrum Master: Facilitates Scrum practices// Removes
impediments.// Shields team from outside distractions.
Product Owner: Owns the Product Backlog. // Defines priorities
→
and requirements. //Represents stakeholders and customer needs
.4 1. Describe the Scrum Values.
→Commitment: Team commits to sprint goals and delivering
quality.
→Courage: Face challenges, speak openly, try new approaches.
→Focus: Team stays focused on sprint work.
→Openness: Transparent about progress, problems, and updates.
→ Respect: Respect team contributions, diverse roles and
opinions.
2.What is the difference between Quality Control and Quality
4
Assurance?
Quality Control (QC):
→Reactive: Detects defects after development.
→Includes testing, inspections.
Quality Assurance (QA):
→Proactive: Ensures quality during development.
→Focuses on process improvement and standards.
3. Describe 5 Best Practices of Scrum.
4
→Time-boxed Sprints: Fixed duration (1–4 weeks) encourages
predictable delivery.
→Daily Stand-ups: Short daily meetings for status, blockers, plans.
→Sprint Retrospective: Review what went well/poorly, apply
continuous improvement.
→Definition of Done (DoD): Clear criteria that define when a task is
truly completed.
→Backlog Grooming: Regular refinement keeps backlog relevant,
prioritized, and clear.
hese practices help ensure transparency, agility, and value
T
delivery.
