Your SlideShare is downloading. ×
Managing distributed teams_webinar_v2_october_2011
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Managing distributed teams_webinar_v2_october_2011


Published on

Slides for Managing Distributed Teams with Assembla webinar, October 2011 - draft

Slides for Managing Distributed Teams with Assembla webinar, October 2011 - draft

Published in: Technology, Business

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Managing Distributed Teams Using Assembla Presenter: Andy Singleton, Founder and CEO The webinar will begin shortly. You may call into the phone number provided or simply listen through your computer speakers
  • 2. Topics
    • Setting up a cloud-based dev environment
    • Coordinate team activities: online scrum & chat
    • Share a daily build
    • Manage all tasks on tickets
    • Use tickets to organize iterations (views)
    • Fix release dates (let features move)
    • Use a developer activity stream
    • (Time permitting) Six things to skip
    • Q&A
    © Copyright Assembla 2011
  • 3. Set up and manage a cloud-based development environment
    • Required tools
      • Shared code repository
      • Ticketing or issue management
      • Standup
      • Chat
    • Setting up Assembla
      • Getting started wiki page
      • Space landing page and ticket landing page
      • Ticket fields and workflows – Walk through the settings page of Tickets
      • Build system
    © Copyright Assembla 2011
  • 4. Coordinate team activities across time zones
    • Stand-Up Reports
      • See what everyone is working on so you can guide each team member to work on what is most important that day
      • See needs and obstacles and resolve them
      • Reduce chat time
      • Breakout example
    © Copyright Assembla 2011
  • 5. Coordinate team activities across time zones
    • Scrum Chat
      • Fixed time
      • 10-15 minute scrum or standup
      • No conference calls
    © Copyright Assembla 2011
  • 6. Share a daily build
    • One version of the software everyone can see and test
    • Or go all the way to continuous integration
    • Requires good automated build scripts
      • Hard, but worth the investment
    • Obstacle: some people don’t want to show work until the task is complete
      • Divide the work into short stages
      • Every day find problems and ask for fixes
    © Copyright Assembla 2011
  • 7. Share a daily build
    • Use workspace templates (pre-packaged build environments) and set up workflows
    © Copyright Assembla 2011
  • 8. Manage all tasks on tickets
    • Everything goes on tickets
      • Feature requests, bugs, tasks, comments, requirements, designs, documents, tests, etc., etc.
    • Stop communicating requests one-on-one
      • Phone email chat
      • Don’t be the hub
    © Copyright Assembla 2011
  • 9. Use tickets to organize iterations
    • Plan milestones/iterations/sprints
    • Track status
    • Drill down on team members, high priority tasks, workflow stages, etc.
    • Have you tried all Assembla ticket views?
      • Ticket list view
      • Cardwall view
      • Agile planner view
    © Copyright Assembla 2011
  • 10. Use tickets to organize iterations © Copyright Assembla 2011 Ticket list Cardwall Agile planner
  • 11. Manage a global organization
    • Take full advantage of filters/reports
      • Exception management
      • User reports
    © Copyright Assembla 2011
  • 12. Fix release dates
    • Fix release dates
    • Remove features that can’t be completed and stabilize the remaining features
    • Benefits:
      • Users see regular improvements
      • Fix bugs with each release (keeps quality high)
      • Establish credibility – You WILL deliver on time
    • Tip: Don’t let nervous bosses overload releases
    • Tip: Don’t send every release to every user group
    © Copyright Assembla 2011
  • 13. Use a developer activity stream
    • Same idea as FaceBook
    • Team members come up to speed across time zones
    • Everyone can react quickly to issues
    • Managers see progress
    © Copyright Assembla 2011
  • 14. Six things to skip
    • Productivity increases when you do less work to get the same results
    • Travel
    • Architect in Advance (ALAP controversy)
    • Adding project managers
    • Conference calls
    • Hiring interviews
    • Estimates
    © Copyright Assembla 2011
  • 15. Questions? Type your questions in the Q&A module on the right of your screen
  • 16. Contact Us [email_address]