From anarchy to sustainable development: SCRUM in less than ideal conditions.
Add to calendarIs it possible to SCRUM the development of a large software system with contributing teams spread out over three cities, five partners, six sites, and a six hour time difference? It started with vague and ambitious objectives and was built on bleeding edge technologies (grails, flex). By all rights we should have fallen flat on our faces. But a year after its dubious beginning, our project continues. Join us as we present the good, the bad and the ugly of distributed team projects.
The session will take the form of a talk designed to integrate audience experiences into the presentation to provide a sometimes contrasting, sometime rallying perspective on our own experiences. We’ll share the lessons we’ve learned in
Facilitating open communication
Continually seeking to improve team productivity in scrum ceremonies: scaling scrum from 6 to 20 people across distances
Managing code complexity and maintaining architectural cohesion
The follies of delaying deployment in a production-like environment with real data
Scrum without end-user feedback?
Living with Artistic Design-driven development, where Artistic Design has changed 3 times.
Breaking the reporting cycle and getting individual teams commitments with the daily Scrum (of Scrum)
Maintaining a common project vision
Not knowing when you’ve reached the target: dealing with “the wow effect”, while hoping to be the first on the market.
Introducing new personnel and teams late in the project.
- A perspective on the collaborative tools that worked and those that didn’t.
- A new appreciation for the challenges faced when dealing with distributed teams and the strategies we tried to overcome them.
- Our recommandations of complimentary presentations to attend at Agile 2009 — discover what is important to know before starting a similar projects
- And ultimately, to realize that distributed projects can be fulfilling and rewarding success stories!