Skip to main content
Added an update after talking to management
Source Link
DRVR
  • 131
  • 5

I work as a software developer for a consulting company in Australia. In the past, we provided support services to a particular client for a specific piece of software. This support contract ended nearly a year ago, and that customer's software is now supported by another vendor.

However, at the time the contract ended, we had another non-BAU related work order in place to redevelop the software to update a specific function. We spent some hours at the initial phase to develop a statement of work, and provide some initial analysis, solutioning, etc. However, due to major delays on the customer side, the actual development could not be started or completed by the time our over-arching contract ended, so it didn't proceed any further.

Today however, I've just received an email from the client, asking us to begin preparations to finally deliver this redevelopment project, almost a year after we finished up our contract (presumably because they managed to resolve their other problems). Normally I would have no issues with this, but the software in question is now being supported by another vendor, who are possibly making their own alterations, etc. I have no idea if the application even resembles the same application as it was at the time the work order was initially drafted up.

My question is - how should I go about discussing my concerns with my own management team, or am I fussing about nothing and I just go along with it? I'm particularly worried about who is on the hook for post-implementation support/issues after deployment, since we won't have a BAU contract. How will issue be triaged, and who can be blamed (for example) if other parts of the application are failing, etc.

Update: I've been advised by management that this work will proceed as initially planned a year ago...

I work as a software developer for a consulting company in Australia. In the past, we provided support services to a particular client for a specific piece of software. This support contract ended nearly a year ago, and that customer's software is now supported by another vendor.

However, at the time the contract ended, we had another non-BAU related work order in place to redevelop the software to update a specific function. We spent some hours at the initial phase to develop a statement of work, and provide some initial analysis, solutioning, etc. However, due to major delays on the customer side, the actual development could not be started or completed by the time our over-arching contract ended, so it didn't proceed any further.

Today however, I've just received an email from the client, asking us to begin preparations to finally deliver this redevelopment project, almost a year after we finished up our contract (presumably because they managed to resolve their other problems). Normally I would have no issues with this, but the software in question is now being supported by another vendor, who are possibly making their own alterations, etc. I have no idea if the application even resembles the same application as it was at the time the work order was initially drafted up.

My question is - how should I go about discussing my concerns with my own management team, or am I fussing about nothing and I just go along with it? I'm particularly worried about who is on the hook for post-implementation support/issues after deployment, since we won't have a BAU contract. How will issue be triaged, and who can be blamed (for example) if other parts of the application are failing, etc.

I work as a software developer for a consulting company in Australia. In the past, we provided support services to a particular client for a specific piece of software. This support contract ended nearly a year ago, and that customer's software is now supported by another vendor.

However, at the time the contract ended, we had another non-BAU related work order in place to redevelop the software to update a specific function. We spent some hours at the initial phase to develop a statement of work, and provide some initial analysis, solutioning, etc. However, due to major delays on the customer side, the actual development could not be started or completed by the time our over-arching contract ended, so it didn't proceed any further.

Today however, I've just received an email from the client, asking us to begin preparations to finally deliver this redevelopment project, almost a year after we finished up our contract (presumably because they managed to resolve their other problems). Normally I would have no issues with this, but the software in question is now being supported by another vendor, who are possibly making their own alterations, etc. I have no idea if the application even resembles the same application as it was at the time the work order was initially drafted up.

My question is - how should I go about discussing my concerns with my own management team, or am I fussing about nothing and I just go along with it? I'm particularly worried about who is on the hook for post-implementation support/issues after deployment, since we won't have a BAU contract. How will issue be triaged, and who can be blamed (for example) if other parts of the application are failing, etc.

Update: I've been advised by management that this work will proceed as initially planned a year ago...

Source Link
DRVR
  • 131
  • 5

Is it normal, as a vendor, to perform software development on a customer application that a different vendor develops and supports?

I work as a software developer for a consulting company in Australia. In the past, we provided support services to a particular client for a specific piece of software. This support contract ended nearly a year ago, and that customer's software is now supported by another vendor.

However, at the time the contract ended, we had another non-BAU related work order in place to redevelop the software to update a specific function. We spent some hours at the initial phase to develop a statement of work, and provide some initial analysis, solutioning, etc. However, due to major delays on the customer side, the actual development could not be started or completed by the time our over-arching contract ended, so it didn't proceed any further.

Today however, I've just received an email from the client, asking us to begin preparations to finally deliver this redevelopment project, almost a year after we finished up our contract (presumably because they managed to resolve their other problems). Normally I would have no issues with this, but the software in question is now being supported by another vendor, who are possibly making their own alterations, etc. I have no idea if the application even resembles the same application as it was at the time the work order was initially drafted up.

My question is - how should I go about discussing my concerns with my own management team, or am I fussing about nothing and I just go along with it? I'm particularly worried about who is on the hook for post-implementation support/issues after deployment, since we won't have a BAU contract. How will issue be triaged, and who can be blamed (for example) if other parts of the application are failing, etc.