Software Project Planning and Estimation Techniques
Viewpoints and Organizational Context in Software Development
Software Development Viewpoints: Software development can be analyzed from two distinct perspectives: * Developers: The individuals or teams responsible for the technical creation of the system. * Clients or Users: The individuals or organizations who will utilize the software.
Organizational Structures: * In-house Development: Occurs when both the developers and the users belong to the same organization. * Outsourced Development: Occurs when developers and users are in different organizations. * Global System Development: In the modern era, development often involves different organizations located on different continents. These organizational and geographical factors significantly influence how a project is structured and managed.
The Build or Buy Decision
Conceptual Framework: * Build: Choosing in-house development to create a custom solution. * Buy: Deciding to purchase Off-The-Shelf (OTS) software. * Outsource: This may involve either building a custom solution via a third party or buying an existing product.
Advantages of Off-The-Shelf (OTS) Software: * Cost Efficiency: It is generally cheaper because the supplier spreads the initial development costs over a large customer base. * Immediate Availability: The software already exists, eliminating the delay associated with a full development cycle. * Trialability: Potential customers can often trial the software before committing to a purchase. * Established Reliability: If there are existing users, bugs are more likely to have been identified and eradicated through previous usage.
Disadvantages of Off-The-Shelf (OTS) Software: * Lack of Competitive Advantage: The customer receives the same application as their competitors; any advantage must come from unique usage rather than the tool itself. * Workflow Constraints: The customer may be forced to change their internal business processes to match the logic of the OTS application. * Lack of Control: The customer does not own the source code and cannot make changes to it. * Supplier Dependency: There is a risk of over-reliance on a single software supplier.
General Approach to Decision Making: * Risks and Uncertainties: Assess if requirements are well understood and if the intended technologies are familiar. * Application Characteristics: Consider the type of application (e.g., information system vs. embedded system), its criticality, and the differences between target and development environments. * Client Requirements: Determine if a specific methodology is mandated by the client.
Make or Buy Analysis Calculations
Break-even Analysis: This method compares the cost of leasing an item versus purchasing it to find the point where costs are equal.
Example Problem: * Lease Cost: * Purchase Cost: initial cost plus a daily operational cost of . * Equation: To find the break-even point ( being the number of days): * 400 \times d = * * * Conclusion: If the item is needed for more than days, purchasing is more economical. If needed for fewer than days, leasing is better.
Fixed Build Costs (Build vs. Buy Scenario): * Build Initial Cost: * Build Monthly Fees:
Earned Value Management (EVM)
Earned Value (EV): The value of work actually completed to date, relative to the total project budget. * Formula: * Example: If the budget is and is complete, .
Key EVM Metrics: * Planned Value (PV): The estimated value of work that was scheduled to be completed by a specific date. * Actual Cost (AC): The total amount of money actually spent on work completed so far. * Cost Performance Index (CPI): Measures cost efficiency. . A value indicates the project is under budget (good). * Schedule Performance Index (SPI): Measures schedule efficiency. . A value indicates the project is ahead of schedule (good).
Performance Tracking Scenarios (Example Data): * Scenario 1: PV=100, EV=100, AC=100 → On Schedule, On Budget. * Scenario 2: PV=100, EV=100, AC=75 → On Schedule, Under Budget. * Scenario 3: PV=100, EV=100, AC=150 → On Schedule, Over Budget. * Scenario 4: PV=75, EV=100, AC=100 → Ahead of Schedule, On Budget. * Scenario 5: PV=75, EV=100, AC=150 → Ahead of Schedule, Over Budget. * Scenario 6: PV=100, EV=150, AC=100 → Ahead of Schedule, Under Budget. * Scenario 7: PV=150, EV=100, AC=75 → Behind Schedule, Under Budget. * Scenario 8: PV=100, EV=75, AC=100 → Behind Schedule, Over Budget. * Scenario 9: PV=150, EV=100, AC=100 → Behind Schedule, On Budget.
Activity Planning and Identification
Importance of Activity Planning: * Feasibility Assessment * Resource Allocation * Detailed Costing * Motivation * Coordination
Core Principles of Activities: * A project consists of interrelated activities. * A project begins when at least one activity is ready to start and ends when all activities are complete. * Activities must have clearly defined start and endpoints, typically linked to a tangible deliverable. * Resource requirements for activities must be forecastable.
Identifying Activities: The Activity-Based Approach: * This involves creating an exhaustive list of all project activities. * Methods include team brainstorming or analyzing similar historical projects. * For large projects, it is useful to subdivide tasks by life-cycle stages.
Work Breakdown Structure (WBS): Identifying high-level tasks and decomposing them into lower-level, manageable sub-tasks.
Activity Sequencing and Scheduling
Bar Charts and Gantt Charts: Visual tools used to map tasks against a timeline (weeks, months, quarters). * Gantt Example Tasks (Building a House): Find Plot of Land, Draw Plans, Hire Project Manager, Hire Contractor, Survey Land, Dig, Lay Foundation, Purchase Building Materials, Build Frame, Wire Electrics, Install Drywall, Add Roof, Paint.
Network Modeling Techniques: * Activity on Node (AoN): * The project has exactly one start node and one end node. * Nodes represent activities and contain duration data. * Links (lines) represent dependencies but have no duration. * Time flows from left to right; loops are strictly prohibited. * Activity on Arrow (AoA): * Arrows represent activities; nodes represent events. * Nodes are numbered sequentially. * Tracks earliest and latest dates for events. * Slack: The difference between the earliest and latest date for an event.
Understanding Float: * Float: The time an activity can be delayed without impacting subsequent tasks or the project deadline. * Total Float (TF): (Latest Start minus Earliest Start). * Free Float (FF): (Earliest Start of next activity minus Earliest Finish of current). * Float Calculation (F): .
Software Effort Estimation Techniques
Common Estimation Methods: * Algorithmic Models: Use "effort drivers" (system and environment characteristics) to predict effort. * Expert Judgement: Advice from experienced staff. * Analogy: Using actual effort from a similar, completed project as a baseline. * Parkinson: The estimate is equal to the staff effort currently available. * Price to Win: The estimate is set at the level required to win a contract competition. * Top-down: Breaking a total project estimate into component tasks. * Bottom-up: Sizing individual tasks first and aggregating them for a total.
Specific Estimation Procedures: * Analogous Estimating: Historical information and expert judgment used early in the project. It is fast and low-cost but potentially less accurate. * Parametric Estimating: Identified by the duration per unit of work multiplied by the number of units. (Example: If cutting acres took hours, cutting acres is estimated at hours). * Three-Point Estimates (PERT): Uses three duration estimates to find the expected duration (): * Most Likely () * Optimistic () * Pessimistic () * Formula:
Schedule Development and the Critical Path
Process: An iterative process using activities, relationships, resources, and durations to create a project schedule. * Baseline: The planned start and finish dates for activities and milestones.
Tools and Techniques: * Resource Leveling * What-if Scenario Analysis * Critical Chain Method * Critical Path Method (CPM): * Identifies the minimum time required to complete the whole project. * Highlights the specific set of activities that, if delayed, will delay the entire project. * Used to plan resource allocation and monitor project health.
Contingency Reserves: Buffers (time or cost) added to the schedule to account for uncertainty. These can be fixed periods or percentages and may be adjusted as more data becomes available during the project lifecycle.