Thursday, April 23, 2009

Work gripes: translating requirements and compliance into contractual clauses

Darn it, if I'm supposed to be writing legal contracts, my bosses should have sent me to Law school.

As PM, I did all that's needed to produce business requirements, technical requirements, delivery schedules, acceptance requirements, project management requirements, information security requirements etc.

But now it seemed I am also in charge of converting them into contractual terms that can be legally interpreted, and if not, they'd have to be dropped.

^#!@$%^&#$$^*&^^$%Y&@$%#%#^$@%^$%^$%!!!!!!

10 comments:

  1. Try google, may be able to get some references there..

    ReplyDelete
  2. How did previous PMs do it? Maybe time for a little pantry-chat.

    ReplyDelete
  3. Extra work load, it's common as company try ways to cut budget.

    ReplyDelete
  4. Most projects are single-contracts ... but for this round, it's 2 vendors and 2 contracts for a single project.

    Usually, contracts are handled by a member from Procurement, but there's a lot of "first time" for this, so we're really pioneering into new fields, stretching the boundaries of previously established parameters, Infosec standards, "breaking rules" because it's virgin territory and urgency, even disrupting the normal order of the "gateways".

    *sigh* when it's over, more likely it's the other PMs who'll asking for a chat if the company's going into more multi-tenanted SaaS vendors.

    ReplyDelete
  5. Snowy, I have given up trying to understand the newfangled lingo of the younger generation. ^_^

    ReplyDelete
  6. During a meeting last Thursday, one manager said in jest, "Does that mean I'll have to get Min (a new staff) to work 16 hour day instead of 14 hour?"

    I told him, "Matt, Min is Gen-Y, they don't do 14 hours, much less 16."

    Min just smiled sheepishly.

    ReplyDelete