• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Have you ever worked on a project with any decent documentation?

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    #21
    Most documentation tends to suffer the same problem as most of the code it's written about, i.e. over complicated, verbose and full of unnecessary crap.

    There's also the problem that some developers (and managers who used to be developers) have the opinion that any time spent not coding is time wasted

    Then there are also companies with ridiculous documentation templates which need to be followed at all times and bloat what could be a 1 page diagram with a bit of text to 10 pages with an abstract, introduction, intended audience, distribution lists, contents page etc...

    There are some good wiki systems which can be used on the corporate system which are a much better idea than hundreds of word documents. The beauty of the wiki pages is that high level docs can easily link to lower level technical explanations meaning that a reader only needs to dig as deep as they need to.
    Coffee's for closers

    Comment


      #22
      Originally posted by Spacecadet View Post
      Most documentation tends to suffer the same problem as most of the code it's written about, i.e. over complicated, verbose and full of unnecessary crap.

      There's also the problem that some developers (and managers who used to be developers) have the opinion that any time spent not coding is time wasted

      Then there are also companies with ridiculous documentation templates which need to be followed at all times and bloat what could be a 1 page diagram with a bit of text to 10 pages with an abstract, introduction, intended audience, distribution lists, contents page etc...

      There are some good wiki systems which can be used on the corporate system which are a much better idea than hundreds of word documents. The beauty of the wiki pages is that high level docs can easily link to lower level technical explanations meaning that a reader only needs to dig as deep as they need to.
      Right. Totally agree.

      Given that there are standards for Project Management, Coding, Design Patterns, Testing, Data modelling etc etc is there a standard for producing quality documentation?
      Knock first as I might be balancing my chakras.

      Comment


        #23
        Originally posted by suityou01 View Post
        Right. Totally agree.

        Given that there are standards for Project Management, Coding, Design Patterns, Testing, Data modelling etc etc is there a standard for producing quality documentation?
        A conversation we had earlier in the year.
        What happens in General, stays in General.
        You know what they say about assumptions!

        Comment


          #24
          Originally posted by suityou01 View Post
          Right. Totally agree.

          Given that there are standards for Project Management, Coding, Design Patterns, Testing, Data modelling etc etc is there a standard for producing quality documentation?
          Standards; practices and approaches that somebody says worked for them, got a few people together and wrote a book about them and set up a club called the 'International Organisation for Standardisation of ...'. In other words, tosh. Use your brain, agree an approach with colleagues and do what you believe will work.
          And what exactly is wrong with an "ad hominem" argument? Dodgy Agent, 16-5-2014

          Comment


            #25
            Originally posted by MarillionFan View Post
            A conversation we had earlier in the year.
            Indeed. Did you get anywhere with it?

            I have my own tried and tested standards for documentation which I have often been praised for.

            Please don't own up to our off line conversations btw, it rather lets the side down on our on board rivalry.
            Knock first as I might be balancing my chakras.

            Comment


              #26
              one of the key things is ensuring that whatever document hoops you need to jump through you ensure that the documentation is easy to read and fit for purpose...

              too much an no body reads it too little and it is of no use.

              but ultimately my experience has found that it is knowledge in people's heads which is the biggest help - as often documentation is not clear enough or does not contain enough context to be of value

              on another /similar note

              is it a benefit if the BA and the PM have knowlegde of the system that are being developed.

              My expereince is that if they do not the requirements for example have no real context and are of little value when trying to actually drive out development needs.

              Comment


                #27
                Originally posted by suityou01 View Post
                Indeed. Did you get anywhere with it?

                I have my own tried and tested standards for documentation which I have often been praised for.

                Please don't own up to our off line conversations btw, it rather lets the side down on our on board rivalry.
                Bedwetter.
                What happens in General, stays in General.
                You know what they say about assumptions!

                Comment

                Working...
                X