As software penetrates every single aspect of the human world, large enterprises are conceiving extremely large and complex software projects. With software development going global, many organizations are practicing distributed development in various forms today. There are not many large projects left which are being developed without outsourcing or off shoring. While this is a trend in the industry, we also see more and more organizations are realizing heavy-weight processes are too rigid and risky. Some claim they simply don’t work. The good news is, over the last decade, organizations world-wide are trying light weight methods like Agile on large, mission-critical, distributed projects.
The Large Scale and Distributed stage is dedicated to sharing insights from large scale, distributed, complex projects. We invite practitioners and evangelists to shed light on real-world challenges and share their success and horror stories. We hope to provide pearls of wisdom for teams considering or already in large, distributed set ups. This stage is not limited to just distributed projects; we believe a lot of this thinking applies to large collocated projects as well. This stage will stress the practical applications and implications of tweaking Agile values and practices to suit distributed and/or large-scale projects.
Reading and hearing about agile practices is one thing, but actually doing it is completely different. This workshop puts you to work in an agile fashion, applying agile development practices. During this workshop, we're going to take a problem and iteratively develop the solution, using test-driven development, pair programming, retrospectives, pair rotation, and other agile management & development techniques.
|Day and Time:||Monday, 09 August 2010, 09:00 - 12:30|
What is a stew? A stew is made from various ingredients you have around, left overs, new ingredients that go together well, and others that are filling but need lots of sauce. The enterprise software market is made up of products that are a stew of software on many legacy platforms that have evolved over a long period by many hands. Taking an enterprise software product to Agile methods is a challenge. In a uniquely European context, this presentation will draw from the ongoing agile adoption in a multi-location multi-team enterprise product with 460 staff in 4 countries and 5 locations.
|Presenter(s):||Robin Dymond , Jurgen De Smet|
|Day and Time:||Tuesday, 10 August 2010, 11:00 - 12:00|
Distributed development challenges the effectiveness of retrospectives.We designed and trialled a lightweight analytical approach (CLPP-Retro) that engages distributed teams and generates actionable solutions. We discuss the feedback from a team that employed CLPP-Retro over 12 iterations. They find that it identifies solutions that are not merely corrective; it facilitates agile adoption, identifies critical gaps in the organization, improves estimation, decreases repetitive problems, and provides a voice for the engineer. We also discuss lessons learned during deployment. We'll be conducting in-room retrospective sessions simulating a distributed environment. BRING YOUR LAPTOPS!
|Day and Time:||Tuesday, 10 August 2010, 13:30 - 15:00|
For a distributed team it is even more important to pay 'Continuous attention to technical excellence and good design' as the Agile Manifesto requests. Yet, how to implement the typical agile development practices like pair programming or collective code ownership in a distributed setting? Moreover are there any differences or things to watch out for when applying “easier” practices like unit testing or refactoring? In this session I want to focus on the impact and application of agile development practices in distributed teams and how such a team can ensure its technical excellence.
|Day and Time:||Tuesday, 10 August 2010, 15:30 - 17:00|
Dean Leffingwell describes how rapidly advancing agile methods are being successfully applied to enterprise-class software development. He describes emerging practices including: lean requirements practices that scale to the full needs of the enterprise, intentionally emergent architectures, achieving strategic alignment and product development flow with the Agile Release Train, a kanban system for re-architecting large-scale systems, and strategies for agile portfolio management.
|Day and Time:||Wednesday, 11 August 2010, 09:00 - 10:30|
The author and Jeff Sutherland previously showed (at Agile2008,2009) Scrum teams using XP practices achieved distributed velocity equal to local velocity with multiple distributed teams. This was shown under extreme timezones and at large scale development. The authors have formalized the principles & practices that are the foundation for hyperproductive fully distributed Scrum. This framework has been published as free e-book (SEE ATTACHMENT) and is the subject of this presentation. New experiences and figures on recent projects will be shared to illustrate the pitfalls and success points.
|Day and Time:||Wednesday, 11 August 2010, 11:00 - 12:00|
Experience design is expanding as product development teams disperse. No longer will experience design occur in one open, physical room. Instead, distributed teams will design as well as develop...and they need techniques, guidelines and tools to do so. Development has already become a multishore activity. Yet how do we ensure that distributed teams also incorporate experience design as an integrate part of their approach and outcome? This session provides principles and guidelines to enable teams to design in a collaborative yet distributed fashion.
|Day and Time:||Wednesday, 11 August 2010, 13:30 - 15:00|
Have you successfully implemented Scrum on your team, and are hungry to expand? Are you finding the pain of scaling your Scrum deployment too much to handle? Is the Scrum of Scrums concept not working out the way you thought it would? Has someone told you that you need to roll out Scrum to a team of 300+ developers? Have you had success with scaling Scrum, and want to share what you've learned with others? If so, join us for this interactive session where we explore three different experiences scaling Scrum in large organizations.
|Presenter(s):||Melanie Paquette , Mike Osmond|
|Day and Time:||Wednesday, 11 August 2010, 15:30 - 17:00|
What do four global enterprises, each with 40+ Scrum teams of 5-9 people have in common? For the most part they are no different than a project with just one Scrum team. This session will show the size-dependent problems that arose in these projects and how the practices of Multi-stage Continuous Integration, small story size, collocation, cross functional teams, one piece flow, and unit tests helped to address them. Even if you don’t have many Scrum teams today, learning about the growing pains will help you fine tune what you are doing today and prepare for growth tomorrow.
|Day and Time:||Thursday, 12 August 2010, 09:00 - 10:30|
Offshore is never easy, but more often than not, the secret saboteur isn't someone in far off timezone, it's you and your team. This working session will examine offshore work from the perspective of an offshore team lead who deals with onshore resources that often enable the failure of their offshore teams. The workshop will address issues commonly faced by teams working with offshore and what onshore teams can do to foster better results. Towards the second half of the session the discussion will be opened up for participants to introduce issues and develop solutions as a group.
|Presenter(s):||Dave Prior , Thushara Wijewardena|
|Day and Time:||Thursday, 12 August 2010, 11:00 - 12:00|
When agile methods are adopted in enterprise organizations there are often members or teams which are not collocated, or work is segregated among distributed teams. While this is often a challenge for things like technical practices (for example, pair programming) it has an even greater impact on the psychology of the team in how they interact and learn. In this session Cory will demonstrate tools and practices he's coached. These tools and practices cover three high-level categories: Development Practices, Product Management / Customer Interaction and Reflection and Introspection.
|Day and Time:||Thursday, 12 August 2010, 13:30 - 15:00|
Most Agile practices target teams of 7±2. A Scrum of Scrums addresses teams of (7±2)², or 25 to 81. What do you do when you run a project on the scale of 7³ (~350) or 7^4 ( ~2400) contributors? It’s no longer a Scrum of Scrums of Scrums of Scrums. I’ve been in the role of product owner for extended teams of 400=2400 at Microsoft. Building on my Agile 2009 talk, Agile in the Very Large, I'll discuss techniques for envisioning, planning, executing, and releasing product in an organization of this scale, while maintaining empowerment and agile at the individual team scale of 7±2.
|Day and Time:||Thursday, 12 August 2010, 15:30 - 17:00|
Producer: Joshua Kerievsky
Co-Producer: Nicola Douramebis