Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.
Is it reasonable to insist on reproducing every defect before diagnosing and fixing it?
I work for a software product company. We have large enterprise customers who implement our product and we provide support to them. For example, if there is a defect, we provide patches, etc. In other words, It is a fairly typical setup.
Handling internal IT issues
In the company I work at, developers also serve as internal tech support. This means we have to do three types of things:
Handling internal IT issues
In the company I work at, developers also serve as internal tech support. This means we have to do three types of things:
Handling internal IT issues
In the company I work at, developers also serve as internal tech support. This means we have to do three types of things:
How can Scrum be adapted to allow for support obligations?
Scrum’s great for new development and proactive tasks. But I’ve never been sure how to use it when the department’s obligations also include analyzing/answering/fixing customer support questions, which come in unpredictably, typically have high enough priority to interrupt what we planned on doing, and whose complexity ranges from trivial to major.
How to make sure that reported issues are not caused by wrong credentials or typos of the client? [duplicate]
This question already has answers here: Getting users to write decent and useful bug reports (6 answers) Closed 10 years ago. I have found myself a few times in the situation where a client reports an issue like ‘I can no longer login to my account‘. Sure enough when trying to login with the client’s […]
How to make sure that reported issues are not caused by wrong credentials or typos of the client? [duplicate]
This question already has answers here: Getting users to write decent and useful bug reports (6 answers) Closed 10 years ago. I have found myself a few times in the situation where a client reports an issue like ‘I can no longer login to my account‘. Sure enough when trying to login with the client’s […]
How to make sure that reported issues are not caused by wrong credentials or typos of the client? [duplicate]
This question already has answers here: Getting users to write decent and useful bug reports (6 answers) Closed 10 years ago. I have found myself a few times in the situation where a client reports an issue like ‘I can no longer login to my account‘. Sure enough when trying to login with the client’s […]