Distributed Agile: Ten Guiding Principles Raja Bavani, Chief Architect, Mindtree 28-Dec-2013 資工三 A-100502544- 梁乃勻.

Slides:



Advertisements
Similar presentations
Metrics and Databases for Agile Software Development Projects David I. Heimann IEEE Boston Reliability Society April 14, 2010.
Advertisements

FMS. 2 Fires Terrorism Internal Sabotage Natural Disasters System Failures Power Outages Pandemic Influenza COOP/ Disaster Recovery/ Emergency Preparedness.
Are Parametric Techniques Relevant for Agile Development Projects?
Agile Software Development Robert Moore Senior Developer Curtin University.
Chapter: 3 Agile Development
CUPA-HR Strong – together!
Definition of Information System INFORMATION SYSTEM IN MANAGEMENT  An information system can be defined as set of coordinated network of components which.
COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. 1 Agile documentation development methodology Giby Panicker and Judith Benjamin 1-Dec-2012.
Open Data Center Alliance (ODCA) Commercial Framework Ado Trakic Technical WorkGroup Contributor, ODCA Enterprise Architect, Marriott International.
Office of the State Chief Information Officer Customer Satisfaction Survey Enterprise Project Management Office Gaye Mays Kathy Bromead October.
SCRUM John Drew. SCRUM - overview Scrum is a project management discipline that has evolved since the early 1990s to deliver software that meets business.
Agile Software Methodologies Employee, Customer and Organization Factors 歐俊良.
Extreme Programming Team Members Gowri Devi Yalamanchi Sandhya Ravi.
The W3C Web Accessibility Initiative (WAI) Inclusive learning through technology Damien French.
1 July 23, 2002 Strategic Technology Plan Briefing to LOT Committee.
Agile Quality Assurance Reference Model Jacob Sandnes 3/23/15.
Project Management Communications Management*
1. 2 SIX SIGMA "Delivering Tomorrow's Performance Today" AIR CDRE ABDUL WAHAB.
Agile Testing with Testing Anywhere The road to automation need not be long.
The Many Contexts of Software Architecture
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
8/17/2015(c) 2013 Morell D. Boone1 Impact of Implementing Virtual Work Tools in the Globalization of Enterprises Morell D. Boone, Ph.D. Emeritus Professor.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
CMM Level 3 KPA’s CS4320 Fall Organizational Process Focus (Goals) Software process development and improvement activities are coordinated across.
Qatar Planning Council 1 Best Statistical Information to Support Qatar’s Progress Statistical Capacity Building for Information Society in Qatar.
Software Development Process
Achieving Agility with WSO2 App Factory S. Uthaiyashankar Director, Cloud Solutions WSO2 Inc. Dimuthu Leelarathne Software Architect WSO2 Inc.
 Contoso is working on Wireless 1xEvDo application to handle high speed 3G application data transfer (voice, video data) in mobile phones while working.
The Uses of Blackboard in IDARI
Effective Pair Programming Practice - An Experimental Study Authors:Venkata Vinod Kumar Padmanabhuni, Hari Praveen Tadiparthi, Muralidhar Yanamadala, Sagar.
ON THE ROAD TO BUSINESS APPLICATIONS OF SEMANTIC WEB TECHNOLOGY Sematic Web in Business - How to Proceed IASW Kari Oinonen Kiertotie 14.
AGILE Methodology. AGILE  derived from the word ‘agile manifesto’, also called the Manifesto for Agile Software Development which is a formal proclamation.
Resource Systems.  The need for agility  History of Product Development  Delivery of EPCOT  Future Challenges & Recommendations  Reflection  Questions?
Disturbance Strategy to Achieve Self Organization.
Agile and XP Development Dan Fleck 2008 Dan Fleck 2008.
資工 4A 陳怡秀 Microsoft Visual Studio’s Journey to Continuous Delivery.
Human Resource Management Lecture 27 MGT 350. Last Lecture What is change. why do we require change. You have to be comfortable with the change before.
Distributed Agile: Ten Guiding Principles Student: Yu Chang 張鈺 Raja Bavani, Chief Architect, Mindtree 28Dec Department of Computer Science and Information.
A Collaborative-Interaction Model of Software Project Development An Extension to Agile Based Methodologies Rehan Akbar#1, Mohd Fadzil Hassan#2 Department.
Role-Based Guide to the RUP Architect. 2 Mission of an Architect A software architect leads and coordinates technical activities and artifacts throughout.
DEV 303 Visual Studio "Whidbey" Enterprise Tools: Source Control and Work Item Tracking Brian Harry Product Unit Manager Microsoft Visual Studio.
WG4 SUMMARY DATA WG4 can be summarized in one word: Management of data: Use of data How do we keep track of, exchange and manage all the data that is generated.
Build the Right Team 1 Organize for Success 2 Build Coalition with Business Partners 3 Maintain Flexibility 4 Key Success Factors KSF 1.1: Relentlessly.
Sonali Bhasin. Abstract  Software organizations that are transitioning from traditional method to Agile development methods.  Study various challenges.
Agile Methodology Paul Mohrbacher. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through.
What Is DevOps? DevOps is "a portmanteau of 'development' and 'operations'" and is "a software development method that stresses communications, collaboration,
LOGO Introduction to DevOps 中科大移动云计算系统实验室 孟宁. LOGO Page  2 Agenda Introduce DevOps DevOp Patterns How to Start Adopting DevOps.
RISK CONTROL.
A HANDBOOK FOR PROFESSIONAL LEARNING COMMUNITIES AT WORK CHAPTERS 1-3 Learning by Doing.
IT and Network Organization Ecommerce. IT and Network Organization OPTIMIZING INTERNAL COLLABORATIONS IN NETWORK ORGANIZATIONS.
Confidential and Proprietary 1 Project Management using Scrum at Wachovia.
Developing a Project Management Standard for Your Organization Francine DiMicele, PMP June 08, 2015 NC Piedmont Triad Chapter.
NSF Middleware Initiative Purpose To design, develop, deploy and support a set of reusable, expandable set of middleware functions and services that benefit.
Alberto Zilio, Director – Public Affairs, AT&T Europe The Connected Cities.
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.
CEPF Strategic Funding Direction 3 Meeting: 28 th June, 2006 Outcomes Monitoring: Status & trends in biodiversity Establishing standard regional monitoring.
Building Systems for Today’s Dynamic Networked Environments A Methodology for Building Sustainable Enterprises in Dynamic Environments through knowledge.
Embedded Systems Software Engineering
Continuous Delivery- Complete Guide
Supply Chain Management
An Analysis of Project Management Practices Related to Constructability followed in Indian Construction Industry Sharmin Khan Assistant Professor, Department.
Script-less Automation: An Approach to Shift-Left.
Robert Hayes & Sambo Zulu Leeds Beckett University, Leeds
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Software engineering -1
How to become PMI-ACP ®?.
Applying Agile Lean to Global Software Development
SD5953 Successful Project Management AGILE SOFTWARE DEVELOPMENT
Presentation transcript:

Distributed Agile: Ten Guiding Principles Raja Bavani, Chief Architect, Mindtree 28-Dec-2013 資工三 A 梁乃勻

Outline 1. Methodology driven by project teams 2. Consistent usage of common tools improve productivity 3. Infrastructure for communication and coordination is crucial 4. Knowledge management is the key to success 5. Quality is multi-dimensional,and owned by everybody 6. Distributed Agile requires an inclusive approach 7. Governance is the backbone of successful distributed teams 8. Automation enables sustainable pace 9. It is essential to streamline the accumulation and payoff of technical debt 10. Iteration progression is a common phenomenon and ensuring early success is a collective responsibility

Consistent usage of common tools improve productivity Team members in a distributed team must have access to a standardized set of tools for engineering activities such as design, coding, static analysis, unit testing, build automation, test automation, defect tracking, and so on. Disparate tools result in compatibility issues and loss of information and hence impact team productivity. Besides, they need to use such tools consistently in order to realize the benefits.

Infrastructure for communication and coordination is crucial Team members of geographically distributed teams depend on phone calls, chat, and video conferencing for communication. Also, they depend on webbased tools for agile project management, issue tracking, defect tracking, etc., It is crucial to have an infrastructure that supports distributed development in order to relieve teams from technical issues related to communication and coordination.

Iteration progression is a common phenomenon and ensuring early success is a collective responsibility Distributed teams show progress over the first three or four iterations. Aiming for instantaneous results from the first iteration is an unrealistic. Ensuring early success is a collaborative responsibility of project as well as governance teams

Conclusion These ten principles presented in this short paper are the result of our experience over the past ten years.During the initial years, we perceived them as good practices and later found that these are essential for every distributed agile project. As a result we arrived at these ten principles. In our industry, several large enterprises have started adopting agile in geographically distributed projects. This trend is going to continue over the next decade. Considering the ten principles discussed in this paper and adhering to them will certainly benefit geographically distributed teams.