Being able to go into a meeting and talk about project requirements is sometimes

Question

Being able to go into a meeting and talk about project requirements is sometimes difficult when you do not know much about what the client needs. The clients always like to use that time to figure out what their department wants to get out of the new product. As the lead application developer, you have to keep the client(s) focused.

What are some techniques that you could use in the meeting that would benefit everyone, by keep the client from wasting your valuable time, and still make progress documenting project requirements in the meeting?

Explanation / Answer

Documenting project requirement in a meeting can be a hard task for both the presenter (us) and the members present in the room. It goes without saying that proper communication and a strong sense of presence is required in order to gather the attention of people. Confidence is also the key. In order to engage the audience, it is necessary that your presentation is interactive. Nobody likes a dull presentation and there is also the need to practice everything beforehand. The fact that nothing can be left on chance is a true one.

Especially, in the case, you want to condense the entire presentation into bite-sized information that the audience can chew upon (metaphorically speaking). The information should be precise, to the point and the fact that every point needs to be concerned with the various aspects that need to be followed in order to realize the requirements of the project makes it even more important. The biggest thing to remember is that larger data should not be brought out unless the audience demands it or there is a need for it due to the change in plans.

Related Questions

Navigate

• Browse (All)
• Browse B
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.