A Study On Risk Management in Brisk Technologies at Bangalore Interim

A STUDY ON RISK MANAGEMENT IN BRISK
TECHNOLOGIES AT BANGALORE
CHAPTER-1
1
1. INTRODUCTION
Every organization has a mission. In this digital era, as organizations use automated information
technology (IT) systems to process their information for better support of their missions, risk
management plays a critical role in protecting an organization’s information assets, and therefore
its mission, from IT-related risk. An effective risk management process is an important
component of a successful IT security program. The principal goal of an organization’s risk
management process should be to protect the organization and its ability to perform their
mission, not just its IT assets. Therefore, the risk management process should not be treated
primarily as a technical function carried out by the IT experts who operate and manage the IT
system, but as an essential management function of the organization.
There are many risks involved in creating high quality brisk technologies software on time and within
budget. However, in order for it to be worthwhile to take these risks, they must be compensated for
by a perceived reward. The greater the risk, the greater the reward must be to make it worthwhile to
take the chance. In brisk technologies software development, the possibility of reward is high, but so
is the potential for disaster. The need for brisk technologies software risk management is illustrated in
Gilb’s risk principle. “If you don’t actively attack the risks, they will actively attack you”. In order to
successfully manage a brisk technologies software project and reap our rewards, we must learn to
identify, analyses, and control these risks. This paper focuses on the basic concepts, processes, and
techniques of brisk technologies software risk management.
There are basic risks that are generic to almost all brisk technologies software products. Although
there is a basic component of risk management inherent in good project management, risk
management differs from project management in the following ways:
2
1. Avoiding software project disasters, including run away budgets and schedules, defect-ridden
software products, and operational failures.
2. Avoiding rework caused by erroneous, missing, or ambiguous requirements, design or code,

which typically consumes 40-50% of the total cost of software development.
3. Avoiding overkill with detection and prevention techniques in areas of minimal or no risk.
4. Stimulating a win-win software solution where the customer receives the product they need and
the vendor makes the profits they expect.
1.1 PROBLEM STATEMENT
Software development is activity that uses a variety of technological advancements and requires high
levels of knowledge. Because of these and other factors, every software development project contains
elements of uncertainty. This is known as project risk. The success of a software development project
depends quite heavily on the amount of risk that corresponds to each project activity. As a project
manager, it’s not enough to merely be aware of the risks. To achieve a successful outcome, project
leadership must identify, assess, prioritize, and manage all of the major risks. The goal of most software
development and software projects is to be distinctive—often through new features, more efficiency, or
exploiting advancements in software. Any software project executive will agree that the pursuit of such
opportunities cannot move forward without risk. Because risks are painfully real and quite prevalent on
all software projects, it’s critically necessary that stakeholders work hard to identify, understand, and
mitigate any risks that might threaten the success of a project. For projects that have time and cost
constraints, our experience shows most clearly that successful software
3
development efforts are those in which risk mitigation is a central management activity.
1.2 NEED FOR THE STUDY
Risk management means risk containment and mitigation. First, you’ve got to identify and plan.
Then be ready to act when a risk arises, drawing upon the experience and knowledge of the entire
team to minimize the impact to the project.
Risk management includes the following tasks:
Identify risks and their triggers

Classify and prioritize all risks
Craft a plan that links each risk to a mitigation
Monitor for risk triggers during the project
Implement the mitigating action if any risk materializes
Communicate risk status throughout project
Identify and Classify Risks
Most software projects are inherently risky because of the variety potential problems that might
arise. Experience from other software projects can help managers classify risk. The importance here
is not the elegance or range of classification, but rather to precisely identify and describe all of the
real threats to project success. A simple but effective classification scheme is to arrange risks
according to the areas of impact.
4
1.3 OBJECTIVES OF THE STUDY
The main objective of the study is to know the overall financial position of the Brisk Technologies
from 2018-2019.
• To study the project performance of the Brisk Technologies.

• To study the sources and applications to the risk.
• To find out the financial stability of the Brisk Technologies.
• To know how effectively the Brisk Technologies is using its resources
• To measure the extent to which the company’s using its needs through project schedule.
• To make an overall view on theoretical approach of Project Flow and Software flow
statements.
1.4 SCOPE OF THE STUDY

Very simply, a risk is a potential problem. It’s an activity or event that may compromise the success
of a software development project. Risk is the possibility of suffering loss, and total risk exposure to
a specific project will account for both the probability and the size of the potential loss. Guesswork
and crisis-management are never effective. Identifying and aggregating risks is the only predictive
method for capturing the probability that a software development project will experience unplanned
or inadmissible events. These include terminations, discontinuities, schedule delays, cost
underestimation, and overrun of project resources.
This research project is conducted to study the risk factors affecting the software quality. This study
is conducted under three main categories. They are quality of testing, test planning and quality
assurance team. In this study, a data collection survey is conducted, among Software quality
managers and quality leads of Software development companies in the Bangalore. This study will
fully focus on risk factor under IT SECTOR.
· Avoiding risks may also mean avoiding opportunities

· Not all risks can be avoided
5
· Avoiding a risk in one part of the project may create risks in other parts of the project.
Do we know enough? If we don’t know enough, we can plan to “buy” additional information
through mechanisms such as prototyping, modeling, simulation, or conducting additional research.
1.5 INDUSTRAL PROFILE
Introduction to IT sector
Information Technology (IT) industry in India is one of the fastest growing industries. Indian IT
industry has built up valuable brand equity for itself in the global markets. IT industry in India
comprises of software industry and information technology enabled services (ITES), which also
includes business process outsourcing (BPO) industry. India is considered as a pioneer in software
development and a favorite destination for IT-enabled services. The origin of IT industry in India can
be traced to 1974, when the mainframe manufacturer, Burroughs, asked its India sales agent, Brisk
Technologies (BT), to export programmers for installing system software for a U.S. client.
6
Today, Indian IT companies such as Tata Consultancy Services (TCS), Wipro, Infosys, HCL etc are renowned
in the global market for their IT prowess.
Some of the major factors which played a key role in India's emergence as key global IT player are:
Indian Education System
High Quality Human Resource
Competitive Costs
Infrastructure Scenario
Information technology (IT) is the application of computers to store, retrieve, transmit and
manipulate data, often in the context of a business or other enterprise. IT is considered a subset
of information and communications technology (ICT).
Brisk Technologies is an IT services, business solutions and outsourcing organization that

delivers real results to global businesses, ensuring a level of certainty that no other firm can
match. BT offers a consulting-led integrated portfolio of IT and IT-enabled services delivered
through its unique Global Network Delivery Model (GNDM), recognized as the benchmark of
excellence in software development. BT is part of the Tata group, one of India’s largest industrial
conglomerates and most respected brands. BT has over 238,583 of the world’s best-trained IT
consultants in 42 countries. Revenue of $10.17 billion (fiscal year ending March 31, 2012). BT
Integrated Quality Management System (iQMS) integrates processes, people and technology
maturity through various established frameworks and practices, including IEEE, ISO 9001: 2000,
CMMi, SW-CMM, P-CMM and Six-Sigma.
7
India is the world's largest sourcing destination for the information technology (IT) industry,
accounting for approximately 67 per cent of the US$ 124-130 billion market. The industry
employs about 10 million workforces. More importantly, the industry has led the economic
transformation of the country and altered the perception of India in the global economy. India's
cost competitiveness in providing IT services, which is approximately 3-4 times cheaper than the
US, continues to be the mainstay of its Unique Selling Proposition (USP) in the global sourcing
market. However, India is also gaining prominence in terms of intellectual capital with several
global IT firms setting up their innovation centers in India.
FEATURES OF THE IT INDUSTRY AT A GLANCE
Economies of scale for the information technology industry are high. The marginal cost of
each unit of additional software or hardware is insignificant compared to the value addition
that results from it.
Unlike other common industries, the IT industry is knowledge-based.
Efficient utilization of skilled labor forces in the IT sector can help an economy achieve a
rapid pace of economic growth.
The IT industry helps many other sectors in the growth process of the economy including the
services and manufacturing sectors.
This statistic illustrates the amount of revenue generated by the IT industry worldwide from 2005
to 2012, and also includes a forecast for 2013 and 2016. The source estimates that in 2016, more
than 1,357 billion euro revenue will be made through software, hardware and IT services.
FUTURE PROSPECTUS OF IT INDUSTRY

India is the topmost offshoring destination for IT companies across the world. Having proven its
capabilities in delivering both on-shore and off-shore services to global clients, emerging
technologies now offer an entire new gamut of opportunities for top IT firms in India. Social,
8
Mobility, Analytics and Cloud (SMAC) are collectively expected to offer a US$ 1 trillion
opportunity. Cloud represents the largest opportunity under SMAC, increasing at a CAGR of
approximately 30 per cent to around US$ 650-700 billion by 2020. The social media is the
second most lucrative segment for IT firms, offering a US$ 250 billion market opportunity by
2020. The Indian e-commerce segment is US$ 12 billion in size and is witnessing strong growth
and thereby offers another attractive avenue for IT companies to develop products and services to
cater to the high growth consumer segment.
The IT industry has also created significant demand in the Indian education sector, especially for
engineering and computer science. The Indian IT and ITeS industry is divided into four major
segments – IT services, Business Process Management (BPM), software products and
engineering services, and hardware.
The IT-BPM sector which is currently valued at US$ 143 billion is expected to grow at a
Compound Annual Growth Rate (CAGR) of 8.3 per cent year-on-year to US$ 143 billion for
2015-16. The sector is expected to contribute 9.5 per cent of India’s Gross Domestic Product
(GDP) and more than 45 per cent in total services export in 2015-16.
The Indian IT sector is expected to grow at a rate of 12-14 per cent for FY2016 in constant currency
terms. The sector is also expected triple its current annual revenue to reach US$ 350 billion by FY
2025, as per National Association of Software and Services Companies (NASSCOM).
9
India, the fourth largest base for new businesses in the world and home to over 3,100 tech start-
ups, is set to increase its base to 11,500 tech start-ups by 2020, as per a report by NASSCOM and
Zinnov Management Consulting Pvt Ltd.
India’s internet economy is expected to touch Rs 10 trillion (US$ 146.72 billion) by 2018,
accounting for 5 per cent of the country’s GDP, according to a report by the Boston Consulting
Group (BCG) and Internet and Mobile Association of India (IAMAI). India’s internet user base
reached over 350 million by June 2015, the third largest in the world, while the number of social
media users grew to 143 million by April 2015 and smartphones grew to 160 million.
BT has a strong network of strategic and solution partners with a joint objective of helping its
customers become high-performance businesses by maximizing the value of their technology
investments. Established in 1968, BT has grown to its current position as the largest IT services
firm in India on the basis of its outstanding service record, collaborative partnerships, innovation
and corporate responsibility.
For most software industrial, we can define five main risk impact areas:
New, unproven technologies

User and functional requirements
Application and system architecture
Performance
Organizational
New, unproven technologies. The majority of software projects entail the use of new technologies.
Ever-changing tools, techniques, protocols, standards, and development systems increase the
probability that technology risks will arise in virtually any substantial software engineering effort.
Training and knowledge are of critical importance, and the improper use of new technology most
often leads directly to project failure.
User and functional requirements. Software requirements capture all user needs with respect to the
software system features, functions, and quality of service. Too often, the process of requirements
definition is lengthy, tedious, and complex. Moreover, requirements usually change with discovery,
10
prototyping, and integration activities. Change in elemental requirements will likely propagate
throughout the entire project, and modifications to user requirements might not translate to
functional requirements. These disruptions often lead to one or more critical failures of a poorly-
planned software development project.
Application and system architecture. Taking the wrong direction with a platform, component, or
architecture can have disastrous consequences. As with the technological risks, it is vital that the
team includes experts who understand the architecture and have the capability to make sound design
choices.
Performance. It’s important to ensure that any risk management plan encompasses user and partner
expectations on performance. Consideration must be given to benchmarks and threshold testing
throughout the project to ensure that the work products are moving in the right direction.
Organizational. Organizational problems may have adverse effects on project outcomes. Project
management must plan for efficient execution of the project, and find a balance between the needs
of the development team and the expectations of the customers. Of course, adequate staffing
includes choosing team members with skill sets that are a good match with the project.
Risk Management Plan
After cataloging all of the risks according to type, the software development project manager should
craft a risk management plan. As part of a larger, comprehensive project plan, the risk management
plan outlines the response that will be taken for each risk—if it materializes.
Monitor and Mitigate
To be effective, software risk monitoring has to be integral with most project activities. Essentially,
this means frequent checking during project meetings and critical events.
Monitoring includes:
11
Publish project status reports and include risk management issues

Revise risk plans according to any major changes in project schedule
Review and reprioritize risks, eliminating those with lowest probability
Brainstorm on potentially new risks after changes to project schedule or scope
When a risk occurs, the corresponding mitigation response should be taken from the
risk management plan.
Mitigating options include:
Accept: Acknowledge that a risk is impacting the project. Make an explicit decision to accept the
risk without any changes to the project. Project management approval is mandatory here.
Avoid: Adjust project scope, schedule, or constraints to minimize the effects of the risk.
Control: Take action to minimize the impact or reduce the intensification of the risk.
Transfer: Implement an organizational shift in accountability, responsibility, or authority to other
stakeholders that will accept the risk.
Continue Monitoring: Often suitable for low-impact risks, monitor the project environment for
potentially increasing impact of the risk.
Communicate
Throughout the project, it’s vital to ensure effective communication among all stakeholders,
managers, developers, QA—especially marketing and customer representatives. Sharing
information and getting feedback about risks will greatly increase the probability of project success.
RISK ASSESSMENT MATRIX FOR ENTERPRISE BUSINESS OWNERS

Enterprise business owners can use this risk assessment matrix to list out the thresholds for measuring
risk in various categories on an ongoing basis. Under “Cost,” for example, the dollar amount will vary,
but a “5” would be a significant portion or even majority of a time period’s forecasted income and “1”
would be a small amount. Using this matrix, an enterprise business owner can sketch out and keep
track of where the biggest risks may lie, and then update it weekly or
12
biweekly as the project progresses. Everything listed in the top two lines are usually
businesscritical and this matrix helps keep the most urgent issues front and center.
Issues might include IT security, global and national compliance issues if applicable, delivery of
vendor shipments or contributions, launching a new product line, political unrest, and more.
13
RISK ASSESSMENT MATRIX FOR SMALL BUSINESS OWNERS
Small business owners can use this risk-assessment matrix to list out the thresholds for measuring
risk in various categories on an ongoing basis. Like the matrix above, the dollar amount under
14
“Cost” will vary for example, but a “5” would be a significant portion or even majority of the time
period’s forecasted income, while “1” would be a small amount. Using this matrix, a small
business owner can sketch out where the biggest risks may lie, and then update this weekly or
biweekly. Everything listed in the top two lines are usually business-critical and this matrix helps
keep the most urgent issues front and center.
Issues might include IT security, compliance issues if applicable, delivery of vendor shipments or
contributions, launching a new product line, and more.
15
1.6 COMPANY PROFILE

Brisk Techno Private Limited was established 9 years back as a Telecom Implementation and
Software Development Company, leading its way towards progress. It started its IT division after
two years of its birth. Now it is a one of the India's leading IT & Telecom Companies and among
the top Telecom / Software Development & training companies. We have provides complete
16
endto-end outsourcing solutions for various industries. It has a comprehensive set of solutions
Telecom & IT Companies.
Brisk Techno Pvt. Ltd. has worked with over 200 Client worldwide, Including - Reliance
Communication, Northern Railway, BSNL, ESSAR Telecom, GTL, WTTIL(TATA) AT&T,
Quippo Telecom, Webtech, Mach Well Tools, Uniwise ,S.D Engineers, Ashari Technology
and Many More....
Brisk Techno Pvt. Ltd. serves customers in India and has presence across 4 continents. The
company offers the following range of enterprise services and solutions to meet varying
partner/customer requirements.
Brisk Techno for its Software services and certified for its IT & Telecom services.
The Group operates in Eight Segments:
•IT Enabled Services • Professional Training & Placement
•Infra & Maintenance • College Training

•Software Development • Summer Training
•Education and Training • Vocational Training
•Business Process
Management • Corporate Training
•Telecom Enabled Services • PDP

•Outsourcing • Placement Aptitude Test Training
•Event Management
17
Brisk Techno has three delivery Offices in India, Lucknow, Meerut & Delhi.
JOB FAIR EVENT
Some reputed companies visit SIPL campus or our collaborative college campuses for placement.
For getting updated information about these drives, visit our website http://www.brisktechno.com.
In the June 2010, Twelve Companies have visited CERT College Meerut For Campus
Placement in an Job event organized by SIPL and has selected 175 candidates, out of which the
biggest recruiter were New Delhi, Gurgaon, Noida, Faridabad, Lucknow Based Companies, SIPL
has established itself as a pioneer Engineers Training Company, SIPL also provides Student and
Professional Membership, R&D, Tech-Fests and many other technical activities. SIPL has already
conducted On Campus Training Programs at many Colleges.
These training programs have been started to fulfill the requirements of various SIPL collaborative
companies.
CLIENT & PARTNER

1 Aegis (Essar Group) 21 Mercer India Gurgaon
2 Ambit Switch Gear 22 Metrotel
3 Ashari Technology Pvt.Ltd. 23 Net Wing
4 Aura System Pvt. Ltd. Noida 24 Nokia Siemens Networks (NSN)
5 Bata Faridabad 25 Northern Railway
6 Bharat Sanchar Nigam Limited 26 Optimum Solutions Pvt. Ltd. Delhi
7 Blue Star India, Mumbai 27 Orbit InfoTech Delhi
8 Bonanza 28 Poly Diamond
9 CMS Info System 29 Quippo Telecom Infrastructure Ltd.
18
10 Eclipse Systems Pvt. Ltd. Noida 30 Reliance Communication

11 Effectron Luminex Ltd. Delhi 31 Religare Enterprises Limited
12 Elin Electronics Ltd. Ghaziabad 32 S.D Engineers Pvt.Ltd.
13 Essar Telecom Infrastructure Pvt. Ltd. 33 TVS Telecom
14 Fizer 34 Ultra Motors India Pvt. Ltd. Delhi
15 Godrej, Faridabad 35 Uniwise Consulting Pvt.Ltd.
16 GTL Limited 36 Webtech Engineers Pvt.Ltd.
17 Havells India Ltd. Noida 37 Wipro BPO
18 Huawei Technology India Pvt. Ltd. 38 Wipro Telecom
19 i-Gate 39 WTTIL (TATA)
20 Mech Well Tools & Gauges Pvt Ltd. 40 ZTE Corporation
BANGALORE OFFICE
Brisk Technologies
#30/1, Leemans Complex Above Rehham’s Restaurant 3rd Floor,
Cunningham Road,
Bangalore- 560052
Email: sudhakar.m1983@brisktechnologies.net
Phone: 99642575597/ 9964278607
Mobile: 9886309117
LUCKNOW OFFICE:
nd
Address: 4/285 2 Floor, Vivek Khand, (Opp. Petrol Pump)
Gomti Nagar, Lucknow (U.P.)-226010
Phone No: +91-522-4067636
Fax No: -0522-4067636
MEERUT OFFICE:
19
Address: A - 3rd Floor, 92/1 Metro Arcade Complex,

Tej Garhi -Near BSNL Office. Meerut -250001 (U.P.)
Phone No: 0121-4059827
Fax No: 0121-4059827
Project & Business Head Bangalore Mr. PUSHPENDRA SINGH

Project & Business Head Meerut Mr. Samir Husain
For Any Query Contact Shivendra Singh
Email Id shivendra@Brisk Techno.com

Mob No. +91-9598072232, +91-9415872506
SMS “BT” @ 5607008

For queries email us at
training@Brisk Techno.com hr@Brisk Techno.com
Website: http://www.BriskTechno.com
20
CHAPTER-2
21
2.1 RESEARCH AND METHODOLOGY

The chief criteria for the validity of any research study lies in its methodology. An enquiry would
prove a failure if it is not done along certain methodical lines.
The method of study adapted to carry out the project work is mainly through personal enquiry
with the Account’s Manager. The study comprises of the company‘s operations and the
techniques followed by them.
The data extracted from the annual reports of the company was analyzed and further reduced to
tables. To make it pictorial and easier to grasp and understand the data was represented in
graphical forms.
SOURCES OF THE STUDY:
This is the study entirely based on:
• Personal discussion.
Annual Project reports
Published sources.
• Simple statistical
analyses.
There are mainly two types of data sources they are as follows:
PRIMARY DATA:
The data are originally collected by an investigator or agency for the first time for a statistical
investigation and used by them in the statistical investigation and used by them in the statistical
analysis and termed as primary data this data are collected directly from the source for first time.
SECONDARY DATA:
22
The data published or unpublished which have already been collected and processed by some
agency or person and take over from there and used by any other agency for their statistical work
and termed as secondary data as for as second agency is concerned. The second agency if and
when it possible and files one who late uses this data.
Both primary and secondary data have collected for the study purpose primary interviewing
certain executive who were and work experience in the nature in order to gain as such as
information as possible.
Most of the data collected is secondary in nature and include:

Annual project report of the company.

Other books and accounts maintained by the company.

Internet

Text books relating to financial management, management accounting
PROCEDURE ADOPTED:
The questionnaire will prepare through direct contact with respondents.

Sample Size & Sampling Technique:
The study covers a sample of 100 employees of companies. The Respondents will be selected on a
Sample Random basis from the following categories of the employees,
i. Project Manager
ii. Team leaders
Iii.Developers/Programmers

Statistical Tool: Sample percentage

Sample Variety: Respondents will select from the Software Risk management category.
So the Sample Size is limited to 100 due to availability and the schedule of the employees.
23

Sampling Procedure: The sampling method will use as a Random Sampling. The
sampling unit mostly from Executives and non-executives. The sample size is fixed to 40
respondents; the sampling procedure is response from the respondents.

Statistical Tool: In this research various percentages were identified in the analysis and
these were presented pictorially by the pie charts in order to have a better quality.

Questionnaire Design: A structured questionnaire was designed consisting of close-ended
questions and were distributed to the respondents personally to get their responses.
24
CHAPTER-3
DATA ANALYSIS AND INTERPRETATION

DATA ANALYSIS AND INTERPRETATIONS
TABLE 4.1: Based on respondent gender
Gender Respondents Percentage

Male 69 92%
Female 6 8%
Total 75 100%
Analysis:
The above table clearly indicates 92% respondents are male and 8% female, out of 100%
respondents.
Graph 4.1:
Respondents percentage
100%
total
75
8%
Female
6
92%
Male
69
Interpretation
According to the survey, the above table indicates that 69(92%) of respondents are Male, 6(8%)
are Female and major software product risk finder in male only.
Table4.2: based on age showing respondents from the software company

Age Respondents Percentages
20-30 49 66%
30-40 14 18%
40-50 6 10%
50-60 6 6%
Total 75 100%
Analysis:
From the above table indicates that 66% of the respondents are aged among 20 to 30,
respondents are aged between 30 to 40 for 18%, between 40 to 50 for10 percent, between 50 to
60 for 6%.
Graph 4.2: showing respondents based on age
Respondant Age
Total
100%
50-60
6%
40-50
10%
Respondents
30-40 Percentages
18%
20-30
66%
0 10 20 30 40 50 60 70 80
Interpretation:
According to the survey, the above table indicates that 30(66%) of respondents are age 20-30,
19(26%) are 30-40 age, 14(18%) are 30-4- age, 6(10%) are 40.50 age and 6(6%) are 50-60 age
major peoples responders software products 18-20 age groups.
Table4.3: Who is facing more risk during software development?
Person Respondents Percentages

Software Developer 49 66%
Project Manager 14 18%
Systems Analyst 6 10%
Software Tester 6 6%
Total 75 100%
Analysis:
From the above table indicates that 66% of the respondents are software developer facing
more risk during development,18% project manager facing risk, Systems Analyst 10% facing
software risk and 6% software tester facing risk.
Graph 4.2: showing respondents based on person facing risk

Facing more risk during software
development
Total
Software Tester
Systems Analyst
Project Manager
Software Developer
0 10 20 30 40 50 60 70 80
Interpretation:
According to the survey, the major percentage facing risk software developer above mention the
table and graph.
Table4.4: What percentage of software projects is completed on time, within budget and
with all the required functionality?
Person Respondents Percentages

Yes 60 80%
No 15 20%
Total 75 100%
Analysis:
From the above table indicates that 80% of the respondents are saying yes, 20% saying
no, But Major concern about every project completed on time more.
Graph 4.4: What percentage of software projects is completed on time, within budget and
with all the required functionality
software projects is completed on

time, within budget and with all the
required functionality
Total
No
Yes
0 10 20 30 40 50 60 70 80
Interpretation:
According to the survey, the major percentage saying project completed on time 80% and
remaining saying no.
Table4.5: What percentage of software projects fail to meet any or all of the following three
requirements, i.e. completed on time, within budget, and with all the required
functionality?
Project Status Respondents Percentages

Completed on time 60 75%
Within Budget 10 20%
All required functionality 5 5%
Total 75 100%
Analysis:
From the above table indicates that 75% of the respondents are saying completed on time
every software products, 20% saying within budget, and all required functionality in 5%, But
Major concern about every project completed on time more.
Graph 4.5: What percentage of software projects fail to meet any or all of the following
three requirements, i.e. completed on time, within budget, and with all the required
functionality?
completed on time, within budget, and with all
the required functionality?
Total 100
%
5%
All required functionality Respondents
Within Budget 20%
Percentages
75%
Completed on time
0 10 20 30 40 50 60 70 80
Interpretation:
According to the survey, the major percentage saying project completed on time 75% and
remaining saying below 75%.
Table4.6: While developing software product, what major risk facing?
Risk Respondents Percentages

Time very less 60 75%
Insufficient Resource 10 20%
Lake of knowledge 5 5%
Total 75 100%
Analysis:
From the above table indicates that 75% of the respondents are saying time very less,
20% saying insufficient resource, and Lake of knowledge in 5%, But Major concern about every
project facing risk for time very less reason.
Graph 4.6: While developing software product, what major risk facing
While developing software product,
what major risk facing
Total
Lake of knowledge
Insufficient Resource
Time very less
0 10 20 30 40 50 60 70 80
Interpretation:
According to the survey, the major percentage saying project development time very less 75%,
insufficient resource for 20% and lake of knowledge 5%.
Table4.7: What percentage of software projects is terminated before completion?
Terminated Before Respondents Percentages

Completion
yes 60 90%
no 15 10%
Total 75 100%
Analysis:
From the above table indicates that 90% of the respondents are saying software project is
terminated before completion and 10% saying software project terminated before completion.
Graph 4.7: What percentage of software projects is terminated before completion?

Terminated Before Completion
Total
no
yes
0 10 20 30 40 50 60 70 80
Interpretation:
According to the survey, the major percentage saying project development terminated before
completion 90% and Saying no only 10%.
Table4.8: What impact does risk management have on the success of software projects in
terms of completing the project on time, within budget and within scope?
Impact of risk management Respondents Percentages

Risk management increases the 60 75%
probability of success
Risk management has no 10 20%

impact on project success
Not sure 5 5%
Total 75 100%
Analysis:
From the above table indicates that 75% of the respondents are saying Risk management increases
the probability of success, 20% saying Risk management has no impact on project success and 5% not
sure.
.
Graph 4.8: What impact does risk management have on the success of software projects in
terms of completing the project on time, within budget and within scope?
Impact of risk management

100
otal %
ot sure 5%
20 Respondents
isk management has no impact on project success % Percentages

75
isk management increases the probability of success%
0 10 20 30 40 50 60 70 80
Interpretation:
According to the survey, the major percentage saying Risk management increases the probability
of success 75%.
Table4.9: .Do formal risk management procedures typically yield better results (with
regard to completing a project on time within scope and within budget) than ad hoc
internally developed procedures?
Formal risk management Respondents Percentages

Formal methods produce 60 75%
better results than internal
methods
Formal methods do not 10 20%

necessarily produce better
results than internal methods
Not sure - I am not in the 5 5%

position to accurately compare
the two methods
Total 75 100%
Analysis:
From the above table indicates that 75% of the respondents are saying Formal methods produce
better results than internal methods, 20% saying Formal methods do not necessarily produce
better results than internal methods and 5% Not sure - I am not in the position to accurately
compare the two methods.
Graph 4.9: .Do formal risk management procedures typically yield better results (with
regard to completing a project on time within scope and within budget) than ad hoc
internally developed procedures?
Formal risk management

Respondents Percentages
100
% 75
n the position to accurately compare the two methods 5%
5
not necessarily produce better results than internal methods 20
%
10
duce better results than internal methods 75%
60
Interpretation:
According to the survey, the major percentage saying Formal methods produce better results than
internal methods 75%.
Table4.10: How to improve project performance?

Performance of Project Respondents Percentages
Project Storage 60 75%
Multiple Sharing tool 10 20%
Quality of Service 5 5%
Total 75 100%
Analysis:
From the above table indicates that 75% of the respondents are saying project storage, 20%
saying multiple sharing tools and 5% Quality of services.
Graph 4.10: How to improve project performance?
Perofrmance of project
Total
Quality of Service
Multiple Sharing tool
Project Storage
0 10 20 30 40 50 60 70 80
Interpretation:
According to the survey, the major percentage saying Project storage on cloud that why storage
improve automatically 75%.
Table4.11: What kind of risk getting from software developer?
Risk getting from software Respondents Percentages

developer
Communication risk 60 75%

Lack of knowledge 10 20%
Delay of task completion 5 5%
Total 75 100%
Analysis:
From the above table indicates that 75% of the respondents are saying communication risk, 20%
saying lack of knowledge and 5% Delay of task completion.
Graph 4.11: What kind of risk getting from software developer?
risk getting from software employee
Total
Delay of task completion
Lack of knowledge
Communication risk
0 10 20 30 40 50 60 70 80
Interpretation:
According to the survey, the major percentage saying communication risk on software developer
to interact between managers to team leader at major percentages 75%.
Table4.12: What kind of risk getting from financial stability?
Software Financial Stability Respondents Percentages

Software cost 60 75%
insufficient budget cost 10 20%
Resource of payment 5 5%
Total 75 100%
Analysis:
From the above table indicates that 75% of the respondents are saying software cost, 20% saying
insufficient budget cost and 5% Resource payment.
Graph 4.12: What kind of risk getting from financial stability?
software financial stability
Total
Resource of payment
insufficient budget cost
Software cost
0 10 20 30 40 50 60 70 80
Interpretation:
According to the survey, the major percentage saying software cost on IT Company marketing
rating for corporate worlds 75%.
Table4.13: Technical risk based on software company domain?
Technical risk Respondents Percentages

Not prepare knowledge about 60 75%
the particular domain
Less technical resource 10 20%

Others 5 5%
Total 75 100%
Analysis:
From the above table indicates that 75% of the respondents are saying Not prepare knowledge
about the particular domain, 20% saying Less technical resource and 5% others.
Graph 4.13: Technical risk based on software company domain?
Technical Risk
Total
Others
Less technical resource
Not prepare knowledge about the particular domain
0 10 20 30 40 50 60 70 80
Interpretation:
According to the survey, the major percentage saying not prepares knowledge about the particular
domain for software engineer at 75%.
Table4.14: Which one face more risk project flow or software flow?
Risk flow Respondents Percentages

Project Flow 60 75%
Software Flow 10 20%
Others 5 5%
Total 75 100%
Analysis:
From the above table indicates that 75% of the respondents are saying project flow, 20% saying
software flow and 5% others.
Graph 4.13: Which one face more risk project flow or software flow?
Compare risk project flow or software
flow
Total
Others
Software Flow
Project Flow
0 10 20 30 40 50 60 70 80
Interpretation:
According to the survey, the major percentage saying project flow more risk compare to software
flow for IT Company.
FINDINGS
1. The finding for risk management software fields under data analysis interpretation
following table clearly indicates 92% respondents are male and 8% female, out of 100%
respondents.
2. From the above table indicates that 66% of the respondents are aged among 20 to 30,
respondents are aged between 30 to 40 for 18%, between 40 to 50 for10 percent, between
50 to 60 for 6%.
3. From the above table indicates that 66% of the respondents are software developer facing
more risk during development,18% project manager facing risk, Systems Analyst 10%
facing software risk and 6% software tester facing risk.
4. From the above table indicates that 80% of the respondents are saying yes, 20% saying
no, But Major concern about every project completed on time more.
5. From the above table indicates that 75% of the respondents are saying completed on time
every software products, 20% saying within budget, and all required functionality in 5%,
But Major concern about every project completed on time more.
6. From the above table indicates that 75% of the respondents are saying time very less,
20% saying insufficient resource, and Lake of knowledge in 5%, But Major concern
about every project facing risk for time very less reason.
7. From the above table indicates that 75% of the respondents are saying Risk management
increases the probability of success , 20% saying Risk management has no impact on project
success and 5% not sure.
8. According to the survey, the major percentage saying project development terminated
before completion 90% and Saying no only 10%.
9. From the above table indicates that 75% of the respondents are saying Not prepare
knowledge about the particular domain, 20% saying Less technical resource and 5% others.
10. According to the survey, the major percentage saying software cost on IT Company
marketing rating for corporate worlds 75%.
11. According to the survey, the major percentage saying not prepares knowledge about the
particular domain for software engineer at 75%.
12. From the above table indicates that 75% of the respondents are saying project flow, 20%
saying software flow and 5% others.
13. From the above table indicates that 75% of the respondents are saying project storage,
20% saying multiple sharing tools and 5% Quality of services.

14. From the above table indicates that 75% of the respondents are saying software cost, 20%
saying insufficient budget cost and 5% Resource payment.
LEARNING OUTCOME:
I learned brisk technologies risk management based on software product and software
application.
Brisk technologies, how they handling project and how they managing risk factor in
on time.
Learned various technical risk management under brisk technologies pvt ltd.
Following keys:
Software company risk management.

Project schedule
Type of risk management under IT sectors.
LEARNING OUTCOME CONTENTS

Learn outcome Level 1 Introduction, industry profile, organization
profile, promoters, vision, mission ,quality
polices, service profile territory task,
framework offices, contenders information,
SWOT examination, future development and
prospects and money related proclamation
Learn outcome Level 2
Conceptual background: Theoretical
background of the study and Literature
Survey
Statement of the problem, need of the study
,objective ,scope of the study, Research
methodology, Hypothesis and Chapter
Scheme
Analysis and interpretation: Data collected
from the relevant source table and graphs.
Learn outcome Level 5 Finding, Suggestion/Recommendations and
conclusion.
Bibliography and Annexure Figures ,Graphs ,Photograph etc.
CHAPTER-4
CONCLUSIONS AND RECOMMENDATIONS
CONCLUSIONS
The following conclusions can be made with respect to the research questions.
• The success rate (completing the project on time, within budget, and within scope) of software
projects in Brisk Techno in India is low, as it is in the rest of the world. The need to investigate
the impact of risk management on project success rates can thus be substantiated.
• The application of risk management processes or procedures increases the chances of

successfully executing software projects in India.
• The risks that face software projects are generally the same in India as in the developed world.
• Most Indian software Brisk Techno use ad hoc internally developed risk management
procedures. These procedures mostly do not conform to the IEEE standard for software project
risk management. The adequacy of these procedures is thus questionable. Having stated that, the
success rate of Indian software projects was higher where ad hoc risk management was applied,
compared with projects where no risk management was applied.
• The fact that the majority of software risk management methods that were applied to Indian
software projects were ad hoc internally developed methods, rather than recognized formal
methods, means that the effectiveness of formal risk management procedures could not be
accurately measured. The results of formal methods could thus not be compared with the results
of ad hoc methods.
No formal procedure was applied to a sufficient number of projects (within the test sample) to
measure its results properly. It was thus not possible to state that one procedure is more effective
than others.
This study investigated the application of the IEEE Standard 1540 for risk management within
software development projects in India. This standard is fairly generic, and the steps are similar
to many other risk management processes in use today. The results indicate that formal processes
are not always used by Brisk Techno. The information engineering (IE) approach was developed
to assist Brisk Techno to execute software development projects successfully, and to do this on
time and within budget. Application of a risk management process should form part of IE; and
the results of this study indicate that there is a definite need for a more formal approach to
delivering software projects in India more successfully. The IE methodology is therefore not
applied in most software projects in India, and probably contributes to the low success rate.
RECOMMENDATION
It is recommended that India software Brisk Techno implement some form of risk management
in all of their software projects, since the application of risk management has a positive impact
on project success. Given that software project risks were found to be the same in India as in the
developed world, local software Brisk Techno are very likely to encounter a number of the risks
that were identified as being especially prevalent in the developed world (such as Boehm’s top
10 software project risks). It is therefore recommended that India software Brisk Techno take the
necessary steps appropriately to mitigate these risks that are common to most software projects
for Brisk Technologies in Bangalore.
FUTURE RESEARCH
There is still a gap in research into the effectiveness of formal software risk management
procedures in India. The fact that risks are the same in India as in the developed world suggests
that mitigation strategies that have proven to be successful in the developed world will also be
successful in India. This statement, however, cannot be empirically proven at this point. So there
is still a need to find Brisk Techno that implement formal software risk management procedures,
and to measure the effectiveness of these procedures.
REFERENCES
[1] The Standish Group. 2009. Standish chaos report. www.projectsmart.co.uk/docs/

chaosreport.pdf [Accessed on November 11, 2010].
[2] Fairley, R. 1994. Risk management for software projects, IEEE Software 11 (3) pp. 59-67.
[3] Hogan, P.T & Raja, M.K. 1997. Information engineering implementation in organizations: A
study of factors affecting success. Journal of Information Technology Management 8 (3,4).
[4] Misra, S.C., Kumar, V. & Kumar, U. 2006. Different techniques for risk management in
software engineering: A review. Eric Sprott School of Business, Carleton University, ASAC,
Banff, Alberta.
[5] Boehm, B.W. 1991. Software risk management: Principles and practices, IEEE Software 8
(1), pp. 32-41.
[6] Esteves, J., Pastor, J., Rodriguez, N. & Roy, R. 2004. Implementing and improving the SEI
risk management method in a university software project. IEEE Latin American Transactions, 3,
(1), pp. 90-97.
[7] Kontio, J. 1997. The Riskit method for software risk management, version 1.00, UMIACS-
TR-97- 38, Institute for Advanced Computer Studies and Department of Computer Science
Technical Report, University of Maryland.
[8] Kontio J. 2001. Software engineering risk management: A method, improvement framework
and empirical evaluation. Doctoral dissertation, Helsinki University of Technology, Center of
Excellence, ISBN 952-5136-22-1.
[9] Keshlaf, A.A. & Hashim, K. 2000. A model and prototype tool to manage software risks,
IEEE Quality Software, 1,(1), pp. 297-305.

A Study On Risk Management in Brisk Technologies at Bangalore Interim

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

A Study On Risk Management in Brisk Technologies at Bangalore Interim

Загружено:

Авторское право:

Доступные форматы

A STUDY ON RISK MANAGEMENT IN BRISK

2. Avoiding rework caused by erroneous, missing, or ambiguous requirements, design or code,

1.1 PROBLEM STATEMENT

1.2 NEED FOR THE STUDY

Risk management includes the following tasks:

Identify risks and their triggers

Identify and Classify Risks

1.3 OBJECTIVES OF THE STUDY

• To study the project performance of the Brisk Technologies.

1.4 SCOPE OF THE STUDY

· Avoiding risks may also mean avoiding opportunities

1.5 INDUSTRAL PROFILE

Brisk Technologies is an IT services, business solutions and outsourcing organization that

FUTURE PROSPECTUS OF IT INDUSTRY

New, unproven technologies

Risk Management Plan

Monitor and Mitigate

Publish project status reports and include risk management issues

Mitigating options include:

RISK ASSESSMENT MATRIX FOR ENTERPRISE BUSINESS OWNERS

RISK ASSESSMENT MATRIX FOR SMALL BUSINESS OWNERS

1.6 COMPANY PROFILE

The Group operates in Eight Segments:

•IT Enabled Services • Professional Training & Placement

•Infra & Maintenance • College Training

•Telecom Enabled Services • PDP

JOB FAIR EVENT

CLIENT & PARTNER

10 Eclipse Systems Pvt. Ltd. Noida 30 Reliance Communication

Address: A - 3rd Floor, 92/1 Metro Arcade Complex,

Project & Business Head Bangalore Mr. PUSHPENDRA SINGH

For Any Query Contact Shivendra Singh

Email Id shivendra@Brisk Techno.com

SMS “BT” @ 5607008

2.1 RESEARCH AND METHODOLOGY

SOURCES OF THE STUDY:

This is the study entirely based on:

The questionnaire will prepare through direct contact with respondents.

DATA ANALYSIS AND INTERPRETATION

TABLE 4.1: Based on respondent gender

Gender Respondents Percentage

Table4.2: based on age showing respondents from the software company

Graph 4.2: showing respondents based on age

Table4.3: Who is facing more risk during software development?

Person Respondents Percentages

Graph 4.2: showing respondents based on person facing risk

Person Respondents Percentages

software projects is completed on

Project Status Respondents Percentages

Table4.6: While developing software product, what major risk facing?

Risk Respondents Percentages

Time very less

Terminated Before Respondents Percentages

Graph 4.7: What percentage of software projects is terminated before completion?

Impact of risk management Respondents Percentages

Risk management has no 10 20%

Impact of risk management

isk management has no impact on project success % Percentages

isk management increases the probability of success%

Formal risk management Respondents Percentages

Formal methods do not 10 20%

Not sure - I am not in the 5 5%

Formal risk management