1. TECH581 Analyze Presentation Fall 2008 Date: 11/11/08 Team Members: xxxxx xxxxx Sound Removed

2. Brief Review of Project Charter Information Technology Department of major Insurance Company attempting to collect metrics on business requirements changes throughout application project lifecycle. If collected, measure is taken at the end of the project, amounting to 8 hours of work for a project manager. Tracking and recording the changes throughout the lifecycle of a project and the associated process that can be implemented across the organization can be a significant improvement to a maximum of 1 hour total for each project. The process of requirements counts/metrics can be used to further analyze and estimate future projects. Goal: To understand current processes for requirements metrics gathering to identify and eliminate non value add steps. Identify value added steps performed inefficiently and implement improvements.

3. CTQ Tree(s)

4. Data Collection Summarized Random sample of historical projects. PMs estimated time it took to measure requirements changes over time Random sample of new projects that were initiated soon before and/or after start of class project. Stratified by tool used for requirements collection and tier (size in forecasted dollars).

5. Data Collection Chart – Historical Data Estimate average hours to count requirements changes over time at the end of the project

6. Pivot Tables - Historical Data Data by stratification factors Historically, Tier 2 projects took longer to count requirements changes at the end of the project lifecycle. Historically, requirements kept in MS Word took longer to count changes at the end of the project lifecycle.

7. Data Collection – Current and Ongoing Projects Counting requirements changes during the project lifecycle averages to 1.10 hours of time to collect.

8. Fishbone Diagram

9. Chart by Project Size Tier 2 included a project with Word as the requirements tool.

10. Chart by Requirements Complexity

11. Chart by PM Experience (Grade)

12. Chart by PM Awareness

13. Chart by Awareness and Tool Tier 4 and low complexity Higher complexity and size (tier)

14. Chart by Requirement Tracking Tool

15. Chart by Tool and Project Size

16. Conclusions Total hours to count requirements changes over the project lifecycle at the end of the project averages 7.6 hours based on historical information. Average hours to count requirement changes over the lifecycle of the project during the project lifecycle averages 1.1 hours based on sample of projects studied.

17. Conclusions based on sample of projects studied: Requirements took longer to count when using MS Word as the requirements tracking tool. Projects with high complexity requirements took longer to count. No correlation found between awareness of the priority of the task and the effort to report requirements counts. No correlation found between PM experience (grade) and the effort to report requirements counts.