• 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!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "Things you don't want to hear from a CIO"

Collapse

  • Mich the Tester
    replied
    Originally posted by Sysman View Post
    TPS means either Transactions Per Second or Totally Pointless Stuff to me.

    What do you understand by it?
    Second guess was right;

    TPS report - Wikipedia, the free encyclopedia

    Leave a comment:


  • Sysman
    replied
    Originally posted by amcdonald View Post
    So what's the difference between a management summary and a TPS report ?
    TPS means either Transactions Per Second or Totally Pointless Stuff to me.

    What do you understand by it?
    Last edited by Sysman; 12 May 2011, 11:33.

    Leave a comment:


  • Mich the Tester
    replied
    Originally posted by amcdonald View Post
    So what's the difference between a management summary and a TPS report ?
    Originally posted by DaveB View Post
    The cover sheet.
    Oh, oh, wait there my dear fellow!

    You're forgetting the template, the version history, the distribution list, the template version history, the headers, the footnotes, the index, the appendix, the addendum and the obfuscation clauses. That's at least 30 hours of invoicing!

    Leave a comment:


  • DaveB
    replied
    Originally posted by amcdonald View Post
    So what's the difference between a management summary and a TPS report ?
    The cover sheet.

    Leave a comment:


  • amcdonald
    replied
    Originally posted by Sysman View Post
    A management summary should be no more than one page and easy to locate.
    So what's the difference between a management summary and a TPS report ?

    Leave a comment:


  • DimPrawn
    replied
    Things you don't want to hear from a CIO
    The Indian team arrive Monday, please clear your desk by the end of the day. If you could help them settle in and perhaps carry their new computers, that would be great.

    Leave a comment:


  • DaveB
    replied
    Originally posted by alreadypacked View Post
    It was a user guide, the CIO wanted to use it.
    In which case he is a Knob. A pointy haired Knob at that. Maybe give him an Etch-A-Sketch instead?

    Leave a comment:


  • alreadypacked
    replied
    Originally posted by thunderlizard View Post
    Then it was at the wrong level of detail. Screen shots are for a user guide, not a CIO overview.
    It was a user guide, the CIO wanted to use it.

    Leave a comment:


  • Sysman
    replied
    Originally posted by DaveB View Post
    From RFC 2795



    UNless they tell you otherwise CIO's typically want a management summary, preferable less than one page, that tells them the fundamental facts. We will do this. We will use this. It will cost us this. The outcome will be this. The business benefit will be this.

    Anything more than that and they tend to lose interest.
    A management summary should be no more than one page and easy to locate. It should be on a page of its own so that it can be photocopied without any extraneous info. I like to stuff them immediately after the TOC so that:
    1. management only has to read the first couple of lines of the TOC far to find out where it is
    2. management doesn't have to turn many pages to get there


    Got to make it as easy as possible for them to pass it up to the board reasonably intact. and hopefully without any wild promises added.

    Leave a comment:


  • DimPrawn
    replied
    I was once drawn into a battle between IT and a senior manager.

    Manager claimed software was defective.

    I pointed out it was all in the spec.

    He said, "I never read the spec it was too complicated".

    I said "You signed it off".

    He said "I had to, otherwise I would never have got the system".


    The project got worse from that point.

    Leave a comment:


  • Moose423956
    replied
    Originally posted by alreadypacked View Post
    I wrote the document in an idiots guide style, with more screen shots than a comic, FFS
    Did you tell him/her that?

    Leave a comment:


  • DaveB
    replied
    Originally posted by alreadypacked View Post
    CIO "I just want to ask X"

    X is covered in the document.

    CIO "I stopped reading the document as it was too complicated."

    I wrote the document in an idiots guide style, with more screen shots than a comic, FFS
    From RFC 2795

    A diagram of IMPS concepts is provided below. Non-technical readers
    such as mid-level managers, marketing personnel, and liberal arts
    majors are encouraged to skip the next two sections. The rest of
    this document assumes that senior management has already stopped
    reading.
    UNless they tell you otherwise CIO's typically want a management summary, preferable less than one page, that tells them the fundamental facts. We will do this. We will use this. It will cost us this. The outcome will be this. The business benefit will be this.

    Anything more than that and they tend to lose interest.
    Last edited by DaveB; 12 May 2011, 09:50.

    Leave a comment:


  • thunderlizard
    replied
    Then it was at the wrong level of detail. Screen shots are for a user guide, not a CIO overview.

    Leave a comment:


  • alreadypacked
    started a topic Things you don't want to hear from a CIO

    Things you don't want to hear from a CIO

    CIO "I just want to ask X"

    X is covered in the document.

    CIO "I stopped reading the document as it was too complicated."

    I wrote the document in an idiots guide style, with more screen shots than a comic, FFS

Working...
X