What makes software development project UNsuccessful

1
What makes software development project
UNsuccessful
Ivanna Kyryk QATestLab Program Manager
2
About me
5-year experience in management
experience in testing, marketing, sales, business
development
15 active projects
team of more than 20 members
Like to travel and fond of learning something new
QATestLab. All rights reserved.
3
Quality is critical for software
In terms of current market conditions, a fast
delivery of software that satisfies the end
users needs is a guarantee for business
development.
QATestLab. All rights reserved.
4
Focus on software development
Applying to a software development company, a
customer expects a high-quality product ready for
end users. But focusing on coding, software
development companies run a risk to estimate the
scope of testing, its lifecycle, and required
means peripherally that results in a buggy
software.
QATestLab. All rights reserved.
5
Role of testing in software development companies
A bug-free code as well as exhaustive testing is
a challenging task to fulfill. In order to
accomplish a project on time, software
development companies shortcut activities and
often these are the testing ones.
QATestLab. All rights reserved.
6
Risks of testing by software vendor

• Omitting of testing stage
• Wrong estimates of testing
• Limited test coverage because of tight timeframes
• Biased testing by internal QA team
• No or lack of acceptance testing before a release
• No software support

QATestLab. All rights reserved.
7
Omitting of testing stage
Providing not full software development
lifecycle, software vendors can omit a testing
stage because of lack of infrastructure,
competence, and time resources.
QATestLab. All rights reserved.
8
Wrong estimates of testing
Focusing on coding to provide a bug-free code,
software vendors run a risk of preparing wrong
estimates of the required testing scope,
infrastructure, and timeframes, thus, releasing a
software of lower quality, than planned or
required.
QATestLab. All rights reserved.
9
Limited test coverage
Striving to fulfill a project on time, software
vendors are ready to shortcut testing activities,
thuswise, they provide a buggy code within
defined timeframes.
QATestLab. All rights reserved.
10
Biased testing by internal QA team
As an internal QA team is aware of the specifics
of development procedure, this affects on
providing an objective and unbiased quality
evaluation. Constantly working with one and the
same software, the team runs a risk to get
accustomed to its specific features and starts to
omit bugs.
QATestLab. All rights reserved.
11
Omitting of acceptance testing
To ensure a successful release of a ready
software, acceptance testing is required. Basing
on defined acceptance criteria, it shows to make
sure the product meets all defined objectives.
Acceptance testing is called to decrease the
chance and severity of new issues and
regressions. On the basis of test results, a
customer is able to make a final decision on
software release.
QATestLab. All rights reserved.
12
No software support
Despite being well-written, the ready code may
malfunction after its implementation or because
of integration with third-party software. In
some cases, software vendor services do not
include post-release bug fixing, and a customer
faces additional spendings to resolve the newly
detected issues.
QATestLab. All rights reserved.
13
Independent testing helps to ensure a high
quality of developed software and minimize the
risks of bug detection by end users after its
release. Testing makes assurance double sure.
QATestLab. All rights reserved.
14
Contacts
E-mail contact_at_qa-testlab.com
Twitter QATestLab
Phone [phone] Address 154a,
Borschagivska str., 03056, Kiev, Ukraine
Web-site qatestlab.com
SkypeID sales.qatestlab
QATestLab. All rights reserved.
15
Thanks