|
|
我的澳洲朋友给我回复了!
1. I would say there was not such thing as a "typical day" - coz every day was so different. I would say that it varied depending on the phase of the project that I was in, and then explain each phase and what my role/responsibilities were. I would also say it depends on the activity and level of engagement with stakeholders - sometimes meeting with a lot of ppl, other times spending time on my own reviewing and documenting specs.
2. I would first identify what the business problem is (eg client complaints about functionality on the website, product gap, process inefficiency), and who the key people are. I would do analysis of any information I have on hand (historical docos etc), speak to other BA/PMs to further understand and develop my knowledge on the subject, then approach the interal client/key people to clarify my understanding of the problem and current state, and determine the scope of the requirements, and then detailed requirements.. I would document it all, and send for review. Then schedule a workshop to obtain feedback.
3. I would ask for clarification on the meaning of "defeat found"? I don't know what that means. In terms of communication, I would say that I try and modify my style to the audience. As a ba, u need to talk to a variety of diff ppl - including business, legal, executives, IT/developers, testers.. They each speak a diff language, and u need to modify your style to suit. |
评分
-
查看全部评分
|