Can you describe a method to estimate the resource needs for a project with undefined requirements?

In college, I worked on a significant group project for a marketing class where the requirements were initially vague. To estimate our resource needs, we first held a brainstorming session to outline potential tasks and objectives based on our understanding of the assignment. We divided the project into phases, such as research, design, and presentation. For each phase, we discussed what resources we would need, like software tools, research materials, and time commitments from each member. We also consulted with our professor for guidance on expectations. By approaching it this way, we developed a more refined estimate of what we needed, which allowed us to allocate our time and efforts efficiently. This experience taught me the importance of collaboration and flexibility in project estimation.

While working part-time at a retail store, I was tasked with organizing a promotional event with unclear objectives. To estimate the resources needed, I started by gathering input from my manager and coworkers about what previous events had required, such as promotional materials, staffing, and inventory levels. I then created a checklist of potential resources and estimated quantities based on the anticipated customer turnout. This helped me communicate what we might need to order and how many staff members should be scheduled. Although we had to adjust some estimates as we got closer to the event, this proactive approach ensured that we were well-prepared and could adapt quickly to changes, making the event a success.

In my first job at a small tech firm, I was part of a team tasked with launching a new software feature, but the requirements were still being defined. To estimate the resource needs, I organized a meeting with my team to break down the project. We created a rough outline of the deliverables and identified key milestones. By leveraging the expertise of more seasoned colleagues, we could make educated guesses about necessary resources, such as development time, testing requirements, and potential software tools. We also agreed to revisit our estimates regularly as the project evolved. This collaborative and iterative approach not only helped us stay on track but also ensured that we could adapt to any changes efficiently.