• HobbitFoot
    link
    fedilink
    English
    arrow-up
    3
    ·
    19 hours ago

    But you’re dealing with the mechanics on their side causing an issue with approval.

    At that point, I’d look to remove scope to get under the 100k threshold.

    • Ephera@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      18 hours ago

      Sure. If I knew what the scope of this offer even was, I might have suggested doing that.

      To be fair, the contract has a statement in there, that we don’t actually have to complete the features written down, we just need to put in the amount of work that this money pays for. The customer is more or less within our own company, so it’s not like anyone’s going to sue the other side anyways. But yeah, it still just feels weird to hear management talking about fictitious features for a random amount of money.

      Sometimes, I am worried that if the customer is dissatisfied one day, that management will be angry at us for giving such a bad estimate, even though we didn’t. For example, as far as I’m aware, the current offer contains the complete list of features from a meeting where we explicitly brainstormed what would still be required. We did not discuss how much of that we could complete within the budget we’re given. But if I now notice that management is offering the whole list for far too little money, am I supposed to intervene or are we doing the bullshit charade again?

      • HobbitFoot
        link
        fedilink
        English
        arrow-up
        2
        ·
        17 hours ago

        If there isn’t a written down set of features, it sounds like they want you to get done with as much as you can for less than $100,000.

        That’s going to require more coordination in your end, since it means holding their hands while they prioritize what minimum features they can accept.