3 ms·
Today, with "agile" being popular, that specification almost certainly is implicit, and it _was_ in the heads of both parties when they were writing the systems
by Someone 12y ago
Today, with "agile" being popular, that specification almost certainly is implicit, and it _was_ in the heads of both parties when they were writing the systems (but probably not completely; if both parties fully understood the protocol, chances are there would be little reason to look into it).
Also, the heads the specification _was_ in may have left the company.
But I agree that "closed source" most of the time is only a small part of the problem. Having the source of your shell script that talks to my perl script helps, but only a bit.
- SideburnsOfDoom 12y agoAs someone who has worked in various agile ways, I can assure you that agile certainly does not mean "do not provide your users with explicit specification of a public api". In the Agile manifesto (1), the phrase "we value ... Working software over comprehensive documentation" refers to the big upfront waterfall design and architecture documents that precede implementation and are usually obsolete before the software is working. If you are working in an agile way and you find that your system's behaviour is under-specified to people trying to use it, then you have a problem, and agile methods encourage you to change your ways of working to fix the problem. For instance, by providing sufficient specification with each piece of working software. See: Definition of Done (2) You could however just be using "agile" to mean something else such as "lazy", "sloppy", "hasty" or "inexperienced". 1) http://agilemanifesto.org/ http://agilemanifesto.org/ 2) http://guide.agilealliance.org/guide/definition-of-done.html http://guide.agilealliance.org/guide/definition-of-done.html