Está haciendo malabarismos con las demandas contradictorias de los clientes para las características del proyecto. ¿Cómo se decide qué es lo que tiene prioridad?

In order to adequately assess needs, it is vital that prior to starting any project a robust framing workshop is undertaken. This helps in identifying the critical features and their importance to each client, what they want and don't want is essential so effort is not wasted addressing issues the client may not care about. Knowing where value is added for the client is essential.

I prioritize based on factors like client impact, alignment with project goals, deadlines, and resource availability. I assess which features deliver the most value, address urgent needs, and fit within current capacities, then communicate decisions clearly to manage expectations.

Evaluate the technical complexity and risk associated with each feature. Features that are less complex and carry lower risk might be prioritised higher, especially if they can be implemented quickly.

Good technical leadership will work with the engineering team and, more importantly, listen to them. An area of frustration for engineers is when they estimate a task will take 3 days, but the engineering "leadership", who doesn't touch the code, says it can be done in 2. It is also important to listen to the engineers when they raise concerns on features. Remember, a task might take a senior engineer 3 days to complete and a junior engineer 4 days. If the junior is doing the work, go with the junior's estimate.

Establish a feedback loop to continuously monitor the impact of implemented features and gather input from clients. Use this feedback to reassess and adjust priorities as needed. Adopt an agile approach that allows for flexibility and iteration.

This is where a Gantt chart proves invaluable to a client. This will visually help them to see what resources are currently working on, what their expected completion time is, and what tasks are next in their queue. Let them help participate with the product owner and technical leadership to prioritize the backlog. This often results in an internal meeting where they come back and lay out what features are necessary and when. It also helps them to see when engineers are scheduled for > 8 hour days and / or weekend work. Then they (hopefully) understand that engineers are people too and burning them out hurts longer term goals.

This is when change control is most important. Projects do not go in the ditch if stringent change control is in place . If not, the client will expect everything not is scope, for free, and that will put you out of business!

Communicate the rationale behind prioritisation decisions to all stakeholders. Explain how decisions were made based on value, feasibility, and strategic alignment. Manage client expectations by discussing timelines, potential trade-offs, and the reasoning behind prioritization. Ensure clients understand that not all features can be delivered simultaneously.