The six Centripetal Forces For Successful Global Software Teams  Telecommunications Infrastructure  Product Architecture  Team Building  Development.

Slides:



Advertisements
Similar presentations
©SHRM 2008 Managing Virtual Work Teams by Frankie S. Jones, Ph.D. Employee and Labor Relations.
Advertisements

Copyright © 2012 Certification Partners, LLC -- All Rights Reserved Lesson 10: IT Project and Program Management.
Global Software Development Main issue:  distance matters.
Copyright 2002: LIIF Technology Architecture Review Database Application Architecture Database Application Architecture Collaborative Workgroup Architecture.
Mary Lou Maher University DECO2005, Semester 2, 2005 Virtual Teams.
Lesson 10 IT Project & Program Management.
© Prentice Hall CHAPTER 1 Managing IT in an E-World.
Architecture is More Than Just Meeting Requirements Ron Olaski SE510 Fall 2003.
SESSION 10 MANAGING KNOWLEDGE FOR THE DIGITAL FIRM.
Global Software Teams Problems  Global software teams are risky management propositions ? Cross-cultural differences Geographical dispersion (Burden of.
Project Management and Communication Represented by: Latifa Jaber Al-Ghafran.
Chapter Extension 1 Information Systems for Collaboration © 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke.
Requirements Analysis INCOSE Systems Engineering Boot Camp
The Six Centripetal Forces for Successful Global Software Telecommunication Infrastructure Collaborative Technology.
1 Chapter 7 IT Infrastructures Business-Driven Technology
Software Configuration Management (SCM)
An Introduction to the Hennepin County Hennepin County GIS Technical Advisory Group (eGTAG) 10/20/2009.
The Nature of Groups Ch. 8.
Understanding Management First Canadian Edition Slides prepared by Janice Edwards College of the Rockies Copyright © 2009 Nelson Education Ltd.
EC Review – 01/03/2002 – G. Zaquine – Quality Assurance – WP12 – CS-SI – n° 1 DataGrid Quality Assurance Gabriel Zaquine Quality Engineer - WP12 – CS-SI.
Configuration Management
Lesson 10: IT Project and Program Management. Lesson 10 Objectives  Identify resources for technical data  Identify project management fundamentals.
Software Configuration Management
Overview of Virtual Collaboration. Virtual Collaboration has far- reaching benefits Employee to Employee Employee to Employee R&D – Insights on regulatory.
QUALITY ASSURANCE PROJECT Improvement Coach The purpose of this session is to introduce participants to the role of the improvement coach and prepare for.
Global Software Teams. Sources – Handout Readings  Carmel “Global Software Teams”  Alexander “Virtual Teams Going Global”  Geber “Virtual Teams” 
Creating Business Workflow Using SharePoint Designer 2007 Presented by Tarek Ghazali IT Technical Specialist Microsoft SQL Server MVP Microsoft SQL Server.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 7-1 Chapter 7 Collaborative Computing Technologies:
Foundations of Information Systems in Business
Deloitte Consulting SCOOPS Session September 2003.
C2- How Businesses Use Information Systems. BMW Oracle’s USA in the 2010 America’s Cup.
Copyright Course Technology 1999
Collaborative Computing Technologies: Group Support Systems By Dr.S.Sridhar,Ph.D., RACI(Paris),RZFM(Germany),RMR(USA),RIEEEProc.
ECS.
Human and Institutional Capacity Development Project in Rwanda (HICD-R) CORE TEAM KM WORKSHOP February 26, 2015 Delivered by Courtney Roberts.
Problem Identification
Chapter 4. Writing Collaboratively © 2010 by Bedford/St. Martin's1 There are three basic patterns of collaboration: collaboration based on job specialty.
Ihr Logo Chapter 7 Collaborative Computing Technologies: Group Support Systems Turban, Aronson, and Liang Decision Support Systems and Intelligent Systems,
Service Transition & Planning Service Validation & Testing
Relationships July 9, Producers and Consumers SERI - Relationships Session 1.
7-1 Chapter 7 IT Infrastructures Business-Driven Technology.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
Chapter 3 Project Management Concepts
Copyright © 2002 by The McGraw-Hill Companies, Inc. All rights reserved. Slide 1.
7-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Chapter 7 IT Infrastructures.
7-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Chapter 7 IT Infrastructures.
©2007 by the McGraw-Hill Companies, Inc. All rights reserved. 2/e PPTPPT.
2.1 To accompany Excellence in Business Communication, 5e, Thill and Bovée © 2002 Prentice-Hall Chapter 2 Communicating in Teams: Collaboration, Listening,
Across the hall / Across the Globe Project Management: Challenges for globally distributed teams Vikas Sehgal Projistics San Jose,
Fall 2002CS/PSY Computer Support Cooperative Work (CSCW) Facilitating work by more than one person Computer Supported Cooperative Work  Study of.
Interagency Collaboration: Transition’s Reality Show Sharon deFur Jeanne Repetto coe.ufl.edu.
ANKITHA CHOWDARY GARAPATI
Tenant – Led Community Building in MHSA Housing Anne Cory Corporation for Supportive Housing 2/9/11
Chapter7 TELECOMMUNICATIONS AND NETWORKS. Content e-Business Systems – Cross-Functional Enterprise Applications – Enterprise Application Integration –
McGraw-Hill/Irwin © The McGraw-Hill Companies, All Rights Reserved CHAPTER 15 Creating Collaborative Partnerships.
Requisite Skills for IS Management and Interpersonal Skills.
Software Configuration Management SEII-Lecture 21
Structures That Support Learning Structuring Actions The structuring actions are levers that are available to a person, a team, or an organization to.
 What is Groupware  Why organization use Groupware  Categories of Groupware  Barriers of Groupware  Getting Groupware to work in your organization.
Office automation Office automation has changed the equipments and work habits of today’s end users and work groups None will be interested to work in.
Copyright © 2002 by The McGraw-Hill Companies, Inc. All rights reserved. Slide 1 Working in Groups PART FOUR.
Global Software Development Main issue:  distance matters ©2008 John Wiley & Sons Ltd. vliet.
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, All Rights Reserved Chapter 15 Creating Collaborative Partnerships.
New York City PMI Chapter Professor Martin Flank MBA, PMP April 20, 2016 Managing Global Projects.
Enterprise Resource Planning and Collaboration Systems
Business System Development
Software Project Configuration Management
MANAGING KNOWLEDGE FOR THE DIGITAL FIRM
Deloitte Consulting LLP SCOOPS Session
Lesson 10: IT Project and Program Management
Presentation transcript:

The six Centripetal Forces For Successful Global Software Teams  Telecommunications Infrastructure  Product Architecture  Team Building  Development Methodology  Management Techniques  Collaboration Technologies

Telecommunications Infrastructure  Telecomm Infrastructure Analogous to the foundation of a house A global software team requires a  Reliable network  High bandwidth network

Telecommunications Infrastructure  Invest in reliable, high bandwidth connections to all desktops at all sites  Establish consistent hardware and software platforms  Excellent telecommunications infrastructure does not negate the need for travel.

Collaborative technologies  Collaborative technologies promises to collapse distance and bring us closer to our colleague far away.  Team wall  Well run dispersed team will be using types of collaborative technology all at once. Place Time Same Different Video-conference Audio-conference E-chart E-whiteboard Voic Video-mail Groupware platform Calendar/schedule Discussion list meetingware Generic Collaborative technology

 Formal and Informal Communications Formal: help mitigate the inevitable communication breakdown that occur as a result of distance and culture Informal: collaborative technology needs to emulate the co- located work environment as much as possible, with its informal mechanisms for resolving problems (finding, sorting, processing, and retrieving the information that members need to solve a problem)  Research Result of a study on developers 2/3 of all messages were quite brief – less than 5 minutes Each day, on average, each developer sent 6 messages and received 16. Conclusion:  For developers, coordination and knowledge sharing is conducted by informal lateral networks  For dispersed team there is a need to encourage a great deal of informal communications Collaborative technologies

 Collaborative Technology supports Deliberation and Workflow: Deliberation: The classic problem-solving activities of identifying the problem, evaluating the solutions, selecting a desired plan, and monitoring its implementation. Workflow: routing objects from one person to another in need of work, review, or authorization. Collaborative Technologies

 Objectives of “Generic” Collaborative Technology 1. Serves as a team memory & knowledge center  The team store and shares information and knowledge across a work unit 2. Provides each team member a 360 view  All members at all sites are informed regarding task, status, people, and other dynamic team information (transparency) 3. Forster a sense of community  The “glue” creates and maintains interpersonal relationships Collaborative technologies

Collaborative Technologies  Selected Collaborative Technologies and Their Use  Is the most important collaborate technology  “when we had trouble with we went insane”  Phone to use ration 1:20 Time zone differences Developers are comfortable with is part of the professional culture in where in the world Help to understand language differences Facilitates lateral communication – communications that does not go through a formal chain of authority.

Collaborative Technologies  Groupware Platforms , Document repositories, discussion lists, Calendars, and Workflow automation. The industry leader is Lotus Notes  Group Calendar/ Group Scheduler An excellent tool to inform dispersed team members of different holidays, milestones, events, and meetings. Time zones differences, different work hours, and summertime clock changes.  Discussion Lists  Audio-conferencing  Electronic Whiteboard

Collaborative Technologies  Video-conferencing Promises  To reduce the need for travel  Accelerate the process of reaching decisions  Reduces development cycles by accelerating problem resolution  Promote creative thinking  Foster bounding between people and building the sense of teamness Limitation  Technical limitations  Cost issues  Quality problems  Synchronicity issues (same time)  Behavioral norms  Are collaborative technologies culturally neutral?

 Cultural Overlay of Collaborative Technology In High-context Cultures  Much of the communication is outside the body of the message – in greeting style, gestures, posture, etc  Forces users toward a high information mode in their message, away from the ambiguous contextual cues  The most culturally neutral collaborative technology is even then it is not neutral.  Example American and Scandinavian decision making norms vs. Decision making in Japan Collaborative Technologies

 Objectives 1. Serves as a team memory & knowledge center  The team store and shares information and knowledge across a work unit 2. Provides each team member a 360 view  All members at all sites are informed regarding task, status, people, and other dynamic team information (transparency) 3. Reduces duplication of effort  Software engineers need to share many types of project knowledge, otherwise they may end up fixing the same bug or working on software components that are out of date as result of others’ work. 4. Supports coordination activities and workflow  Need to support team members self-managing tasks via electronic lateral coordination and via electronic workflow procedures. Support Quality Assurance  Bug tracking, version control, requirement tracking, are essential to maintaining quality level. Collaborative Technologies to Support Software Engineering CT-SE

 CT-SE Functions Software configuration management (SCM)  As a control and enforcement mechanism, it establishes formalism: used to control processes, set the rules, and structure the workflow within a team  As a coordination mechanism, it is an effective way to create up-front dialogue among the dispersed sites. Project status Notification services Project scheduling and tasking CASE and process management Programming tools Bugs and change tracking Team memory and knowledge center Collaborative Technologies to Support Software Engineering CT-SE