IPTM

1.       Unit 1: Pro Management

1. 1.What is the need of project management? 5M

• Resource Allocation: Optimize use of time, money, and manpower.
• Goal Achievement: Define and meet project objectives within deadlines.
• Risk Mitigation: Identify and manage potential project risks.
• Quality Assurance: Ensure project output meets quality standards.
• Stakeholder Communication: Facilitate clear and effective communication.

1. 2.What is conflict management in PM (Project Management)? 5M

• Identify Conflict Types: Recognize various forms of conflict (interpersonal, technical).
• Resolution Methods: Use strategies like negotiation and collaboration.
• Effective Communication: Foster open dialogue to resolve conflicts.
• Conflict Documentation: Record conflict occurrences and resolutions.
• Stakeholder Satisfaction: Resolve conflicts without harming project goals.

1. 3. Explain requirement management.

• Gather Requirements: Collect project needs from stakeholders.
• Analyze and Prioritize: Assess and rank requirements based on impact.
• Ensure Traceability: Link requirements to project deliverables.
• Manage Changes: Control scope changes effectively.

1. 4. Explain Release management. 4M
2. • Plan Releases: Outline features and timelines for product releases.
   • Coordinate Deployment: Manage rollout to production environments.
   • Quality Assurance: Test and validate software quality.
   • Maintain Documentation: Keep records of release notes and guides.
3. 5. Explain PMI model. 10M
4. (PMI) provides a framework for project management. Five key points in the PMI model include:
5. • Initiation: Assess project feasibility and define goals.
   • Planning: Develop detailed project plans and schedules.
   • Execution: Implement plans and coordinate resources.
   • Performance Control: Monitor progress and adjust as needed.
   • Closure: Complete, review, and learn from the project.
   • 
   • 
     
6. 6. Why do software projects fail? 5M
7. • Poor Requirements: Vague or changing project specifications.
   • Inadequate Planning: Unrealistic timelines and resource allocation.
   • Poor Communication: Misunderstandings among team and stakeholders.
   • Quality Issues: Software defects or performance problems.
   • Scope Creep: Uncontrolled changes leading to delays.
8. 7. Explain the changing nature of software. 10M
9. • The nature of software is continually changing due to technological advancements and evolving user needs.
   • o Rapid Technological Advancements: Software technologies, languages, and tools continuously evolve, requiring software professionals to adapt and stay current. o Increased Connectivity: Software is now more interconnected, with cloud-based services, APIs, and IoT, changing how software is developed and used. o User-Centric Focus: Software development increasingly focuses on user experience and user-centered design to meet evolving user expectations. o Agile and DevOps: Agile methodologies and DevOps practices have reshaped software development by emphasizing collaboration, flexibility, and continuous delivery. o Security Challenges: Growing cybersecurity threats necessitate a focus on security in software development.
   
   
10. 8. Explain software problems. 10M
11. • o Bugs and Errors: Software often contains defects or errors that can affect functionality, leading to crashes or unexpected behavior. o Performance Issues: Slow or inefficient software can be a problem, especially for resource-intensive applications. o Usability Challenges: Poorly designed interfaces or non-intuitive software can result in user dissatisfaction and reduced adoption. o Compatibility Problems: Incompatibility with different platforms or devices can hinder the reach of software. o Maintenance Challenges: Software may become difficult to maintain over time due to a lack of documentation, complexity, or changing requirements.
12. 9. Explain software quality attributes. 10M
13. • Software quality attributes refer to characteristics that define the quality of software
    • o Functionality: The software's ability to perform its intended functions 
    • o Reliability: The software's capability to provide failure-free service and operate as expected.
    • o Usability: The ease with which users can learn, understand, and interact with the software.
    • o Efficiency: The ability of the software to perform tasks with optimal resource utilization.
    • o Maintainability: The ease with which the software can be modified, updated, or enhanced.
    
    
14. 10. Explain the three “R” Reuse principles. 5M
15. • Reuse of Components: Incorporating existing elements in new software.
    • Reengineering: Modifying existing software for improvement.
    • Retooling: Applying new tools and technologies in development.
16. 11. Explain S.M.A.R.T Goals. 5M
17. • Specific: Clear and well-defined targets.
    • Measurable: Quantifiable or assessable objectives.
    • Achievable: Realistic and attainable aims.
    • Relevant: Aligned with broader goals.
    • Time-bound: Defined timeframe for completion.
18. 12. Explain the responsibilities of an IT Project Manager. 5M
19. • Project Planning: Organizing project scope, schedule, and resources.
    • Stakeholder Management: Engaging and communicating with all parties.
    • Resource Management: Allocating and overseeing project resources.
    • Quality Assurance: Ensuring project meets quality standards.
    • Risk Management: Identifying and mitigating potential risks.
20. 13 Explain the Power/Interest Grid. 5M
21. • High Power, High Interest: Engage closely; key decision-makers.
    • High Power, Low Interest: Keep informed; important but less involved.
    • Low Power, High Interest: Keep informed and engaged; offer insights.
    • Low Power, Low Interest: Monitor; minimal effort required.
    • 
      
      

Unit 2: PROJECT MODELS phases

1. Explain the waterfall model. 5
2. • Sequential Phases: Progress through distinct stages one at a time.
   • Clear Requirements: Requires well-defined requirements upfront.
   • Lack of Flexibility: Difficult to incorporate changes late in the process.
3. What are feasibility studies? 10

• Purpose: Evaluate the viability and potential success of a proposed project or idea.
• Aspects Assessed:
  • Technical Feasibility: Can the project be realized with current technology and resources?
  • Economic Feasibility: Is the project financially viable and cost-effective?
  • Legal Feasibility: Does the project comply with legal and regulatory requirements?
  • Operational Feasibility: Will the project function effectively within the existing operational framework?
  • Market Feasibility: Is there a market demand or need for the project's output?
• Outcome: Provides a basis for decision-making regarding project initiation, modification, or abandonment.
• Process: Involves research, data collection, analysis, and forecasting.
• Benefit: Minimizes risk by identifying potential problems and opportunities before significant resources are committed.

1. Explain V-Model testing phases. 10

Phases:

Requirements Analysis:

Testing Correspondence: User Acceptance Testing planning.

Focus: Ensuring requirements are testable and meet user needs.

System Design:

Testing Correspondence: System Testing planning.

Focus: Creating overall system architecture.

High-Level Design:

Testing Correspondence: Integration Testing planning.

Focus: Defining how system components interact.

Low-Level Design:

Testing Correspondence: Unit Testing planning.

Focus: Detailed design of individual components.

Implementation:

Testing Phase: Executing Unit Testing.

Focus: Developing and testing individual units/components.

Integration:

Testing Phase: Conducting Integration Testing.

Focus: Testing interactions between integrated components.

System Testing:

Testing Phase: Executing System Testing.

Focus: Testing the complete system functionality and requirements.

User Acceptance Testing (UAT):

Testing Phase: Conducting UAT.

Focus: Validating the system against user requirements.

1. Explain four types of prototyping models. 8

2. • 1. Throwaway/Rapid Prototyping:

        • Quickly built models: Used to visualize and test features.
        • Discarded after use: Not part of the final product.
        • Purpose: Validate requirements and design choices early.

     2. Evolutionary Prototyping:

        • Continuously developed prototypes: Evolve into the final system.
        • Iterative process: Regular updates based on user feedback.
        • Advantage: Adapts to changing requirements over time.

     3. Incremental Prototyping:

        • Partial systems built in stages: Each adding functionality.
        • Combines elements of throwaway and evolutionary: Allows refinement at each stage.
        • Goal: Deliver a working system in increments.

     4. UI/UX Prototyping:

        • Focus on user interface/experience: Test look and feel.
        • Often high-fidelity: Closely resembles the final product.
        • Useful for: Gathering user feedback on usability and design.
3. Explain the incremental process model. 10
4. • Iterative Development: Build software in small, manageable sections.
   • Manageable Increments: Each increment builds upon previous ones.
   • Continuous Delivery: Regular delivery of functional software.

Unit 3: PROJECT

1. Types of project requirement? 5
2. • Functional: Desired features and functionalities.
   • Non-Functional: Performance, security, usability standards.
   • User: End-user needs and expectations.
   • Business: Alignment with business objectives.
   • System: Technical and hardware requirements.
   • Environmental: External factors like regulations.
3. Drawing of Data Flow Diagram (DFD). 5
4. 1. • Visual Representation: Shows how data moves within a system.
      • 
        
        
        
5. Types of data collection. 10
6. • Surveys: Questionnaires or interviews for wide data collection.
   • Interviews: In-depth, one-on-one data gathering.
   • Observations: Direct observation and recording.
   • Experiments: Controlled studies for cause-effect relationships.
   • Focus Groups: Group discussions for collective insights.
   • Document Analysis: Review existing documents for data.
   • Case Studies: In-depth study of specific situations.
   • Online Data Collection: Utilize online sources for data gathering.
7. 
   
8. Line of code (LOC).
9. 1. Measurement of Code Size: Counts the number of lines in a software program's source code. Project Estimation Tool: Used for assessing software complexity and estimating development effort.
      
      Unit 4: BUSINESS PLAN

1. Explain the business case. 5
2. • Project Justification: Reasons and benefits for undertaking the project.
   • Analysis and Benefits: Includes market, feasibility, and risk analysis.
3. Project Communication plan? 5
4. 1. • Communication Guidelines: How, when, and with whom to communicate.

   2. Competitor analysis? 5

   3. Evaluate Competitors: Assess strengths, weaknesses, and strategies.

5. SWOT analysis? 4
6. Internal and External Factors: Strengths, Weaknesses, Opportunities, Threats.
7. Making a project charter? 10
8. Purpose: Formal document that defines and authorizes a project, outlining its objectives, scope, and participants.
9. Key Elements:

• 1. Project Purpose: Describes the reason and need for the project.
  2. Objectives and Goals: Specifies what the project aims to achieve.
  3. Scope: Defines the boundaries and limitations of the project.
  4. Roles and Responsibilities: Identifies the project team and their duties.
  5. Resources: Outlines the budget and resources allocated.
  6. Stakeholders: Lists key stakeholders and their interests.
  7. Risks and Issues: Highlights potential risks and mitigation strategies.
  8. Timeline: Provides a high-level timeline with major milestones.
• Significance: Serves as a guideline for execution and decision-making throughout the project.

1. Work Breakdown Structure (WBS). 5
2. Definition: A hierarchical decomposition of a project into smaller, manageable parts or work packages.
3. Purpose: Helps in organizing and defining the total scope of the project by breaking it down into manageable tasks.

Unit 5: SHEDULING

1. Project Scheduling? 4
2. 1. • Activity Timeline: Outline start and end dates of project activities.
      
      
3. What are the principles used in project scheduling? 10
4. 1. • • Scope Definition: Clearly define project objectives and deliverables.
        • Activity Breakdown: Decompose project into smaller tasks.
        • Activity Sequencing: Order tasks based on dependencies.
        • Duration Estimation: Estimate time required for each task.
        • Resource Consideration: Allocate necessary resources.
        • Critical Path Analysis: Determine the longest path of dependent tasks.
        • Deadline Setting: Establish realistic timelines.
        • Adjustment and Monitoring: Continuously track and revise schedule.
        
        
5. Steps for project scheduling? 5
6. • Activity Identification: List all project tasks.
   • Dependency Determination: Establish task interdependencies.
   • Duration Estimation: Approximate time for each task.
   • Resource Allocation: Assign resources to tasks.
   • Activity Sequencing: Order tasks logically.
   • Schedule Development: Create a project timeline.
   • Schedule Optimization: Adjust for efficiency.
   • Progress Monitoring: Track schedule adherence.
7. Explain Gantt chart? 4
8. Visual Schedule Representation: Display tasks along a timeline.
9. 1. • 
        
10. Steps of CPM (critical path method) with example? 8
11. 1. • Activity Sequence Determination: Identify longest path of tasks.
12. What are the different types of budget? 10
13. • Operating: Day-to-day expenses and revenues.
    • Capital: Long-term investments.
    • Cash: Cash flow management.
    • Project: Specific project costs.
    • Master: Overall financial goals.
    • Flexible: Adjusts with activity levels.
    • Zero-based: Justifies all expenses.
    • Performance: Based on outcomes.
    • 
      
14. Four various degrees of rigor?10

1. Informal: Basic, intuitive approach for small projects.
2. Incremental: Small, stepwise adjustments for stable projects.
3. Analytical: Detailed, data-driven analysis for complex projects.
4. Intensive: Comprehensive, extensive planning for large-scale, high-risk projects.

Types of Projects 10

1. Construction Projects: Building infrastructures like buildings, roads.
2. IT Projects: Developing software, implementing IT systems.
3. R&D Projects: Innovating new products, technologies.
4. Marketing Projects: Launching marketing campaigns, branding efforts.
5. Organizational Change Projects: Implementing new processes or restructuring in organizations.
6. Event Management Projects: Organizing events, conferences, exhibitions.
7. Community or Social Projects: Initiatives for social welfare, community development.
8. Product Development Projects: Creating new products or improving existing ones.
9. Infrastructure Projects: Developing public facilities like bridges, tunnels.
10. Business Process Improvement Projects: Enhancing efficiency of business processes.

Unit 6:

1. What is meant by software quality management?4
2. Software quality management is a set of practices, processes, and techniques used to ensure that software products and services meet defined quality standards and customer expectations. It involves activities such as quality planning, quality assurance, quality control, and quality improvement throughout the software development lifecycle.
3. 
   
4. What is meant by KPA in software development?5
5. In the context of software development, KPA stands for Key Process Area. KPA is a term used in the Capability Maturity Model Integration (CMMI), which is a framework for assessing and improving an organization's software development processes
6. What is meant by maintainability of software?4
Maintainability in software refers to how easily a software system can be modified, repaired, or improved over time. It is crucial because software often needs updates and fixes. A system with good maintainability is designed for easy understanding, modification, and extension.

7. What is meant by portability of software?4
8. Portability in software is the ability for a software system to run or be transferred without significant modifications across different platforms or environments. Portable software is designed to work on various operating systems, hardware architectures,
9. 
   
10. Explain Six Sigma? 5

• Objective: Improve process quality, reduce defects and errors.
• Focus: Enhance efficiency, customer satisfaction, and cost savings.
• Method: Structured approach with statistical analysis.

Five Key Phases (DMAIC):

1. Define:

   • Clarify project purpose, objectives, customer needs.
   • Identify improvement areas and set measurable goals.

2. Measure:

   • Collect data on current process performance.
   • Establish baseline measurements and KPIs.

3. Analyze:

   • Analyze data to find causes of variations/defects.
   • Use statistical techniques for root cause analysis.

4. Improve:

   • Generate and implement solutions for issues.
   • Apply process redesign, mistake-proofing, lean methods.

5. Control:

   • Set up controls and monitoring systems.
   • Maintain process stability and continuous improvement.

1. What is meant by a cause-and-effect diagram (Fishbone)?5
2. • Purpose: Identify root causes of problems.
   • Structure: Resembles a fishbone with a spine and branches.
   • Main Branches: Categories like manpower, methods, machines, materials, measurements, environment.
   • Process: Brainstorm and identify causes in each category.
   • Method: Use root cause analysis, ask "why" repeatedly.
   • Benefits: Maps out all potential causes, aids in understanding interconnections.
   • Outcome: Helps prioritize issues, fosters collaboration, and guides solution development.
3. Explain control charts?4
4. • Purpose: Monitor process performance.
   • Features: Center line for average, upper/lower control limits.
   • Use: Identify process stability and variations.
   • Indication: Data outside limits signals issues.
   • Application: Quality control and process improvement.

Unit 7: HUMAN NEED TEAM

1. What is meant by Project Human Resources Management (PHRM)?5
2. • Definition: Managing people involved in a project.
   • Focus: Ensure effective teamwork and resource utilization.
   • Goal: Achieve project objectives within timeline and budget.
   • Activities: Organizing, leading, and optimizing team performance.
   • 
     
3. Explain different team members in a team (categories)?10
4. • Leader: Guides and directs the team.
   • Specialist: Brings expertise in specific areas.
   • Innovator: Generates creative ideas and solutions.
   • Collaborator: Promotes teamwork and cooperation.
   • Implementer: Focuses on executing tasks and strategies.
   • Communicator: Facilitates clear and effective communication.
   • Coordinator: Organizes tasks and manages workflow.
   • Mediator: Resolves conflicts and maintains harmony.
   • 
     
5. Explain Maslow’s Hierarchy of Needs?5
6. • Concept: A theory in psychology explaining human motivation.
   • Structure: Pyramid with five levels of needs.
   • Levels:
     1. Physiological Needs: Basic survival needs like food, water.
     2. Safety Needs: Security, safety, stability.
     3. Love/Belonging Needs: Relationships, friendships, belonging.
     4. Esteem Needs: Respect, self-esteem, recognition.
     5. Self-Actualization: Personal growth, fulfilling potential.
   • Progression: Must satisfy lower-level needs before higher ones.
7. Explain four dimensions of psychological type in MBTI? 10

8. 1. Extraversion/Introversion (E/I):

      • Extraversion: Preference for external world of people and activities.
      • Introversion: Preference for internal world of thoughts and reflections.

   2. Sensing/Intuition (S/N):

      • Sensing: Preference for concrete, factual information.
      • Intuition: Preference for concepts, theories, and possibilities.

   3. Thinking/Feeling (T/F):

      • Thinking: Decision-making based on logic and objective analysis.
      • Feeling: Decision-making based on values and subjective evaluation.

   4. Judging/Perceiving (J/P):

      • Judging: Preference for structure, organization, and planning.
      • Perceiving: Preference for flexibility, spontaneity, and adaptability.
9. Explain conflict in project management?4
10. • Nature: Inevitable disagreements or differences within a project team.
    • Causes: Varied opinions, interests, or goals among team members.
    • Types: Task-related, interpersonal, or resource-based conflicts.
    • Management: Involves identifying, understanding, and resolving conflicts.
    • Techniques: Effective communication, negotiation, and problem-solving.
    • Outcome: Properly managed conflict can lead to positive project outcomes and team growth.

Unit 8: SOFTWARE MANAGEMENT

1. Explain software management team based on life cycle focus? 5

Role: Oversees software development from conception to deployment.

Phases Managed: Requirements, design, development, testing, deployment, maintenance.

Planning: Sets goals and timelines for each phase.

Coordination: Ensures seamless transition between life cycle phases.

Quality Control: Maintains standards throughout the development process.

Resource Management: Allocates resources effectively for each stage.

Risk Management: Identifies and mitigates risks at every phase.

Collaboration: Facilitates communication among different team members.

Adaptability: Adjusts plans based on feedback and changing needs.

1. What do you mean by a software architectural team? 4

Function: Designs the high-level structure of software systems.

Responsibilities:

Develop software architecture and frameworks.

Ensure technical feasibility and integration.

Focus:

Align architecture with business goals and user needs.

Balance functionality, performance, and scalability.

Collaboration: Works with development teams for implementation.

Guidance: Provides technical direction and standards.

1. What do you mean by line-of-business organizations? 4

• Definition: Departments or units within a company focused on core business areas.
• Purpose: Specialize in specific operational functions or market segments.
• Goal: Drive business growth and profitability in their specific areas.
• Role: Develop and deliver products or services to meet market demands.
• Operation: Function with a degree of autonomy, aligned with overall company strategy.
• Examples: Sales, marketing, production, or customer service departments.

1. Explain Project Review Author (PRA)?5

• Role: Evaluates and assesses project progress and performance.
• Responsibilities:
  • Conducts regular reviews of project milestones.
  • Analyzes project delivery against planned objectives.
• Functions:
  • Provides objective feedback on project management practices.
  • Identifies areas for improvement and risks.
• Outcome: Ensures project aligns with goals and standards.
• Communication: Reports findings to stakeholders and project teams.

1. Explain Automation Building Blocks? 5

• Foundation of Automation Systems: Essential components for creating automation solutions.
• Key Elements:
  • Process Assessment: Identifying processes suitable for automation.
  • Tool Selection: Choosing appropriate automation tools and technologies.
  • Workflow Design: Mapping out automated workflows and processes.
  • Scripting and Coding: Developing scripts or codes for automation tasks.
  • Integration: Ensuring compatibility with existing systems.
  • Testing: Verifying the functionality and reliability of automated processes.
  • Monitoring and Maintenance: Ongoing oversight to ensure continued effectiveness.
• Objective: Enhance efficiency, accuracy, and speed in repetitive tasks.

1. Explain change management? 5

• Purpose: Effectively managing and facilitating organizational change.
• Key Aspects:
  • Planning: Developing strategies for implementing change.
  • Communication: Informing and engaging stakeholders about changes.
  • Training and Support: Providing necessary resources for adapting to change.
  • Monitoring: Tracking the progress and impact of changes.
  • Adaptation: Adjusting strategies based on feedback and outcomes.
• Goal: Ensure smooth transition while maintaining productivity and morale.

1. Explain Configuration Control Board (CBB)? 4

• Function: Oversees changes in project configurations and standards.
• Role:
  • Reviews and approves proposed changes in a project.
  • Ensures changes align with project objectives and requirements.
• Responsibilities:
  • Manages and maintains configuration management documentation.
  • Assesses impact of proposed changes on project scope, time, and cost.
• Authority: Decides on the acceptance or rejection of change requests.
• Collaboration: Works with project managers and teams for smooth implementation of changes.

1. Explain stakeholder environment? 4
2. • • Internal Stakeholders: Includes employees, management, and shareholders.
     • External Stakeholders: Encompasses customers, suppliers, partners, regulators, and the community.
   • Influence: Stakeholders can significantly impact project decisions, strategies, and outcomes.
   • Management: Requires effective communication, engagement, and relationship management.
   • Considerations: Understanding and addressing the diverse needs and expectations of various stakeholders.
   • Objective: Align project goals with stakeholder interests to ensure successful outcomes.

1.