Harnessing Agile Development In Distributed Environment Dusan K Part

Dusan Kocurek Software Lab Manager, Ness Software Product Labs
Part I by co-presenter Dave West not includedSenior Analyst, Forrester Research
Harnessing the Power of Agile Development in a Distributed EnvironmentPart II
1

Most software development is done by distributed teams today
Why distributed development? Cost savings, availability, skills
2
Challenges

3
A Mix Of Agile And…
Reality?
Mix of methodologies
Adaptation
is key to success

Why non-Agile
Customer is conservative
“Waterfall is good, proven, management style”
High risk project – no will and courage to implement Agile
Customer’s clients want non-Agile PM
Why Agile
Current methods aren’t working – late releases, over-budget, team burnout
Agile is a proven method
Agile encourages team communication
Customer is late adopter, but willing to consider if Agile can help
4
Reasons for more methodologies

5
Offshore and AdaptationClient not using Agile method
Adapt
Planning
Tracking
Delivery
Communication
Tools
Offshore team
Customer’s
team

6
Offshore and AdaptationClient not using Agile method
Scrum
Adapt
Planning
Tracking
Delivery
Communication
Tools
Many times Agile
leads to change
Offshore team
Customer’s
team

Offshore and AdaptationClientusing Agile method
Adapt
Ceremonies
Scrum Style
Roles
Communication
Tools
Hyper-productive
teams
Offshore team
Customer’s
team
7

8
“What are the challenges of geographically distributed development?”
Team’s
Communication
Tools

Scrum of Scrum
Integrated Scrum
9
Styles – Isolated SCRUM
Coding
QA
Design

10
Styles –SCRUM of SCRUM
D+C+QA
D+C+QA
D+C+QA

11
Styles –Integrated SCRUM
Team B: D+C+Q
Team A: D+C+Q
Team C: D+C+Q

Ness Technologies, UK client
3 locations (United Kingdom, Czech Republic, Slovak Republic)
One Product Owner based in UK
2 ScrumMasters in UK and Slovakia
Teams are distributed
Developers at every location
QA in UK, Slovakia
12
Scrum of Scrum style

SprintForce company
5 locations (Denmark, Romania, Ukraine, Uganda, Philippines)
One Product Owner per product
3 ScrumMasters located at the same office in Romania
Teams are multi-disciplined and multi-located
Technical experts in different countries help teams to deliver
www.sprintforce.com
13
Integrated Scrum style

Roles and structure
Cross functional teams
ScrumMasters at all locations
Scrum of Scrum
Product owners
14
Teams

Face to face
When?
Where?
15
Communication

Meet online
IM, Email, Webcam
Common project space
When
Daily
At a regular time
16
Communication [Stay tuned]

Time zones
Find core time
Representatives
17
Time Zones

Agile and tools?
Physical board is the best!
I’m using Excel!
Is all that enough?
18
Tools

19
Radiators

20
Virtual Task Boards

21
PM
Microsoft Excel
Microsoft Project
VersionOne
ScrumDesk
GreenHopper
Bug trackers
BugZilla
Jira
Mantis
Mercury Quality Center
Document and collaboration
Microsoft SharePoint
Wiki
Mind map utilities
Screen sharing
Online meeting tools
Version control systems
CSV
Subversion
Visual Source Safe
Development support
Cruise Control
Team Central
Other tools

22
Focus on…

Communication is a must
Visibility for everyone
Time zones could be advantage
23
Summary

Q+A
24
Question and Answer Session

Thank you for attending today’s webinar. Both speakers can be reached via email so that you can follow up with additional questions. Here is their contact information:
Dusan KocurekSoftware Lab Manager, Ness Software Product Labs
dusan.kocurek@ness.com
25
Thank you for attending!

Harnessing Agile Development In Distributed Environment Dusan K Part

by Dusan Kocurek on Aug 07, 2009

Accessibility

Categories

Tags

Upload Details

Usage Rights

1 Embed 5

Statistics

Harnessing Agile Development In Distributed Environment Dusan K Part — Presentation Transcript