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

Poisoned chalice project

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

    #51
    Originally posted by alreadypacked View Post
    ....Always tell them there are 3 main things in projects, Quality, Cheap and Speed. Pick two.

    Comment


      #52
      SY,

      I've never worked on any project that ticked all the right boxes and ran completely smoothly - at least not under the surface.
      There are all sorts of issues & risks that crop up. Your job is to use what experience you have to anticipate them, any political sense to manage and mitigate them, your guile (and a bit of elbow-grease) to document them and close any gaps you can, while driving the damn thing forward & covering your arse at the same time. You've got to be more pragmatic and less idealistic. It's admirable that you have a heart for the best quality product outcome but balance this with the inevitable compromises of a typical megacorp environment and all the bullshit: that entails.

      Managed well, this could prove to be a long-term moneyspinner. I'd keep invoicing and practice those product stakeholder management skills.

      Comment


        #53
        Man up and show some passive aggression.

        Helpfully raise risks detailing what might happen, why, and what impact etc. (i.e. raise risks), and escalate them appropriately. You've then made sure that someone else is responsible - you have alerted the client to what may go wrong and they have chosen to go ahead anyway. You have then done your level best to deliver anyway, but unfortunately it went wrong, just as you predicted. This is what I live for.

        Comment


          #54
          Originally posted by Old Greg View Post
          Man up and show some passive aggression.

          Helpfully raise risks detailing what might happen, why, and what impact etc. (i.e. raise risks), and escalate them appropriately. You've then made sure that someone else is responsible - you have alerted the client to what may go wrong and they have chosen to go ahead anyway. You have then done your level best to deliver anyway, but unfortunately it went wrong, just as you predicted. This is what I live for.
          "You must spread some reputation around before giving it to old greg again"

          well this is it for me, spot on - and exactly what i meant by the impossible situations being manageable
          sufficiently advanced stupidity is indistinguishable from malice - Asimov (sort of)

          there is no art in a factory, not even in an art factory - Mixerman

          everyone is stupid some of the time - trad.

          Comment


            #55
            Originally posted by 2BIT View Post
            "You must spread some reputation around before giving it to old greg again"

            well this is it for me, spot on - and exactly what i meant by the impossible situations being manageable
            I'm considering writing a book on passive aggressive project management.

            Comment


              #56
              Originally posted by Old Greg View Post
              I'm considering writing a book on passive aggressive project management.
              In your case, you don't need to include the PM bit.
              What happens in General, stays in General.
              You know what they say about assumptions!

              Comment


                #57
                An update :

                I ran the meeting today and was clear about progress, lack of attendance, lack of interest. I am documenting all that I am short of and need to progress and escalating to the PM for his risk log. I am also presenting attendance records from the workshops.

                Every time someone tried to hijack the meeting or digress I quickly but politely snatched it back.

                I have also informed the PM there are two options, deliver a shorter F-spec, dropping out of scope the requirements that are not yet clearly defined, or extending the analysis phase and running a requirements sprint to deliver a complete set of requirements.

                So, how's that for starters?
                Knock first as I might be balancing my chakras.

                Comment


                  #58
                  Originally posted by suityou01 View Post
                  An update :

                  I ran the meeting today and was clear about progress, lack of attendance, lack of interest. I am documenting all that I am short of and need to progress and escalating to the PM for his risk log. I am also presenting attendance records from the workshops.

                  Every time someone tried to hijack the meeting or digress I quickly but politely snatched it back.

                  I have also informed the PM there are two options, deliver a shorter F-spec, dropping out of scope the requirements that are not yet clearly defined, or extending the analysis phase and running a requirements sprint to deliver a complete set of requirements.

                  So, how's that for starters?
                  The other option is doing a half arsed job of it and given the lack of interest, that may be a better strategic fit.

                  Comment


                    #59
                    Originally posted by Old Greg View Post
                    The other option is doing a half arsed job of it and given the lack of interest, that may be a better strategic fit.
                    That was option 1, you tard.
                    Knock first as I might be balancing my chakras.

                    Comment


                      #60
                      Originally posted by suityou01 View Post
                      An update :

                      I ran the meeting today and was clear about progress, lack of attendance, lack of interest. I am documenting all that I am short of and need to progress and escalating to the PM for his risk log. I am also presenting attendance records from the workshops.

                      Every time someone tried to hijack the meeting or digress I quickly but politely snatched it back.

                      I have also informed the PM there are two options, deliver a shorter F-spec, dropping out of scope the requirements that are not yet clearly defined, or extending the analysis phase and running a requirements sprint to deliver a complete set of requirements.

                      So, how's that for starters?
                      Yeah!! That's the ticket.

                      <MF in me me me mode>
                      I've delivered my 4 month project early, (this morning, deadline 5pm), on budget, in time, exceeded the scope & all users up and running.

                      Client tried to pin something extra on the team yesterday and was shown the risk log, scope document and their own signature agreeing the deliverables they wanted and assumptions we made based on their input. Have agreed that they now need some extra work doing and that they are going to stump up some more cash.

                      </me me me>

                      I'm off to the pub and a couple of lines of coke. Have a good weekend.
                      What happens in General, stays in General.
                      You know what they say about assumptions!

                      Comment

                      Working...
                      X