Agile Business Conference Template

Download Report

Transcript Agile Business Conference Template

DSDM Offshore
Steve Messenger
Patrick Vermeij
Where Agile Business Meets Agile Development
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
2
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
3
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
4
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
5
Offshore is Easy!
Create
Specification
Choose Vendor
Throw Over the Wall
Receive Perfect System
Where Agile Business Meets Agile Development
6
Offshore is Easy?
No User Involvement
Poor Collaboration
And Cooperation
Systems That don’t
meet Requirements
Where Agile Business Meets Agile Development
7
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
8
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
9
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
10
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
11
There Is One Team!
DSDMO
Offshore Team
Structure
Executive
Sponsor
Project
Manager
Visionary
Technical
Co-Ordinator
Ambassador
Developer
Team
Leader
Developer
Ambassador
User
•Remove isolation
•Ambassadors
•Face to face meetings
Key
On/Off
shore
Ambassador
User
Test Coordinator
Development
Tester
Developer
Onshore
Scribe
Advisor
User
Advisor
User
Where Agile Business Meets Agile Development
Offshore
New Offshore Role
12
There Is One Team!
DSDMO
Offshore Team
Structure
Executive
Sponsor
Project
Manager
Visionary
New Roles
Technical
Co-Ordinator
Ambassador
Developer
Team
Leader
Developer
Ambassador
User
Development
Tester
On/Off
shore
Ambassador
User
Test Coordinator
Key
Developer
Onshore
Scribe
Advisor
User
Advisor
User
New Responsibilities for Existing Roles
Where Agile Business Meets Agile Development
Offshore
New Offshore Role
13
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
14
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
15
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
16
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
17
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
18
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
19
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
24
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
25
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
26
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
27
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
28
Phases – Feasibility Study
Where Agile Business Meets Agile Development
29
Phases – Business Study
Where Agile Business Meets Agile Development
30
Phases – Functional Model Iteration
Where Agile Business Meets Agile Development
31
Design and Build Iteration
Where Agile Business Meets Agile Development
32
Phases – Implementation
 Is onsite phase. No offshore-specific aspects.
Where Agile Business Meets Agile Development
33
Summary
Where Agile Business Meets Agile Development
34