User Tools

Site Tools


wiki:ghc:ghc18:az667

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

wiki:ghc:ghc18:az667 [2018/10/14 15:07] (current)
usankarlal_gmail.com created
Line 1: Line 1:
 +====== Session Title: AZ667: Remotely Agile? Effective Interaction with Distributed Agile teams ======
 +
 +===== Abstract: =====
 + Love it or hate it, Agile is here to stay. Agile'​s focus on face-to-face communication can increase collaboration,​ which is great! But how does that collaboration work when everyone isn't in the same room - or the same country? Come hear lessons from 12 years of work with distributed teams, and learn tools and techniques to make interaction easier when some (or all!) of your team is remote.
 +===== Speaker =====
 +** – Dorinne Hammons, Sr. UX Designer, Kelsey-Seybold Clinic**
 +==== About the speaker: ====
 + As the Senior User Experience Designer at Kelsey-Seybold Clinic, Dorinne Hammons leads all user experience and user interface design efforts for 19 multispecialty medical clinics. With more than 12 years of experience in interface design and project management in both the medical field and in oil and gas, Dorinne has worked on a variety of conventional and unconventional software teams and learned how to use many different project management methodologies. Dorinne is passionate about bringing teams together and inspiring them to develop user-centered applications – specifically in the medical field, where having easy-to-use,​ accessible interfaces is vital to patients and healthcare providers alike. She is currently managing software development projects across human resources, healthcare finance, marketing, pharmacy, and electronic medical records.
 +===== Session Notes: =====
 +  * Agile Manifesto – Quick review
 +  * Team organization
 +       * Since all interactions are happening via phone, most of the time people turn out to be ‘just’ resources – 
 +       * They are just black box – especially when you don’t have any common things (culture, sport etc.,)
 +       * Increase face-to-face communication
 +              * You need to have a human connection – personal touch
 +              * Travel - Depending on the size of the team – have the remote resources travel to the other locations of the team, 
 +              * Video – Have video conferences to the meetings (not all meetings though)
 +              * Establish personal connection – Exchange your photos
 +  * Understand the cultural differences
 +       * It took the speaker some time to understand that in some culture they won’t answer ‘No’ which posed a challenge to completing the deliverables on-time. If you are facing similar issue – try to ask the question in different ways instead of merely asking can you complete the task. That will make them open for conversation rather than ‘yes’ or ‘no’ type of answers.
 +       * Distributed team communication happens over the air – We don’t see the body language. Be cognizant of the language, cultural differences,​ and other differences depending on the team you are working with.
 +       * The best output emerges from self-organizing teams
 +
 +  * Use collaborative tools 
 +       * Status tracking:
 +              *  In the classic agile, it is a post-it move method since all team members are co-located. In distributed teams, use tools to create that visualization.
 +              * Tools such as Visual Studio (Team foundation server), ScrumDo, Sharepoint, excel, Agilo for trac, Wrike, Trello, CA Agile Central are few examples for status tracking tools
 +
 +  * Here are few examples of the tools that are commonly used across companies in their distributed teams:
 +  * Status Tracking Visual Studio (Team foundation server)
 +       * ScrumDo
 +       * Sharepoint
 +       * Excel
 +       * Agile for trac
 +       * Wrike
 +       * Trello
 +       * CA Agile Central
 +  * Meeting Tools Cisco Webex
 +       * GoToMeeting
 +       * Slack
 +       * Skype
 +       * Hangouts
 +       * Adobe Connect
 +  * Collaboration Tools Quip
 +       * Scribbler.com
 +       * Slack
 +       * Twiddla
 +
 +  * Importance of facilitation
 +       * It is very important to keep the meetings on-time. The meetings can go long as the team is meeting on the phone. Start and end the meetings on time to have the effective participation.
 +       * Take all the irrelevant points offline and have a follow-up conversation on them (meeting / mail depend on the situation)
 +       * Avoid side conversations. Focus on the meeting you are on. 
 +       * Mute your phone when you are not talking
 +       * Set the expectations up front with team you are working with
 +              * Be cognizant of the fact that we work in various time zones
 +              * If needed we can have a representation from the team instead of having the entire remote team attending the longer / out-of-hours meetings
 +
 +  * Collaboration
 +       * Collaboration is the key. We can still do everything with the distributed team when the right tools, rules are laid out.
 +       * Remember – it is very easy to forget to collaborate if they are not in the room
 +       * If you’re a remote person, please ensure that you are available while you are working, and answer your phone.
 +       * Agile has quick turnaround times. If you don’t respond, it will delay the stuff further.
 +
 +  * Summary
 +       * Team organization
 +       * Meetings
 +       * Collaboration
 +
  
wiki/ghc/ghc18/az667.txt · Last modified: 2018/10/14 15:07 by usankarlal_gmail.com