This PPT describes about the "Project Tracking" activity & statistical process control at Infosys. It covers the entire topic such as project tracking, activities tracking, defect tracking, issue tracking, etc. It covers all main activity of SPC such as SPC analysis, control chart for SPC etc. This PowerPoint presentation is of "Software Project Management".

1. BIRLA INSTITUTE OF TECHNOLOGY, MESRA
JAIPUR CAMPUS
TOPIC : PROJECT TRACKING /& SPC
BY :
TARUN TIWARI (MCA/25007/18)
MEGHAJ KUMAR MALLICK (MCA/25017/18)
2ND YEAR, 4TH SEMESTER

2. PROJECT TRACKING BY TARUN TIWARI

3. PROJECT TRACKING
• Let us examine the basic project tracking at Infosys.
• Once a detailed project plan is made which consist of all
details of project such as start date & end date, and people
assign for project.
• At least project manager must track the execution of these
task.
• That endeavour constitutes activity tracking.
• The project manager must track the unresolved issues that
crop up & the defect that are detected.
• The outcome is captured in a status report, which is also
distributed to the senior management.

4. ACTIVITIES TRACKING
• The basic task in project tracking is to ensure that planned
activities are done on time.
• At Infosys the activities are scheduled using Microsoft
Project(MSP). It is also used for project tracking.
• The project manger checks the status of the schedule task and
updates the status in MSP.
• When the activity is finished it is marked 100% in MSP.
• MSP provide the feature to track the status of individual task .
• A project manger can determine which higher level task are
lagging behind, what percentage of task has been done.
• Based on the activities completed ,actual time they took, the
project manager reschedule the remaining task.

5. DEFECT TRACKING
• Infosys uses a defect control system for tracking control.
• Once information is entered in this system, it remains open
until it has been fixed.
• The defect is marked as close when its removal has been
verified.
• In this way each defect is logged and tracked to closure.
• Sometimes, project managers track the state of a defect by
recording the date of submission & the date of closure for
each defect.
• The project manager can check the overall defect injection &
defect closure, information about gap between the defects
submitted and the number of defect is in control.

7. ISSUE TRACKING
• Inevitably, many small jobs or clarification come up during a
project. These problem are called issues.
• Managing issue is an important task for any project manager
because they can be numerous & can potentially delay a
project.
• To solve such kind of problem there is a provision of using a
issue log.
• All the issues are recorded as they arise, along with related
information.
• When the issue are closed they are marked as close.
• The project manger use a spreadsheet, maintain document,
use issue tracker utility, or use the defect tracking system.

9. STATUS REPORT
• Status report are the main mechanism for regularly communicating
the state of project to senior management and the customer.
• The party who receive status report are specified in the project
management plan.
• Status report are generated weekly & contain these items.
• Customer complain.
• Milestone achieve this week.
• Milestone missed this week and the reason for them.
• Milestone planned for the next week.
• Issues requiring clarification or attention.
• Escalation, if any
• Estimated work versus available time by milestone.

10. SPC BY MEGHAJ KR. MALLICK

11. ACTIVITY LEVEL ANALYSIS USING SPC
• To provide finer control, activity-level analysis is also done at
Infosys.
• In activity-level analysis, some metrics are analyzed
immediately after a task is performed.
• The analysis is used to evaluate the effectiveness of the task
performance.
• If the task has not been performed satisfactorily, immediate
action can be taken to correct it and to prevent a repetition.
• Activity-level analysis is usually done using statistical process
control (SPC).

12. SPC ANALYSIS
• At Infosys, reviews and unit testing have been identified as
the two tasks for which SPC is applied.
• Using control charts, the project manager immediately
evaluates the effectiveness of a review or a unit test.
• If the performance is not satisfactory, necessary action can be
taken.
• The focus of activity-level monitoring is on the coding-related
activities of reviews and unit testing.
• Activity-level monitoring and control of unit testing the other
activity for which SPC is applied.

13. CONTINUED
• The guidelines given earlier for testing can be used to decide
which actions are needed (for analysis, project managers can
use supporting information about effort spent on the task,
effort expended on previous tasks, and defects found).
• Figure shows the control chart for defect density for unit
testing of one programming language.
• The defect density can be plotted in terms of the number of
defects per LOC or the number of defects per person-hour.

14. CONTROL CHART FOR SPC

15. CAPABILITY BASELINE FOR UNIT TESTING

16. CONCLUSION
• As with reviews, project managers can use the SPC tool to
implement activity-level control of unit testing.
• This tool contains relevant past performance data such as the
defect injection rate, the defect removal percentage, and so
on.
• Using this data, it determines the control limits as well as
expected limits.
• When the performance data of a unit test is entered, the tool
immediately tells whether or not the performance is outside
the limits.