Measurement Plan Presentation

Concordia University

Software Project Management

SOEN 6841

Project Presentation

On

Project Measurement Plan

Hassan Khalid	27885490
Asad Iftikhar	27094906
Mohammad Tuaha	40026959
Dinraj Majumder	40039931
Eric Watat Lowe	27720270
Shubhangi Sheel	40004793
Shubham Singh	40004796

Concordia University

Slide-2

❏Project Description.

-Commonwealth Software Inc issues.

-Business Goal.

❏Description of each of the 7 steps.

❏Conclusion.

Slide-3

Brainstorming Additional Sub Goal Statements

  - The name suggests after team discussion we identified the main objective (goal)

Operationalize Goals

 - we chose two of the sub goals identified in step 1 to carry on the measurement activity.

Success Criteria and Indicators

 - The success criteria and indicators for the identified sub goals are mentioned focusing on improving testing processes.

Sub goals to Strategies and Activities

 - We listed the details on strategies and activities to be carried on to achieve our chosen sub-goal.

Worksheet: Analysis and Progress Indicators

 - We developed our analysis strategy and identified progress indicators ..

Identifying The Data Elements to Be Collected, Availability, and Source

 - Involved identifying the data elements that need to be collected to formulate our success criteria, further tracking the progress, and assessment of the same.

Planning Tasks

 -Finally, in seventh step we tried to highlight the processes that must be available for successful accomplishment of the plan.

Slide-4

Step 1 - Brainstorming Additional Sub Goal Statements

Questions related to Improve testing processes

Entities Managed by Project Manager

•Developers

•Testing team

•Documentation

•Project Plan

•Test Plan and strategy

•Pre-releases and source code.

•Effort estimation and schedule estimation of software

•Product Development

•Software Process Testing

•Risk Management

•Customer can change requests (work in process)

Slide-5

Identified Sub-Goals

❏Define clear Service Level Agreements (SLA) / Estimated Time of Accomplishments (ETA) and comply with the same.

❏To have a ticketing system in place, so all incidents can be recorded, tracked and followed properly and to be resolved in timely manner.

❏Track the contributors of the module in question to have them look into the issue, encouraging them for better and timely patch / fix to the issue.

❏Testing processes to be more robust and thorough adhering to the standards.

Sub Goal 1: Track the contributors of the module in question to have them look into the issue, encouraging them for better and timely patch / fix to the issue.

Slide-6

Step 2 - Operationalize Goals

Perspective: Software development manager

Object of interest: Code

Purpose: In order to minimize SLA breaches, we aim to track contributor’s progress through status reporting which ensures that the task will be completed within defined timeline.

Quality focus and Perspective

Examine the Testability, Maintainability and Reusability from the perspective of the code.

Environment and Constraints

Technical reviews and status updates to be carried on by Software Developers, Testers and Project Manager. 

Slide-7

Step 2 - Operationalize Goals

Sub Goal 2: Testing processes to be more robust and thorough adhering to the standards.

Perspective: Software development manager

Object of interest: Test Scenarios / Test cases

Purpose: To improve the testing process in order to reduce defects in new software release and minimize user complaints.

Quality focus and Perspective

Examine the quality, Stability, and correctness of the code from the viewpoint of the testers/ users.

Environment and Constraints

User acceptance testing and Software testing to be conducted in order to ensure the code compliance with the requirements.

That’s all my part. Now I would to invite subhangi sheel to countinue

Slide-8

Step 3 - How do we define Success?

❏What is the number of defects propagation reduced in the last deliverable?

❏What is the total time increase for resolving failures by last deliverable?

❏How much planned, actual and actual ok per test cases increased?

❏What percentage of classes are in the zone of excellent, good and poor?

Slide-9

Step 4 - SubGoals to Strategy Activity

Strategy 1:

Aim to discover defects early in the development stage with Test-Driven Development (TDD) - In TDD, test cases are identified before development of the module.

Strategy 2:

Ensure that code added after each iteration does not break previews, tested and approved code to limit and track defects propagation. This could be supported by the use of automated tools.

Slide-10

Step 5 - Analysis and Progress Indicator

Strategy

Ensure that code added after each iteration    does not break    previews, tested and approved code to limit and track defects propagation. This could be supported by the use of automated tools.

Activity   definitions Regression Test and unit tests case, Debugging, progress reporting, Update the defects tracker.

Questions about the Activity

•How much code is covered by the test cases?

•What is the reduction rate of defects propagation?

•What is the acceptable Testing progression rate? (test case/hours)

•How much test cases must be successful?

•How much time should it take to resolve a client request?

To be continue ….

Contact to author. Mohammad Tuaha