1 / 7

Being in Each Other’s Shoes

Being in Each Other’s Shoes . Anandi Hira. Background . Clients Medical, Business, Finance, Theater, Law, etc. Jargon Processes May use technology However, they do not know how software is developed Do not understand the back-end of the technology they use/want. Background.

jalen
Download Presentation

Being in Each Other’s Shoes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Being in Each Other’s Shoes AnandiHira

  2. Background • Clients • Medical, Business, Finance, Theater, Law, etc. • Jargon • Processes • May use technology • However, they do not know how software is developed • Do not understand the back-end of the technology they use/want

  3. Background • Development Team • Computer Science, Software Engineering • Bachelor’s Degree • Very few have experience in industry • Know how to build software, but might not understand what clients want • How do they do their work • What is relevant to them • How they think

  4. Misunderstanding • Unfamiliar jargon • Words with similar meanings • Example: Application • Brain cycle • Lack of concentration • Many others!

  5. Let’s Paraphrase! • The client(s) should paraphrase what the developers stated during the meeting • The developers should paraphrase what the client(s) stated during the meeting • Distribute among all attendees

  6. Purpose • Not to embarrass (surprisingly) • Promote understanding, friendly environment • Clarity • Clear requirements, expectations early • Quicker and cheaper solutions • Resolve Issues, come up with options, come to an agreement • Satisfaction with and success of project

  7. References • “Team Coordination Training.” U.S. Department of Homeland Security: U.S. Coast Guard. http://www.uscg.mil/auxiliary/training/tct/chap7.pdf. Page 8. • Eckes, George. “Six Sigma: Team Dynamics.” John Wiley & Sons, Inc. Hoboken, New Jersey. 2003. http://books.google.com/books?id=l73GXmybLBAC&pg=PA92&lpg=PA92&dq=team+success+paraphrasing&source=bl&ots=iXW4_A7ass&sig=Ub7w3aqyn-46YPgMHFFxfQyNDxY&hl=en&ei=80V8TZb3Lo30rAGjv-zOBQ&sa=X&oi=book_result&ct=result&resnum=5&ved=0CDAQ6AEwBA#v=onepage&q=team%20success%20paraphrasing&f=false. Page 92. • McKanders, Carolyn and Robert J. Garmston. “Skillful Paraphrasing Allows Groups to Examine What is Being Said.” Central Michigan University. 2006. http://www.centerforexcellence.cmich.edu/MSIM/Articles/Skillful%20Paraphrasing.pdf. Page 1.

More Related