Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Methods used in scaling Scrum: An experience report


Published on

While the business context of a project decidedly influences the success of any software development project, project execution matters as well.

Scrum, like most agile software development methods, is originally intended for the use of a small team. Larger companies in the software development field have a need to scale these methods to larger environments, often a global operation.

This presentation describes a two-year project involving over a hundred people across the globe directly. The perspective is that of practical methods that helped F-Secure to keep the project moving against many difficulties and uncertainties. Organizational observations are also included.

These areas will be touched:
- Organizing the project staff into teams and projectmanagement
- Large joint planning sessions
- Backlog management and tooling
- Communication about backlog
- Project governance bodies
- Project steering and communication
- Pushing responsibility down
- Integration
- Test automation status radiators
- Testing
- Bug handling process
- Beta releases
- Development environments
- Dealing with disruptions, setbacks, direction changes and surprises

This session will be most valuable to those who are working with real software development projects and want experienced advice on methods that have been successfully applied in global commercial context. The audience is expected to be familiar with Scrum and those who know Scrum well will benefit the most. As the topic is very wide not much time will be used on each area. The focus will be determined by the interest of the audience. Interactive discussion will be encouraged during the session.

Published in: Technology
  • Be the first to comment

Methods used in scaling Scrum: An experience report

  1. 1. F-Secure Corporation, Towo Toivola, director of R&D Global MethodsThis presentation is dedicated to the survivors of the IS11 project.
  2. 2. So, what to concentrate on?Clear, frequent, systematic, high-qualityhuman-to-human communication about• Backlog • Actions• Situation • Quality• Expectations • ImprovementsMake sure you place reality and estimates way above needs and wishes of the organization.Maintain quality in your software and your operations, it is cheaper and faster than not doing it.