Search

Harnessing Agile Development In Distributed Environment Dusan K Part

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

1 comments

Comments 1 - 1 of 1 previous next Post a comment

Post a comment
Embed Video
Edit your comment Cancel

Notes on slide 1

Scrum at locationScrum of Scrum on global level

Teams are distributed and every team has team members in different locationsFor experienced teams understanding cultural differences

Multi-discipline teamsLet the team to manage workDO NOT ASSIGN TASKSHead to Integrated Scrum, work should be distributed across the globeForget technologies. Forget components. You are implementing stories. Multi-discipline teams are able to develop stories, component focus is step back and will not allow you to create multi-discipline teams. Scrum master at every location help to remove obstacles which are possible to remove locally Scrum of Scrum enable to remove high level obstacles, keep all places informed about the progress and the work completed Product Owners – is it good to have more product owners? At least one at every place?

Why - emotional level of communication, body language- Get to know each other, experience, persona, cultureWhenInception phaseProduct planningImportant events (release, demo, crunch time)Regular meetings is bestWhere- At least once in every location

HowHave your buddy defined at other placeUse IM for critical communication use email for less critical, for proposals, operationIf call, then prefer video communicationGive every team member resources required to communicateKeep everybody on the same level of project detail’s knowledge, create common project space, share knowledge, use tweets, rss feeds, newslettersWhenBe in touch on daily baseHave short regular daily all team meetingScrum Masters have to support communication, keep it short, help to find participants

Not a problem if time difference is low (1-2 hours)Define core time for meetings – not to stay very late, not to be very soon in an office for the meetingChallenge if time difference is 9 or more hours -> define representativesRepresentative is working in different time zone, many times customized -> Mars Pathfinder, Spirit, Opportunity project - time in sol (Mars day)

http://www.scrumdesk.com

Information RadiatorsVirtual boards One trackerContinuous IntegrationOne Version Control System

1 Favorite

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

  1. 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
  2. Most software development is done by distributed teams today
    Why distributed development? Cost savings, availability, skills
    2
    Challenges
  3. 3
    A Mix Of Agile And…
    Reality?
    Mix of methodologies
    Adaptation
    is key to success
  4. 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. 5
    Offshore and AdaptationClient not using Agile method
    Adapt
    • Planning
    • Tracking
    • Delivery
    • Communication
    • Tools
    Offshore team
    Customer’s
    team
  6. 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
  7. Offshore and AdaptationClientusing Agile method
    Adapt
    • Ceremonies
    • Scrum Style
    • Roles
    • Communication
    • Tools
    Hyper-productive
    teams
    Offshore team
    Customer’s
    team
    7
  8. 8
    “What are the challenges of geographically distributed development?”
    Team’s
    Communication
    Tools
  9. Scrum of Scrum
    Integrated Scrum
    9
    Styles – Isolated SCRUM
    Coding
    QA
    Design
  10. 10
    Styles –SCRUM of SCRUM
    D+C+QA
    D+C+QA
    D+C+QA
  11. 11
    Styles –Integrated SCRUM
    Team B: D+C+Q
    Team A: D+C+Q
    Team C: D+C+Q
  12. 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
  13. 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
  14. Roles and structure
    Cross functional teams
    ScrumMasters at all locations
    Scrum of Scrum
    Product owners
    14
    Teams
  15. Face to face
    When?
    Where?
    15
    Communication
  16. Meet online
    IM, Email, Webcam
    Common project space
    When
    Daily
    At a regular time
    16
    Communication [Stay tuned]
  17. Time zones
    Find core time
    Representatives
    17
    Time Zones
  18. Agile and tools?
    Physical board is the best!
    I’m using Excel!
    Is all that enough?
    18
    Tools
  19. 19
    Radiators
  20. 20
    Virtual Task Boards
  21. 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. 22
    Focus on…
  23. Communication is a must
    Visibility for everyone
    Time zones could be advantage
    23
    Summary
  24. Q+A
    24
    Question and Answer Session
  25. 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!
SlideShare Zeitgeist 2009

+ Dusan KocurekDusan Kocurek Nominate

custom

818 views, 1 favs, 0 embeds more stats

Harnessing the Power of Agile Development in a Dist more

More info about this document

© All Rights Reserved

Go to text version

  • Total Views 818
    • 818 on SlideShare
    • 0 from embeds
  • Comments 1
  • Favorites 1
  • Downloads 10
Most viewed embeds

more

All embeds

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories

Tags

more
-->
Search
RSS Feed
What's new?

© 2009 SlideShare Inc. All Rights Reserved