Activity Point Effort Estimation for Package Implementation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing effort estimation approaches and tools for package implementation programs are inadequate in providing holistic estimates, failing to account for all work streams such as Training, Organization Change Management, Program Management, Testing, Performance Management, Configuration, Requirement Gathering, Design, Planning, and Business Process Reengineering, leading to inaccurate schedule and cost projections.
Innovation Solution
A method and tool that calculate overall effort using activity-point-based approaches, dividing programs into work streams and phases, determining activity complexity values, and applying productivity metrics to estimate effort across various roles and phases, providing a comprehensive estimate that includes technical and non-technical efforts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If existing effort estimation approaches (SMC, LOC, FP) are used, then technical effort or functional effort can be estimated, but holistic program effort covering all work streams cannot be provided
Solution Approach 1:
The patent segments the package implementation program into multiple distinct work streams (Training, Organization Change Management, Program Management, Testing, Performance Management, Configuration, Requirement Gathering, Design, Planning, and Business Process Reengineering). Each work stream is further divided into phases and activities, allowing comprehensive coverage while maintaining estimation precision for each component.
Solution Approach 2:
The patent creates a universal estimation framework that can estimate effort across all types of package implementation work streams using a common methodology. The activity-point-based approach with productivity metrics provides a multi-functional tool that works for technical, functional, managerial, and organizational activities uniformly.
2Adaptability or versatility
If comprehensive work streams are included in estimation, then holistic program effort can be captured, but estimation complexity increases
Solution Approach 1:
By segmenting the program into work streams, phases, and activities, the patent manages complexity through hierarchical decomposition. This structure allows the comprehensive framework to remain organized and manageable, with each level building upon the previous one systematically.
Solution Approach 2:
The patent changes the estimation parameter from traditional lines of code or function points to activity points based on productivity metrics. This parameter transformation simplifies the estimation process while maintaining comprehensive coverage, as activity points can be assigned based on standardized productivity data for different types of activities.
3Measurement precision
If activity-point-based approach with productivity metrics is used, then accurate holistic effort estimation is achieved, but more data processing and calculation are required
Solution Approach 1:
The patent performs preliminary actions by establishing standardized productivity metrics for different activity types before the actual estimation process. This pre-calculation of productivity data allows for faster and more accurate estimations during implementation, as the complex calculations have already been prepared in advance.
Solution Approach 2:
The patent uses copying by applying standardized productivity metrics and activity point values across similar activities and work streams. Instead of calculating effort from scratch for each activity, the framework copies and adapts proven productivity data, significantly reducing processing requirements while maintaining accuracy.
Data Source
AI summary
Techniques and solutions are provided for determining overall effort for a package implementation program. Determining overall effort can comprise determining a program parameter complexity value for each of a plurality of program parameters, determining activities for program phases and program work streams, calculating an activity point value for each determined activity, and calculating overall effort for the package implementation program. The activity point values can be calculated using, at least in part, the program parameter complexity values. Calculating the overall effort can use, at least in part, the activity point values and a pre-determined productivity metric that is specific to a type of the package implementation program.