Embed Size (px)
DESCRIPTION
Slides for Managing Distributed Teams with Assembla webinar in October 2011 - Draft
Citation preview
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
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 20112
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 20113
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 20114
Coordinate team activities across time zones
•Scrum Chat
–Fixed time
–10-15 minute scrum or standup
–No conference calls
©Copyright Assembla 20115
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 20116
Share a daily build
•Use workspace templates (pre-packaged build environments) and set up workflows
©Copyright Assembla 20117
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 20118
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 20119
Use tickets to organize iterations
©Copyright Assembla 201110
Ticket list
Cardwall
Agile planner
Manage a global organization
•Take full advantage of filters/reports–Exception management–User reports
©Copyright Assembla 201111
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 201112
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 201113
Six things to skip
Productivity increases when you do less work to get the same results
1.Travel
2.Architect in Advance (ALAP controversy)
3.Adding project managers
4.Conference calls
5.Hiring interviews
6.Estimates
©Copyright Assembla 201114
Questions?Type your questions in the Q&A module
on the right of your screen
