Socialtext Distributed Agile
Download as PPT, PDF12 likes5,870 views
The document discusses Socialtext's approach to distributed agile development, emphasizing the transition from traditional waterfall methods to agile practices for improved collaboration and efficiency. Key elements include two-week iterations, cross-functional teamwork, and a transparent culture that encourages continuous learning and adaptation. Challenges such as teamwork dynamics, design collaboration, and testing processes are also highlighted, along with strategies for resolution and ongoing improvements.
Socialtext Distributed Agile
- 1. Socialtext Distributed Agile Ross Mayfield Adina Levin Tracy Ruggles
- 2. Socialtext Distributed Agile Distributed agile is a trend At BarCamp and D-Camp a few years ago Last year at PCamp
- 4. Socialtext Distributed Agile Why agile? Personal experience with waterfall 300 page prds 24 month product cycles product obsolete when released dev and pm mutual incomprehension Agile sounds like better way Small-a agile, not big-A agile Lots of war stories requiring beer
- 5. Socialtext Distributed Agile The basics 2 week iterations Hosted service and SAAS appliance Hosted every 2 weeks, appliance every month
- 6. Anatomy of a story Anatomy of a story
- 7. Anatomy of a Story
- 8. Anatomy of a Story
- 9. Anatomy of a Story
- 10. Anatomy of a Story Cross-functional discussion Real time teamwork
- 11. Anatomy of a story family How to do planning with agile Leadership team direction for year and quarter Stories fit into projects. Occasional focused planning a project level Occasional f2f and focus
- 12. Real Live Customers ” Customer feedback blog"
- 14. Challenges - Teamwork “ The swarm" Started with multiple processes Changed to one process, one dev group Emotional challenges Can't fight and then play foosball, get beer Logistics Need to be sensitive to timezone differences or we'll miss people
- 15. Socialtext Agile Culture Learning... retrospect every iteration, what went well, what didn't, what can be improved JFDI.. if you have an idea for improvement, take the ball Transparency - code, design, planning, customer feedback, better in the open
- 16. Outakes
- 17. Challenges - Design Harder to "whiteboard" ideas together voip and screen or vnc communicate that it's a brainstorming meeting and not tactical story definition Design patterns could do more to make it easier to add additional stories with design variants Usability testing Architecture Review stories in families Appoint architecture steward
- 18. Socialtext Agile Development No code ownership (but some expertise) Source code control - cvs > subversion > git Iteration capacity based on on "yesterday's weather" Pair programming with voip and screen Standup 3x per week - what are you working on, where do you need help
- 19. Socialtext Agile QA Release testing is a considered combination of automated and human testing with the goal of preventing unhappy experiences for our users. Story test cover expected behavior & corner cases As stories are finished, QA validates and raises concerns during the iteration. Browser based testing with selenium UI tests run 24/7 just like unit tests. Automated tests are maintained and always exercise a majority of the functions exposed to the user. Exploratory testing Lightweight performance analysis