You're struggling to meet project deadlines. How do you decide which feature requests to prioritize?

When struggling to meet project deadlines, deciding which feature requests to prioritize is crucial. Start by assessing the impact of each request on your user base—will it significantly enhance the user experience or solve a critical issue? Prioritize features that deliver the most value to users. Additionally, consider the potential return on investment (ROI) for each feature; those with higher ROI should take precedence, as they're more likely to contribute to the overall success and adoption of your web application. Balancing user needs with strategic value ensures you focus on what truly matters.

You are so close to the deadline, and you have to choose which feature to develop and what to leave out. No matter how close the launching is there are features you can't do a way with say social app can't be launched without authentication.

When deadlines are tight, I first look at the impact each feature will have. I ask myself: Will this significantly enhance the user experience or solve a major issue? Features that bring the most value to users usually get top priority. It’s about making sure every minute spent adds meaningful improvements.

Looking at the fact the the features may have same weight in need, Let's look at time needed to deliver each module. The module that is easier to do is given a higher priority to clear the board for others.

Not all features are created equal in terms of effort. I break down tasks and estimate how long each will take. Quick wins with big impact? Those are my go-tos. Features that demand a lot of time but offer less immediate value? They can usually wait.

If a given feature depends on another, say developing a social app user liking depends on authentication. Then authentication is done first

Some features hinge on others being done first. I map out these dependencies to avoid bottlenecks. Prioritizing features that pave the way for others helps keep the project on track and prevents crunch-time chaos.

What do the stakeholders say about what needs to be done first. It is paramount to ensure clients have their needs met. Most times the clients may have a better domain knowledge and may be understand what they need to achieve it may be frustrating when the deployed product does not meet minimum requirements

Stakeholders—whether clients or team members—have valuable insights. I make it a point to gather their input on which features matter most to them. This helps align priorities with both business goals and user needs, ensuring we’re all on the same page.

Does a given feature align with the objectives of the system to be developed, Some features may wait as you be supporting goals not core

Zoom out and look at the bigger organisational objectives. How do the features fit into this larger strategy and which will contribute the most to its success. Prioritise features based on their relative impact, effort required to deliver and any inherent dependencies. You may be able to rescope larger blocking jobs into smaller ones that can be partially delivered. This can unblock other features/team members and increase overall delivery velocity. If you find that low-impact features are becoming a time sink don't be afraid to pause them and put them back on the backlog for when time is less constrained.

I always tie feature prioritization back to the core objectives of the project. If a feature doesn’t align with the main goals, it’s probably not worth focusing on right now. Staying focused on the big picture helps avoid getting sidetracked by “nice-to-haves.”

Development is dynamic, and priorities can shift. I stay flexible, ready to adjust when new challenges or insights emerge. This adaptability is key to meeting deadlines while still delivering a quality product that meets user needs.