Discussion Locked

Business Stakeholder Needs Advice - Mission-critical app not reliable

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am the main business stakeholder for an email delivery system built in-house. (We are an agency and this web-based application is one of our top software tools, used globally.) The development went smoothly and since launching 6 weeks ago, the users are generally happy. However... I would rate software reliability as a 6 out of 10. About 5-7 bugs are reported per week that cause a user's email campaign to come to a halt -- we lose data on that campaign, and the user has to spend days recovering the error and even explaining to our clients why something has gone wrong.

We've had several conversations with the development team about this; they have put in several solutions such as monitoring alerts. The challenge is, we are a small company so the dev team is stretched. There is no documentation on the system and the main developer on it is only several months old in the company so doesn't understand our business, and is less experienced than the other developers (who have been around for years). I bring up the point on experience because everytime we report a problem, a senior developer takes 2 seconds to figure out the problem. But by that time, it's too late -- the users have lost a lot of time and their confidence in the software's reliability is getting chipped away.

I would appreciate any advice on how to bring up our software's reliability. Thanks.

2 replies

by jamesrl

Its been part of my training that there should be a warranty period for new apps - 30/60/90 days after the implementation when the developers are not fully committed to new projects, and when issues are "fast tracked" to speedy resolution.

You need to talk to the development management about the impact of your issue so that they can shake loose some resources to fix the stability issues. If you look at the issues one by one, they might seem like growing pains - if you can show the negative impact cummulatively it should give them your perspective.

James

by larry2005

Stakeholder,

I have had some experience as PM on web
development projects. A couple of questions
and thoughts come to mind.
1. USER TEST TIME. Did the application have
any user testing time ? If so, did any of these
bugs appear at that time? From this article, it
appears that the most common bug is that of
loosing data; are there other major bugs that
appear? If the IT group is not keeping a bug
list you might start keeping a bug list to
quantify the bugs, resolution and date,
comments, etc.
2. DATA FLOW. Is all data entered through
the same interface; do customers enter data
through a common interface on the web, or
are there other methods/processes to enter
data to the databases where you are capturing
data?
3. INTERIM - REPAIR OF DATA. When the
data is lost, does it all the data reside on the
database, and only has to be extracted
manually, or does the data not exist at all and
needs to created from scratch? During
testing, did the database and application
undergo any load testing?
4. MONITORING ALERT STATUS. Have the
monitoring alerts provided any diagnosis of
the problem - to date? If not, what else is the
IT group suggesting to diagnose the major
bugs?
5. DBA INVOLVEMENT. This is a question,
after the fact, but was a DBA involved in the
project, and were they able to analyze the data
flow through the database and tables, and
were they able to diagram the database? Did
the development team develop data integrity
methods within the application or database to
verify data collected is being entered in a valid
format? Are they able to determine that the
data is not being truncated as it passes from
start (data entered) to end point (report).
6. DOCUMENTATION. Lack of documentation
is a challenge the operations group will have
to work with. Recommend you insist on
documentation and approvals for software
deliverables completion of your projects.
7. BUSINESS CASE FOR UPGRADE.
Business or organizational suggestions.
Present a case to your management that will
justify money to resolve this business issue.
You may need to demonstrate one or a
number of points to your management. How
the credibility of your product tool is at stake,
and explains that the tool is working
inadequately to your clients needs and
expectations. Is there any potential of
business loss (sales or other reason) due to
not repairing the application? You will need to
get a FIRM description and explanation of the
resolution for these "bugs", and estimate of
work prior to making a major correction to the
application or database. You can also provide
quantitative data as to time spent on the
project for corrections or when the system
goes down, if significant (customers impact
to their business (?), your time and
development time).

Regards. Larry

This discussion is closed to new replies.