In my company it is the job of someone in business technology to manage production applications. Personally I think that this is a job for a Project Manager, not a developer, as it is about management and is not particularly technical. You do not actually have to carry out any of the work on the application, just:
- Manage the relationship with the vendor
- Manage the infrastructure teams to keep the application running
- Manage all issues and problems with the application
- Manage any updates to the application
- Manage all access to the production system
- Manage any documentation for the system and its operation
- Manage SOX audits on applications that require it
This is no small task and incorporates only part of my job. When everything is well, there is little to do, but as usual everything happens at once.
I currently own:
- Our general ledger application (soon to be decommissioned)
- All of our Mortgage Souring systems (around six applications)
- Visual Studio Team System (includes Team Explorer, Web Access to Team System, Office Integration, )
- a CRM that I built
- and a few others
I am performing a SOX audit on our general ledger application and all of our Mortgage Sourcing application have stopped working due mainly to the way they are built being incompatible with our infrastructure.
Fixing these problems, or managing the solutions is slow and painfully. At least my company has just implemented a SOX audit management system that is taking the audit from two months last year to only a few weeks this year.
What to read next
Software Development Industrial Revolution
Explores how industrialising software development with tools like Team Foundation Server boosts speed, collaboration, and scalability in …
Deploying Team Server
Discusses the challenges, costs, and benefits of implementing Team Foundation Server (TFS) for large development teams in a corporate …
Deployment documentation
Outlines steps to document and improve deployment for a complex business app, focusing on automation, rollback, vendor updates, and …
Technical Debt Management for Long-Term Quality
Explains how managing and repaying technical debt improves software quality, delivery speed, and long-term value by addressing both known …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …