10月23日(三)【20回娘家系列講座】專案管理需求中, 溝通脫節經常發生, 那是誰的錯?
發布時間：2019/8/1 上午 11:21:23
The infamous requirement communication breakdown, Who are to be blamed?
Anyone who involves in requirement elicitation would surely be familiar with this challenge. Therefore, business analyst would spend tremendous time in interviewing users so to elicit their “requirements”, documenting “requirement documentations” as detailed as possible. Architect would complete demand hardware and software specification to plan the architecture load. Developer develops strictly according to the “requirements”. While in project management, a change request is purported as “sinful” as breaking a law.
Is there a highly plausible requirement definition and communication method? And Who are responsible?
This sharing and discussion session seeks to explore them.
Delivering business values is Kim Ling’s top goal. This propels her relentless pursuit for Quality Project Management and Delivery. She has led various programs and projects during her years in Intel. Even after her responsibility-shift into management role, when she relocated to Taiwan from Singapore six years ago, she has continued adapting and experimenting different project management techniques. In this sharing, she would like to discuss her novice experience with “inside out” requirement gathering approach.