ScholarQuill logoScholarQuillUniversity Notes
  • Notes
  • Past Papers
  • Blogs
  • Todo
Login
ScholarQuill logoScholarQuillUniversity Notes
Login
NotesPast PapersBlogsTodo
More
SubjectsDiscussionCGPA CalculatorGPA CalculatorStudent PortalCourse Outline
About
About usPrivacy PolicyReportContact
Notes
Past Papers
Blogs
Todo
Analytics
    Current Subject
    🧩
    Software Project Management
    ITEC3131
    Progress0 / 42 topics
    Topics
    1. Introduction Software Project: Classification of project types2. Scope triangle3. Project risk vs business value4. The S curve5. Five phases of project management life cycle6. WBS: Work Breakdown Structure7. Estimate activity duration8. Five methods of Estimating Activity Duration9. Elapsed Time vs Productive time10. PMI Process Groups & Knowledge Areas11. Project Planning and Project Scheduling12. Project Proposal13. Project Networks: Critical Path Method (CPM)14. Build the project network15. Analysis of the project network16. Network Analysis and Critical Path Analysis17. PERT18. GANTT Chart19. Using MS-Project to draw GANTT chart20. Project Metrics & Software Project Estimation21. Software Project Metrics: Metrics & Indicators22. Software measurement: Size Oriented Metrics23. Function-Oriented Metrics24. Software Project Estimation: Decomposition Techniques25. Software Sizing26. Problem-Based Estimation27. Cost Estimation28. Size Estimation: COCOMO Model29. Function Point Analysis30. Project Staffing31. Project Monitoring and Control32. Project Staffing and Personnel Planning33. Software project Teams34. Risk Identification, Analysis and Management35. Earned Value Analysis36. Configuration Management37. Earned Value Analysis for Project Monitoring and Control38. Software Project Quality Assurance Plans39. SQA Process40. Software Project Quality Standards41. Overview of Project Configuration Management42. Project Risk Management
    ITEC3131›Estimate activity duration
    Software Project ManagementTopic 7 of 42

    Estimate activity duration

    3 minread
    542words
    Beginnerlevel

    📘 Estimate Activity Duration (Software Project Management)


    🔹 1. Definition

    Estimating activity duration means predicting the amount of time required to complete a specific task or activity in a project.

    👉 It answers the question: “How long will this task take?”


    🔹 2. Importance

    • Helps create a realistic project schedule
    • Ensures timely project completion
    • Aids in resource planning
    • Reduces chances of delays and cost overruns

    🔹 3. Factors Affecting Activity Duration

    🔸 1. Task Complexity

    • Simple tasks → less time
    • Complex tasks → more time

    🔸 2. Resource Availability

    • Skilled team → faster completion
    • Limited resources → delays

    🔸 3. Experience of Team

    • Experienced developers → accurate and faster work

    🔸 4. Technology Used

    • Familiar tools → less time
    • New technology → more time (learning curve)

    🔸 5. Dependencies

    • Some tasks depend on completion of others

    🔹 4. Common Estimation Techniques


    🔸 1. Expert Judgment

    • Based on experience of experts

    👉 Example: Senior developer estimates coding time


    🔸 2. Analogous Estimation

    • Based on similar past projects

    👉 Example: Previous login system took 3 days → similar estimate used


    🔸 3. Parametric Estimation

    • Uses mathematical models

    👉 Formula:

    Duration = Work / Productivity Rate
    

    👉 Example: 100 pages ÷ 10 pages/day = 10 days


    🔸 4. Three-Point Estimation ⭐ (Important)

    Uses three estimates:

    • Optimistic (O) → Best case
    • Most Likely (M) → Normal case
    • Pessimistic (P) → Worst case

    👉 Formula (PERT):

    Expected Time (TE) = (O + 4M + P) / 6
    

    👉 Example:

    • O = 2 days
    • M = 4 days
    • P = 8 days
    TE = (2 + 4×4 + 8) / 6 = (2 + 16 + 8)/6 = 26/6 ≈ 4.33 days
    

    🔸 5. Bottom-Up Estimation

    • Estimate small tasks first, then combine

    👉 More accurate but time-consuming


    🔹 5. Units of Measurement

    • Hours
    • Days
    • Weeks

    👉 Avoid vague terms like “soon” or “quickly”


    🔹 6. Diagram Description

    📌 Activity duration estimation is often shown in:

    👉 Gantt Chart

    • Bars represent duration of tasks over time

    👉 Network Diagram (PERT/CPM)

    • Nodes = activities
    • Arrows = dependencies
    • Duration written on tasks

    🔹 7. Example

    Task: Develop login feature

    Estimate Type Time
    Optimistic 2 days
    Most Likely 3 days
    Pessimistic 6 days

    👉 Using PERT:

    TE = (2 + 4×3 + 6)/6 = (2 + 12 + 6)/6 = 20/6 ≈ 3.33 days
    

    🔹 8. Important Exam Points

    • Duration ≠ Effort 👉 (Effort = total work, Duration = calendar time)

    • Use PERT formula for accuracy

    • Consider risks and uncertainties

    • Always base estimates on data or experience


    🔹 9. Common Mistakes

    ❌ Ignoring risks ❌ Over-optimistic estimates ❌ Not considering dependencies ❌ Lack of historical data


    🔹 10. Short Summary

    • Estimating activity duration = predicting time required for tasks

    • Uses techniques like:

      • Expert judgment
      • Analogous
      • Parametric
      • Three-point (PERT)
    • Accurate estimation is key for successful scheduling


    🔹 11. Quick Exam Answer (2–3 lines)

    Estimating activity duration is the process of predicting the time required to complete a project task. It uses techniques such as expert judgment and PERT, and is essential for creating an effective project schedule.


    🔹 12. Likely Exam Questions

    1. Define activity duration estimation.
    2. Explain the PERT formula with example.
    3. What factors affect activity duration?
    4. Differentiate between effort and duration.
    5. Describe different estimation techniques.
    6. Why is accurate duration estimation important?
    Previous topic 6
    WBS: Work Breakdown Structure
    Next topic 8
    Five methods of Estimating Activity Duration

    Past Papers

    Open this section to load past papers

    Click on Show Past Papers to see past papers.
    On This Page
      Reading Stats
      Est. reading time3 min
      Word count542
      Code examples0
      DifficultyBeginner