Why is it that vendors insist on developers staying up all night to write installation documentation for a 40 component on 19 server installation? Do they not realize that this is not the best way to have your documentation produced? What about the image that it presents to the customer, or the impact of someone actually following said documentation!
That has been one of my tasks over the last week. I stalling a complex enterprise solution from documentation written at four in the morning by a very tired developer. Needless to say it has been difficult and my copy of the documentation is now full of notes to take back to the vendor. Notes like “What is this?” or “Which config files are you referring to?” and “In the config file I can find, what ’exactly’ do I need to change?”
It does not help that the application is not complete…
We are trying to follow cryptic documentation for an application that is not complete to install two instances with four environments per instance and twenty servers per instance and as many as twenty-five applications per server!
Hmm… Fun.
Technorati Tags: Fail
What to read next
Deployment documentation
Outlines steps to document and improve deployment for a complex business app, focusing on automation, rollback, vendor updates, and …
Navigating My Most Memorable Challenge as an Agile Consultant: Lessons in Readiness and Engagement
A personal account highlighting the importance of organisational readiness, engagement, and listening for successful agile consulting and …
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 …