Where Agile Business Meets Agile Development DSDM Offshore Steve Messenger Patrick Vermeij.

Slides:



Advertisements
Similar presentations
State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
Advertisements

An Intro to Professionalizing Procurement & Strategic Sourcing
<<replace with Customer Logo>>
Global Software Development Main issue:  distance matters.
Agile 101.
Agile development By Sam Chamberlain. First a bit of history..
1 LaCrosse PMI Chapter Meeting A discussion about the Introduction of PM within your business 4/20/2011 Jim Strong Mayo Clinic DLMP PMO Director.
© ThoughtWorks, 2008 Improving Productivity and Quality With Agile Patrick Kua.
Agile
Dynamic Systems Development Method (DSDM)
Presented by Vijaya L Uppala 09/30/2003
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Project Execution.
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
AGILE DELIVERY FACILITATION Agile Project Manager should see his stakeholders as kids and aim to help them be successful in their respective goals, each.
What is Business Analysis Planning & Monitoring?
Global Project Management April 23, 2008 Challenges and Opportunities By Wafa Bunney.
Managing Offshore Software Development Projects Presented by Orlando Moreno Phone: web:
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
Software Project Management
 Since in 1994, DSDM, the Dinamic Systems Development Method, has gradually become the number one framework for rapid application development (RAD) in.
Tuesday, June 8 th, Agile Development-Successful Delivery & Implementing Across the Enterprise.
Alcatel-Lucent CDC Workshop, Coaching & Knowledge Transfer Project Management.
West Impl 1© The Delos Partnership 2005 Integrated Enterprise Leadership Implementation.
MGT 461 Lecture # 19 Project Initiation Phase (I OF II)
James Aiello PricewaterhouseCoopers Africa Utility Week 06 International Good Practice in Procurement.
Industrial Software Project Management Some views on project managing industrial and business software projects.
Setting up an Internal Audit Program By
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Agile Assessment Gadi Lifshitz, Ayelet Kroskin, Barak Yagour, Yael Dubinsky.
1 Outsourcing and OffShoring January 2004 Sandy Senti.
Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Paul Hardiman and Rob Brown SMMT IF Planning and organising an audit.
K.Ingram 1 Sept 2007 Agile Software Development. K.Ingram 2 Sept 2007 Contents Agile Software Development: 1.What is it? 2.Agile’s Values, Principles,
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Project Management Workshop James Small. Goals Understand the nature of projects Understand why Project Management is important Get an idea of the key.
Information System Project Management Lecture Five
Network design Topic 1 Business goals. Agenda Network life cycle Network design process Business goals Scope Constraints.
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
Project Management Project Integration Management Minder Chen, Ph.D. CSU Channel Islands
University of Sunderland ENGM91 Unit 4 ENGM91 Project Planning Unit 4.
Agile. Processes Waterfall Traditional With prototyping Sprial Agile Dynamic Systems Development Method (DSDM) Scrum Crystal eXtreme Programming (XP)
DSDM Dynamic Systems Development Method. DSDM Methodology Goals On time Within budget Of desired quality.
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
Illuminating Britelite’s Internal Services for Success Strategy for Process Improvement.
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
Agile 101. Feasibility Study SDLC – What is it? Systems Development Life Cycle: The most commonly used, and generally accepted, project management approach..
Global Software Development Main issue:  distance matters ©2008 John Wiley & Sons Ltd. vliet.
Challenges in Agile Unclear project scope, multiple iterations, minimal documentation, early and frequent testing needs and active stakeholder involvement.
1 1 Effective Administration of Commercial Contracts Breakout Session # Session D06 Name: Holly Walker, CPCM Corporate Learning Solutions and Contract.
APMG-International Webinar Integrating Agile into PRINCE2® Thursday 19 December 2013 / 13:00 GMT Presented by Melanie Franklin,
1 Requirements Engineering for Agile Methods Lecture # 41.
Delivery Method: Online Duration: 180 Days Scrum Developer Certified (SDC™)  Participants will become familiar with the concepts, advantages, and challenges.
1 Home Care Support Outcome Based Specification Workshop 26 th November 2009.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Office 365 Security Assessment Workshop
Scrum Project Transition Case Study
Multinational / Multicultural Teams in Offshore IT Projects
Description of Revision
Guidance notes for Project Manager
Atern v2 – Summary of changes from v1
Portfolio, Programme and Project
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

Where Agile Business Meets Agile Development DSDM Offshore Steve Messenger Patrick Vermeij

Where Agile Business Meets Agile Development 2 Agenda  Introduction of the speakers  The need for DSDM Offshore  Offshore Team  Communication is Key  Offshore Risks  The DSDM Phases Applied to Offshore  Summary

Where Agile Business Meets Agile Development 3 What is Offshore?  “A project whereby a development process, which is the responsibility of one organisation, is performed by another organisation at a separate location.”

Where Agile Business Meets Agile Development 4 Why Go Offshore?  Offshore can provide:  Large pool of resource  Lower rates  Extended working hours  Leading to:  Faster, cheaper development  Giving your business  Agile response to business changes  Competitive Edge

Where Agile Business Meets Agile Development 5 Frequently Encountered Issues  Communication  Cultural differences cause different perceptions  Understanding and trust  Logistical  Legal and Contractual Issues  Hidden Costs  More Management  Costs of travel  IT infrastructure and data communication  Product delivery  Late  Poor Quality

Where Agile Business Meets Agile Development 6 Offshore is Easy! Create Specification Choose VendorThrow Over the Wall Receive Perfect System

Where Agile Business Meets Agile Development 7 Offshore is Easy? No User Involvement Poor Collaboration And Cooperation Systems That don’t meet Requirements

Where Agile Business Meets Agile Development 8 Offshore Issues With DSDM  People  Impossible to locate everyone in the same place  Communication and understanding  Cultural differences a barrier to DSDM principles  How do we ensure a one-team environment?  Organizational  Onshore / offshore have different objectives  Ensuring collaboration in a contractual relationship

Where Agile Business Meets Agile Development 9 DSDM Offshore  Amendment of DSDM targeted at offshore development  Highlights:  There is one team! (no offshore and onshore teams)  Specialized and extended roles  Communication is key  Predefined risk list  Extended product quality criteria  Additions to the DSDM process

Where Agile Business Meets Agile Development 10 Agenda  Introduction of the speakers  The need for DSDM Offshore  Offshore Team  Communication is Key  Offshore Risks  The DSDM Phases Applied to Offshore  Summary

Where Agile Business Meets Agile Development 11 Empowerment  Is there a culture of empowerment?  Bring developers to you  Contractual clauses  Confidence is basis for empowerment  Vendor has knowledge of business area  Use same offshore vendor  Appropriate decision making  Business team members make business decisions  Technical team members make technical decisions

Where Agile Business Meets Agile Development 12 There Is One Team! Remove isolation Ambassadors Face to face meetings

Where Agile Business Meets Agile Development 13 There Is One Team! New Roles New Responsibilities for Existing Roles

Where Agile Business Meets Agile Development 14 New Roles  Ambassador Developer  Representative of offshore developers at onshore  Senior Offshore Supplier  Counterpart of the executive sponsor  Offshore Technical Coordinator  Liaising with technical coordinator  Test Coordinator  Coordinator of testing, which takes place at several locations

Where Agile Business Meets Agile Development 15 Amended Roles  Technical Coordinator  Work with onshore and offshore (face to face) to ensure a system that meets the non-functional requirements  Coordinate usage of environments at all locations  Executive Sponsor  Ensure a collaborative and co-operative contract in which changes can be reversed  Resolve escalated issues between offshore and onshore  Others  Be aware of cultural differences

Where Agile Business Meets Agile Development 16 Agenda  Introduction of the speakers  The need for DSDM Offshore  Offshore Team  Communication is Key  Offshore Risks  The DSDM Phases Applied to Offshore  Summary

Where Agile Business Meets Agile Development 17 Communication  Offshore development differs from traditional development in:  Physical distance  Different time zones  Communication is the Achilles’ Heel of offshore development  Rely more on results, less on gut feeling  Tools capture results Yes ? 不是!

Where Agile Business Meets Agile Development 18 Means of Communication  Face to face meetings  Tele-conferencing facilities (telephone and video)  Desktop collaboration tools  Electronic project rooms  Project assets available to the whole team (all locations)  Configuration management tools  Requirements management  Test and defect management

Where Agile Business Meets Agile Development 19 Ensuring Product Quality  Ambassadors MUST travel to tell the story  The WHY and the WHAT from the horse’s mouth  Involve Offshore at earliest possible opportunity (creation of PRL)  Frequent product deliveries, reviews and testing  Mechanism is needed for developers and testers to interact  Desktop collaboration tool for demonstration of defects  Issue management tool to keep track of issue status

Where Agile Business Meets Agile Development 20 Communication per Product (1/3) Best forms of communication for products: ProductType of Communication Business Area Definition  Face to face workshops  Electronic project rooms System Area Definition  Face to face meetings  Tele conferencing facilities Development Plan  Face to face meetings Prioritized Requirements List  Face to face meetings

Where Agile Business Meets Agile Development 21 Communication per Product (2/3)  Best forms of communication for products: ProductType of Communication Functional Model  Face to face workshops (several)  Desktop collaboration tools

Where Agile Business Meets Agile Development 22 Supporting Communication (1/2)  Best forms of supporting communication: ProductType of Communication Project Deliverables  Configuration management tool  Electronic project rooms Project Management  Face to face meetings  Tele conferencing facilities  Electronic tools for documents / issues management.

Where Agile Business Meets Agile Development 23 Supporting Communication (2/2)  Best forms of supporting communication: ProductType of Communication Quality Management  Prototype review sessions – tele/video with desktop collaboration tool.  Test records etc. in EP-room Workshops  Face to face on priority issues.  Tele / Video

Where Agile Business Meets Agile Development 24 Agenda  Introduction of the speakers  The need for DSDM Offshore  Offshore Team  Communication is Key  Offshore Risks  The DSDM Phases Applied to Offshore  Summary

Where Agile Business Meets Agile Development 25 Risks (1/3)  Cultural differences  Could lead to misunderstanding and delays  Mitigate by:  analysis of differences  awareness and acceptance  Daily business risks  Things can go wrong at several locations  Mitigate by:  Face to face meetings with key people at both locations  Communicate, communicate and communicate

Where Agile Business Meets Agile Development 26 Risks (2/3)  Multiple-locations risks  Projects at multiple locations are more complex (e.g. time differences)  Mitigate by:  Face to face meetings at all locations  Create and stick to a communication plan  Planning and control risks  Planning and or budgets are not met  Mitigate by:  Allowing offshore overhead into the timebox plan  Continuous communication of status of project  Prompt escalation of issues

Where Agile Business Meets Agile Development 27 Risks (3/3)  Partnership risks  One of the parties does not meet the requirements of the other  Mitigate by:  Clear communication  Close and open monitoring  Contractual risks  The contract is not co-operative, collaborative and/or does not allow changes to be reversible  Mitigate by:  Contracts negotiators must follow DSDM principles

Where Agile Business Meets Agile Development 28 Agenda  The need for DSDM Offshore  The 9 Principles Applied to Offshore  Communication is Key  Offshore Roles  Offshore Risks  The DSDM Phases Applied to Offshore

Where Agile Business Meets Agile Development 29 Phases – Feasibility Study

Where Agile Business Meets Agile Development 30 Phases – Business Study

Where Agile Business Meets Agile Development 31 Phases – Functional Model Iteration

Where Agile Business Meets Agile Development 32 Design and Build Iteration

Where Agile Business Meets Agile Development 33 Phases – Implementation  Is onsite phase. No offshore-specific aspects.

Where Agile Business Meets Agile Development 34 Summary