Hot answers tagged

6

My answer is based on my observations of IT work in the public sector. YMMV. What I have observed is quite a bit of project overruns, both cost and schedule, on IT projects in the space where I worked. The drivers in my view begin with initial proposals being far too optimistic--on the verge of totally fake--driven by some sense of price-to-win. In a ...


5

Notwithstanding how you were supposed to get paid by the client, you need to have the best interests of your client in mind. This means you need to inform your client of your inability to resolve the issue and make a recommendation to your client to either find another solution provider or to abandon the solution because maybe there might not be an ...


3

Whether or not it is 'normal' is highly subjective and contextual. What is more important is whether or not it is a problem (which I assume it is, otherwise why are you here asking about it?), and, if so, how to fix it. The problem you have is that of clients asking for last-minute amendments. This can be broken down into two sub-problems: 1) The client is ...


1

Risk management approaches As any risk, you might have four ways to address them: Avoid them Reduce them Share/transfer them Accept them Based on your situation, you invest a considerable amount of efforts on reduce them as much as possible. Thing is, maybe they can't be reduced any further and thus, you need to explore other approaches. What else to do?...


1

I agree with David, there’s no canonical answer. In my experience (I've worked mainly in the private sector), it depends a lot on the context of how this happens: Is the team fully able to work together? Have they worked for a long time together? Is the project something innovative? Or Do you have a clear understanding of what you want to do? Are most ...


1

It can be all too common, yes. PMBOK does refer to several techniques which can help the process, however; When collecting requirements and then feeding into scope - obtain customer acceptance requirements. Build a work breakdown structure, containing 100% of the work required to deliver the project. When you're reporting on the project progress, always ...


1

That sounds like there was only an informal change request process and maybe an informal project close process? The idea of a change request process is to make situations like this less likely. The client requests a change, they're told to give more details, and then they're informed how it will impact the budget and scope and schedule. The act of getting ...


Only top voted, non community-wiki answers of a minimum length are eligible