The document discusses measurement and analysis (M&A) in project management. M&A includes measuring a project's state, analyzing the data, and communicating results. It outlines the key goals and subpractices for each step, such as establishing objectives, specifying measures, collecting and analyzing data, and communicating results. An example scenario at a company developing web applications demonstrates how M&A can provide insights into project costs and budgets to improve estimation accuracy.
UNIT-V FMM.HYDRAULIC TURBINE - Construction and working
Measurement Analysis
1. Measurement and Analysis
Software Engineering: Project Management
Feras Tanan, Christoph Bohr, Mayar Davari,
Oleksii Donets, Jakob Eichler, Hosam Nima
2. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 2/32
O.Donets, J.Eichler, H. Nima
Introduction to Measurement and Analysis (M&A)
• What is Measurement and Analysis?
• What is used for?
• M&A includes:
Measuring the state of a project
Analyzing the measured data
Communicating the results of the analysis
3. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 3/32
O.Donets, J.Eichler, H. Nima
• SG 1 Align Measurement and Analysis Activities
• SP 1.1 Establish Measurement Objectives
• SP 1.2 Specify Measures
• SP 1.3 Specify Data Collection and Storage Procedures
• SP 1.4 Specify Analysis Procedures
• SG 2 Provide Measurement Results
• SP 2.1 Obtain Measurement Data
• SP 2.2 Analyze Measurement Data
• SP 2.3 Store Data and Results
• SP 2.4 Communicate Results
4. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 4/32
O.Donets, J.Eichler, H. Nima
SP 1.1 – Establish Measurment Objectives
Goals:
• Specify the objectives for
measuring data.
• Specify the need of data, with
respect to the goals
• Specify how to act upon the
measured data
5. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 5/32
O.Donets, J.Eichler, H. Nima
SP 1.1 – Subpractices
1. Document information needs and objectives
2. Prioritize information needs and objectives
3. Document, review, and update measurement objectives
4. Provide feedback for refining and clarifying information needs and
objectives as necessary
5. Maintain traceability of measurement objectives to identified
information needs and objectives
6. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 6/32
O.Donets, J.Eichler, H. Nima
SP 1.1 – Examples
• Reduce time to delivery
• Reduce total lifecycle cost
• Deliver specified functionality completely
• Improve prior levels of quality
• Improve prior customer satisfaction ratings
7. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 7/32
O.Donets, J.Eichler, H. Nima
Sp 1.2 – Specify Measures
• Goal: Specify measures to address the measurement objectives.
Decision depends on information which can be obtained by
doing measures
Each organization determines what measures are important for
managing their organizational goals
As much as the Measurement is precise , as much as the
decision is correct
8. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 8/32
O.Donets, J.Eichler, H. Nima
SP 1.2 - Subpractices
1. Identify and categorize candidate measures based on documented
measurement
2. Identify existing measures that already address the measurement
Objectives.
3. Prioritize, review, and update measures.
9. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 9/32
O.Donets, J.Eichler, H. Nima
SP 1. 2 - Measurment types & categories
• Measures may be either base
or derived.
• Measures can also be
categorized
• Common categories are:
Schedule and progress
Effort and cost
Size and stability
Quality
10. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 10/32
O.Donets, J.Eichler, H. Nima
SP 1. 2 – Measurement Types
• Base Measurement : Results of base measure are obtained by
direct measurement.
• Examples :
Estimated and actual measures of work product size (e.g.,
number of pages, working hours, ).
Quality measures (e.g., number of defects by severity)
• Derived measure are usually optained by combining two or more
base measures.
• Examples
Average annual profit
Defected products ratio
Earned Value
11. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 11/32
O.Donets, J.Eichler, H. Nima
1.2 - Examples
12. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 12/32
O.Donets, J.Eichler, H. Nima
SP 1.3 - Specify Data Collection And Storage
Procedures
• Specifies how measurement data is collected and stored.
• Work Products:
Data Collection Procedures
Data Collection Tools.
13. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 13/32
O.Donets, J.Eichler, H. Nima
SP 1.3 - Subpractices
1. Identify existing sources of data that are generated from
current work products, processes, or transactions.
2. Identify measures for which data are needed but are not
currently available.
3. Specify how to collect and store the data for each required
measure.
4. Create data collection mechanisms and process guidance.
5. Support automatic collection of data as appropriate and feasible.
6. Prioritize, review, and update data collection and storage
procedures.
7. Update measures and measurement objectives as necessary.
14. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 14/32
O.Donets, J.Eichler, H. Nima
1.3 - Example
15. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 15/32
O.Donets, J.Eichler, H. Nima
• Goals:
Specifying of analysis
procedure
Ensure, that analyses will
be carried out and
reported
SP 1.4 - Specify Analysis Procedures
16. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 16/32
O.Donets, J.Eichler, H. Nima
SP 1.4 – Subpractices
1. Specify and prioritize the analyses to be conducted and
the reports to be prepared
2. Select appropriate data analysis methods and tools
3. Specify administrative procedures for analyzing data
and communicating results
4. Review and update the proposed content and format
of specified analyses and reports.
5. Specify criteria for evaluating the utility of analysis
results and for evaluating the conduct of measurement
and analysis activities
17. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 17/32
O.Donets, J.Eichler, H. Nima
• Goal: Obtain the specified data
for the analysis and check the data
for completeness and correctness.
SP 2.1 - Collect Measurement Data
18. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 18/32
O.Donets, J.Eichler, H. Nima
SP 2.1 - Subpractices 1/1
1. Obtain the data for base measures
Collect all the base data as definied in SP 1.3
2. Generate the data for derived measures
Generate the derived data as definied in SP 1.3
3. Perform data integrity checks
Missing data
Out-of-bounds data values
Unusual patterns
Correlation across measures
19. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 19/32
O.Donets, J.Eichler, H. Nima
• Goal: Analyse the collected
data and identify missing
information needs. Review
the results and revision the
analysis process.
SP 2.2 - Analyze Measurement Data
20. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 20/32
O.Donets, J.Eichler, H. Nima
1. Conduct initial analyses
2. Conduct additional measurement and analysis as
necessary
3. Review the initial results with relevant stakeholders
4. Refine criteria for future analyses
SP 2.2 - Subpractices
21. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 21/32
O.Donets, J.Eichler, H. Nima
Goals:
Enable timely and cost effictive use as historical data and results
Provide sufficient context to interpret the data and the analysis
results
• What information has to be stored?
Measurement plans
Specifications of measures
Collected data sets
Analysis reports and presentations
Maintenance period for data stored
SP 2.3 – Store data and results
22. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 22/32
O.Donets, J.Eichler, H. Nima
1. Review data to ensure their completeness, integrity,
accuracy and currency.
2. Store data according to data storage procedures.
3. Make stored contents available for use only to
appropriate groups and staff members.
4. Prevent stored information from being used
inappropriately.
SP 2.3 - Subpractices 1/1
23. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 23/32
O.Donets, J.Eichler, H. Nima
SP 2.4 - Communicate Results
Goals:
• Communicate results of measurement and analysis
activities to all relevant Stakeholders (end users,.data
analysts, sponsors, data providers)
• Support decision making
• Assist in taking corrective action
24. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 24/32
O.Donets, J.Eichler, H. Nima
1. Keep stakeholders informed in a timely manner
2. Assist stakeholders in understanding the results
Communication in clear and concise manner
Results are understandable, easily interpretable and tied to
information needs
SP 2.4 - Subpractices 1/1
25. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 25/32
O.Donets, J.Eichler, H. Nima
Real Life Example
KEMWEB
Development of web
applications
Approximately 30
employees
Located at Mainz
26. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 26/32
O.Donets, J.Eichler, H. Nima
Example: Scenario
• A customer wants a new web application
• KEMWEB estimates their own costs (mainly in person
hours) to realize the application
• KEMWEB makes an offer based on the estimation
• The application is developed
• The customer pays to KEMWEB the money for the
estimated effort
27. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 27/32
O.Donets, J.Eichler, H. Nima
Example: Measurement Objectives
Information needs:
How accurate are the cost estimations for projects?
How much budget is left in a running project?
Measurement Objectives
Provide insight into actual and estimated cost of each
project during the development process
Give access to remaining budget
28. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 28/32
O.Donets, J.Eichler, H. Nima
Measure the running cost of each project (base measure)
In person hours
Measure the remaining budget (derived measure)
In person hours
Example: Specify Measures
29. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 29/32
O.Donets, J.Eichler, H. Nima
The used budget (working hours) are collected via a web
interface and stored in a database
Each employee enters the time he worked on the project at
the end of each working day
Example: Data Collection and Storage Procedures
30. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 30/32
O.Donets, J.Eichler, H. Nima
The management can access the total amount of done work
and the remaining budget in the same web application
Each day the project manager inspects the remaining
budget. If it is below the estimated budget for the remaining
work, the management is informed for further instructions
After the project is finished, the management takes a look at
the actual cost. If it differs more than 15% form the
estimation, further investigation will be started
(interviewing developers for reasons)
Example: Analysis Procedures
31. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 31/32
O.Donets, J.Eichler, H. Nima
• The Measurement and Analysis
Provides guidance on establishing a working measurement
program.
emphasizes the need for clear objectives and defined
measures
Measurement results are then collected and used to assess
progress towards these objectives.
• The best implementations of M&A focus on what is most
important to a business.
Summary
32. 10.01.2014 | Projectmanagement | Measurement and Analysis | A.Abdulaal, C.Bohr, M.Davari, | 32/32
O.Donets, J.Eichler, H. Nima
Thanks for your attention!
Editor's Notes
- Measurement and analysis is one of CMMI level 2 process area.
-Measurement and analysis: it provide support for process , product or project improvement. It involves gathering data about process,project, and products and analyzing these data in order to support decision making process regarding these areas.
-Use this process area whenever you need to measure project progress, product size or quality, or process performance in support of making decision and taking corrective action.
-Example: Measurement helps to answer crucial questions such as: “Can we commit on schedule?" and “Will the deliverable meet the requirements of the customer?"
-M&A include three steps:
collect data by measuring the process, project or whatever.
Analyze these data.
Communicate the result to the preson responsible of taking actions.
Establish Measurement objectives
The first step in M&A process is to identify the objectives of the measurement and analysis,
i.E our objective is to provide a product with 100% unknown defects, or Reduce time to delivery.
what information are needed for the analysis, what are the corrective actions to be taken after examining the end results of analysis.
Think about why you are collecting the measures and what need the measure will be addressing.
Objectives may cover a broad range of issues such as budget, deadline, quality and product performance.
• Reduce time to delivery
• Reduce total lifecycle cost
The recommended subpractices for this task are:
-Documenting the information needs and objectives.
-Prioritize the information needs , of course in accordance to the resources available, because you cannot subject all initially identified.
-Measurement objectives should be documented and reviewed by the management and stakeholder and updated if necessary in order to ensure that the analysis properly identified information needs and objectives. It is possible to the users of the measurement and analysis to be involved in this action. In addition, many times measures are collected but not use, so with this practice we can minimize the risk that these measures will not be used.
-Using the review from the previous practice we can provide feedback to further clarify ambiguous objectives and remove the conflicts.
We should maintain traceability of measurement objectives because these objectives may change over time.
The process of identifying objectives and information can be iterative process , because we cannot come up with the objective from the first time, so we have to identify objectives, document them , review them and provide feedback to improve them.
Why we have to specify the measures clearly?
-Because people look into measures from different aspect and have different views, so they should be made crystal clear to prevent ambiguous measures. In additions, they are important because the corrective decisions after the M&A process will depend on the information which can be obtained by doing measures. So as much as the measurements are precise , as much as the decision will be correct.
-Identify candidate measures for each measurement objective. And they could be classified into different categories , measures for cost, measures for quality , measures for information assurance.
-measures can be identified from already existed measurements which was identified early somewhere in the organisation.
we have to identify measures based on the measurement objectives and Assign to the measures their suitable category, ex. cost , quality, Size and stability
Measures may have been identified before in some part of the organisation , so we can use them again.
The main responsibility for this specific practice is to identify the measurement‘s data collection and storage procedures. The explicit specification of methods for data aquisition guruantees that the right data is collected the right way and ensures that it is accessible and available for later use.
The result work product of this practice would be:
-Data Collection procedures.
-Data Collection Tools.
The first sub practice is to identify the sources of data that are generated from the current work product, process, or transactions. These sources may have been identified when specifying the measures. These sources could be people, software that collect data, etc.
The second sub practice is to identify which measures require data which is not available.
The thid sub practice is to identify for each measurement objective the procedures of data collection and storage.
Some questions need to be answered in order to acheive this practice:
Have the frequency of collection and the points in the process where measurements will be made been determined?
Timeline required to move measurement results from points of collection to repositories?
Who is responsible for obtaining data, data storage, data retrieval, and data security?
Have necessary supporting tools been developed or acquired?
The next subpractice is to provide a process guidance on correct procedures to people who are responsible for doing the work. In addition, training should provided as needed to clarify the process required for the collection of complete and accurate data and to minimize the load on those who provide and record data.
The fifth sub practice is to provide support for automatic collection of data as appropriate and feasible
Examples of such automated support include the following:
• Time stamped activity logs
• Static or dynamic analyses of artifacts
The Data collection and storage can be enhanced by reviewing and examining collection and storage procedures and methods for their appropriateness and feasibility and suggest some improvement to the current procedures and methods.
The last sub practice is to update measures and measurement objectives as necessary according to the results and sugesstion from the previous sub practice.
Here is an example of such work product of this specific practice.
As shown in the figure in the fourth column:
The data collection procedure and storage for each measurement objective is identified.
For the first objective: the reports is collected every Monday and recorded in file report.doc.
The second objective : the data is collected using a bugtrack program and recorded in bugtrack.xls.
In this specific practice we have to identify the analysis procedures to ensure that the appropriate analysis will be conducted.
It help ensure that all data which will be gathered will be used for the analysis. Also ,the quality of data should
be considered to help select the appropriate analysis procedure and evaluate the results of the analysis.
1.Specify how measurement values analyzed and reported
Specify the analyzes to be performed and the reports to be prepared and in order of priority (explicitly aligned with the documented measurement objectives, audience accessible)
- The analyses explicitly address the documented measurement objectives.
- Presentation of results is clearly understandable by the audiences to whom the results are addressed.
-Priorities may have to be set for available resources.
2- Specify data methods and tools :
Choice of visual display and other presentation techniques assurance that will be conducted and reported, appropriate tests
also a test that actually do the necessary data is collected.
3- Identify procedures for the analysis process:
-Who is responsible for doing what?
-Timeline to analyze the data and conduct the result.
-How and where Communicating result will be done.
4-All of the proposed content and format are subject to review and revision,
including analytic methods and tools, administrative procedures,
and priorities. Relevant stakeholders consulted should include
end users, sponsors, data analysts, and data providers
5- • The results are provided in a timely manner, understandable, and used
for decision making.
• The work does not cost more to perform than is justified by the benefits it
provides
The data necessary for analysis are obtained and checked for completeness and integrity.
Example Work Products
1. Base and derived measurement data sets
2. Results of data integrity tests
In this practice Base and derived data should be collected, and calculated from project records or somewhere in the organisation according to the Storage and Collection procedures specified in 1.3 Specific Practice.
After that the data should be checked for completenes, correctnes and consisitency and .
After collecting the data we should make our planned analysis.
First we conduct out initial analysis.
Initial analysis can suggest additional analysis, may need additional data and/ or recollecting and recalculating the data.
Reviewing the initial results before their release can prevent needless misunderstandings and lead to improvements in the data analysis and
presentation.
Lessons that can improve future efforts are often learned from conducting data analyses and preparing results ways to improve measurement specifications and data collection procedures can become apparent as can ideas for refining identified information
needs and objectives.
Storing Measurement results and its related information enable timely and cost effective use of data.
The recommended subpractices for this specific practics are:
Revision of Data to ensure completenes, correctness and accuracy.
Storing data accoring to the storage procedure
We should provide access control to the stored data, so that only the appropriate people access it in the appropriate way.
For example : Measures used to improperly evaluate the performance of people or to rank projects. And they should not be used to threaten people in someway.
Motivation: To support decison making and assist in taking corrective action the results of the measurement and analysis process have to be communicated to relevant stakeholders. Relevant stakeholders can be end users, sponsors, data anlalysts and data providers.
Keep stakeholders informed about the analysis result in timely manner. And help them understand the results.
Results are communicated in a clear and concise manner appropriate
to relevant stakeholders. Results are understandable, easily interpretable,
and clearly tied to identified information needs and objectives
The communication of results should be
clear about the following:
• How and why base and derived measures were specified
• How data were obtained
• How to interpret results based on the data analysis methods used
• How results address information needs
The PM or other project staff members review the measurement results to determine if measurements objectives are being met, finalize the results and report them in status or metrics reports in accordance with the project’s measurement plan. Note that the reporting of measurement results may be a “self-service” step, depending on the project’s storage and distribution media (e.g., website on an intranet) and retrieval tools (e.g., browser software). These results are used by the PM to re-plan in accordance with the project’s measurement plan or PMP. See the Project Monitoring and Control Process for SSC Pacific, reference (g), for more information on re-planning.