Andy Singleton, Assembla <ul><li>Mission: Accelerate Software Development </li></ul><ul><li>23 people in 7 countries </li>...
Input 1) The Web 2.0 Challenge <ul><li>You have </li></ul><ul><ul><li>$200K </li></ul></ul><ul><ul><li>A few wireframe dra...
Input 2) Open Source <ul><li>You have a bunch of people who have never met each other making great software, with complex ...
Input 3) Agile and Scrum <ul><li>You have a short and defined schedule </li></ul><ul><li>Lesson: Release on timed cycles <...
Six Things to Do <ul><li>Release on a fixed schedule </li></ul><ul><li>Share a daily or continuous build </li></ul><ul><li...
Six Things to Skip <ul><li>Travel </li></ul><ul><li>Architecture in Advance </li></ul><ul><li>Adding project managers </li...
While I am at it… More things to avoid <ul><li>Doing anything with a fixed specification </li></ul><ul><li>Using synchrono...
Other controversial claims <ul><li>Number one developer qualification: Can build from scratch </li></ul><ul><li>Mythical M...
Key success factors <ul><li>Habit and Discipline.  The team learns to stay on the schedule, every day, every iteration </l...
The challenge again <ul><li>You have $200K, A few wireframe drawings, No incumbent staff, Four months.  You’ve seen my pro...
Upcoming SlideShare
Loading in …5
×

Notes on Distributed Agile for Agile Boston 7/29/09

1,242 views
1,166 views

Published on

Notes on Assembla's Distributed Agile methodology for Agile Boston 7/29/09

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,242
On SlideShare
0
From Embeds
0
Number of Embeds
418
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Notes on Distributed Agile for Agile Boston 7/29/09

  1. 1. Andy Singleton, Assembla <ul><li>Mission: Accelerate Software Development </li></ul><ul><li>23 people in 7 countries </li></ul><ul><li>Consulting and contract product development services, mostly for startups </li></ul><ul><li>Assembla.com online service, used by thousands of distributed agile teams </li></ul><ul><li>New: Private Assembla </li></ul>
  2. 2. Input 1) The Web 2.0 Challenge <ul><li>You have </li></ul><ul><ul><li>$200K </li></ul></ul><ul><ul><li>A few wireframe drawings </li></ul></ul><ul><ul><li>No incumbent staff </li></ul></ul><ul><ul><li>Four months </li></ul></ul><ul><li>Lesson: Release early, release often </li></ul><ul><li>Starting point: Roadmap. List features in priority order, and work in that order. </li></ul>
  3. 3. Input 2) Open Source <ul><li>You have a bunch of people who have never met each other making great software, with complex organization evolved over the last 15 years </li></ul><ul><li>Lessons: Many lessons for commercial teams </li></ul><ul><li>Starting point: Use competitive trials to find good people and suppliers </li></ul>
  4. 4. Input 3) Agile and Scrum <ul><li>You have a short and defined schedule </li></ul><ul><li>Lesson: Release on timed cycles </li></ul><ul><li>Starting point: Infrastructure for daily build and weekly release process </li></ul>
  5. 5. Six Things to Do <ul><li>Release on a fixed schedule </li></ul><ul><li>Share a daily or continuous build </li></ul><ul><li>Write it down in tickets </li></ul><ul><li>Daily report and chat </li></ul><ul><li>Watch a team activity stream </li></ul><ul><li>Recruit good people </li></ul>
  6. 6. Six Things to Skip <ul><li>Travel </li></ul><ul><li>Architecture in Advance </li></ul><ul><li>Adding project managers </li></ul><ul><li>Conference Calls </li></ul><ul><li>Interviews </li></ul><ul><li>Estimating </li></ul>
  7. 7. While I am at it… More things to avoid <ul><li>Doing anything with a fixed specification </li></ul><ul><li>Using synchronous collaboration (phone, video, screen sharing) to manage fast-moving situations </li></ul><ul><li>Dividing work geographically. SINGLE GLOBAL TEAM! </li></ul>
  8. 8. Other controversial claims <ul><li>Number one developer qualification: Can build from scratch </li></ul><ul><li>Mythical Man Month is wrong </li></ul><ul><li>Pile on developers at the beginning of the project </li></ul><ul><li>Assembla.com users should pay … something </li></ul>
  9. 9. Key success factors <ul><li>Habit and Discipline. The team learns to stay on the schedule, every day, every iteration </li></ul><ul><li>Raw Talent </li></ul><ul><li>Management confidence </li></ul>
  10. 10. The challenge again <ul><li>You have $200K, A few wireframe drawings, No incumbent staff, Four months. You’ve seen my proposal for Web 2.0 + Open Source + Agile </li></ul><ul><li>Who will compete against us with a different approach? </li></ul><ul><li>Invasion of the Enterprise? </li></ul><ul><li>Related to Cloud Computing? </li></ul>

×