jeudi 8 janvier 2015

What is the ideal mindset for a developer participating in a requirements gathering meeting?


As an mid level developer on my team, I participate in requirements gathering/scope planning meetings of projects that I will be part of. I have been finding it difficult to come up with the questions that add value to the discussion or to my knowledge. On some self analysis, I found that knowing that there is a senior engineer incharge of the project who would lead the discussion , has caused me to be laid back in some of these discussions. But I do want to get to a point where I am entrusted more responsibility and gain skills to handle projects on my own. Though mindset is a bit abstract term to answer about, I would like to get some advice on few things listed below




  • What kind of preparation will I need to gain most out of these meetings . From observations from team members, I noticed that understanding what all systems that the project is going to impact , What business decisions will majorly impact the project design etc. are some of them. Please do add




  • Do I need to avoid thinking about low level implementation details for every requirement. On one hand I feel it's important to consider them because I will know about the feasibility but I also understand it hinders considering all choices.




  • Finally, as a developer ,what is something that I should not be worried about? (my favorite).







Aucun commentaire:

Enregistrer un commentaire