Requirements Elicitation Discussion

1. As a project manager, you will be accountable for planning the requirement elicitation activities. What types of methods will work best for your project and why? 2. What challenges will you face in your quest to understand your customer’s expectations? 3. What challenges will you face in your quest to understand your customer’s expectations?

Uploaded by

hzou6509

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

24 views

Requirements Elicitation Discussion

Uploaded by

hzou6509

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

You are on page 1/ 4

As a project manager, you will be accountable for planning the requirement elicitation

activities. What types of methods will work best for your project and why?

As a project manager, selecting the right elicitation methods is dependent on several factors such as
the scope of the project, its complexity, stakeholder availability and preferences, budget, and timeline.
It is often necessary to use a mix of different methods to ensure that all requirements are thoroughly
covered and to address the constraints of individual techniques. In my current role, I primarily rely on
interviews and workshops for requirements elicitation.

In my opinion, interviews and workshops are popular because of their effectiveness and widespread
use in today's work environment. Interviews, a traditional and widely used technique, facilitate
informal interactions that are important for effective data gathering. Their efficiency in rapidly
collecting substantial data depends on the quality of interaction between participants. Interviews come
in three primary forms: unstructured, structured, and semi-structured. Unstructured interviews
encourage conversational exploration with limited interviewer control; structured interviews follow
predetermined questions for targeted information gathering, while semi-structured interviews combine
elements of both (Zowghi & Coulin, 2005).

Workshops offer another valuable method for requirements elicitation, with various formats available.
Cross-functional workshops engage stakeholders from diverse business areas, with defined activities
and active developer involvement. Creativity workshops encourage innovative thinking and
expression (Maiden, Gizikis, Robertson, 2005). Workshops promote active participation, consensus
building, and a shared understanding of project objectives among participants.

To conclude, using a combination of multiple methods is often essential to ensure comprehensive

requirement coverage and to overcome the limitations built-in in individual techniques.

What challenges will you face in your quest to understand your customer’s expectations?

As a project manager, I have faced several challenges, including unclear or changing customer
requirements, conflicting stakeholder priorities, communication barriers due to cultural differences,
and scope creep. To address these challenges, it is essential to proactively engage stakeholders,
communicate effectively, and continuously manage requirements.

What tools will you use to negotiate the scope of the project with the customer?

In my opinion, the most effective approach to negotiating project scope with customers is to leverage
a combination of "soft skills" and "hard skills". Soft skills refer to teamwork, interpersonal
communication, conflict resolution, negotiation proficiency, and leadership abilities. On the other
hand, hard skills involve tasks such as risk analysis, quality control, scheduling, budgeting, change
control, planning, and project execution. The successful outcome of negotiations is often a result of
the synergy between these soft and hard skills.
References

Maiden, N., Gizikis, A., & Robertson, S. (2004). Provoking Creativity: Imagine What Your
Requirements Could be Like. IEEE Software, 21(5), 68–75.
https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=1331305

Zowghi, D., & Coulin, C. (2005). Engineering and Managing Software Requirements. Open
Publications of UTS Scholars, pp. 19–46. UpdatedChapter2-ZowghiCoulin-v20.doc (uts.edu.au)
Hi Soumya,

I acknowledge your message and appreciate the insights you shared regarding the methodologies and
tools proposed for project management in the healthcare industry. Your approach, which uses
techniques such as user stories and analysis of previous documents and prototypes, demonstrates a
thoughtful strategy. I also appreciate your emphasis on the importance of continuous communication
and collaboration, which are critical elements for navigating the complexities inherent in healthcare
projects and ensuring alignment with customer expectations.

I agree that incorporating user stories and analyzing previous documents can help in understanding
project requirements. However, to further enhance stakeholder alignment, it might be beneficial to
supplement these methods with targeted interviews or workshops to gain insights directly from key
stakeholders.

Finally, I would appreciate further elaboration on your strategies for navigating potential conflicts or
discrepancies in customer expectations, considering the industry's complexity and regulatory
constraints.

Best,

Eric
Hi Adriely,

I appreciate the insights you shared regarding the methodologies and tools that you proposed for your project,
the Urban Eden initiative in Los Angeles. I found your approach to be very effective in gathering diverse
perspectives and aligning the project. Your use of techniques such as community workshops, stakeholder
interviews, public surveys, and review of strategic planning documents demonstrates a well-rounded strategy.

I also agree with your suggestion to incorporate Design Thinking principles into the requirement elicitation
process to foster creativity and innovation in understanding customer expectations. However, I believe
leveraging visual aids such as stakeholder maps and matrices during scope negotiation discussions could
enhance stakeholder understanding and alignment.

Lastly, I would appreciate it if you could elaborate on how you plan to integrate insights from stakeholder
analysis and WBS into the project planning process to ensure alignment with project objectives and stakeholder
expectations.

Best

Eric