cross-post from bbv Blog

This is a list of actions that Scrum Masters at bbv Software Services AG have applied successfully in their teams to improve performance (= how much gets done in an amount of time). Please note that these actions were created to respond to specific problems found in real world projects. They may not be applicable in general in any situation.

I’d be happy to read your experiences and feedback in the comments section.

Agile, Methodology Agile, scrum, ScrumMaster, team

This is a presentation I hold in 2010 for bbv Software Services AG. It shows how my team lives Scrum.

I’d be glad to see your feedback in the comments section…

Agile, Methodology Agile, scrum

Einführung

Scrum, ein agiles Prozess-Framework, wird von Scrum Fanatikern gerne in allen Lebenssituationen appliziert. Daher liegt es nahe, dass Scrum auch auf die Ehe (besonders, beim Lebensbund zweier Scrum Practitioners) Anwendung findet.

Dieses Standardwerk zeigt wie Scrum auf eine Ehe appliziert werden kann.

Agile Fun, scrum

This is the slide deck of my LAS 2010 presentation: From user stories to architecture.

Agile, Architecture, Methodology, Presentation Agile, Architecture, Design, Presentation, scrum

These are the slides and comments of a presentation I held for bbv Software services AG.

The presentation is about how we get quality into our code.

Buzzwords: Fokus, frequent measurements, strong team, clean code, pair programming, test driven development, acceptance tests, continuous integration, collective code ownership, team learning.

Urs Enzler
Senior Software Architect
bbv Software Services AG

urs.enzler _at_ bbv.ch  (replace _at_ with @)
www.bbv.ch

Copyright © 2010 bbv Software Services AG

How to get quality into source code – that’s the question I’ll try to answer in this document.

You’ll see what we do at bbv Software Services to get code that is built with inherent quality and why it is important to think about quality throughout the whole development process.

Agile, Presentation, Test Driven Development Acceptance Tests, Agile, Collective Code Ownership, Continuous Integration, Development, Pair Programming, Presentation, Refactoring, scrum, TDD, Team Learning, Test Driven Development, Testing, Unit Test

This is the slide deck of a presentation I gave for bbv Software Services AG at two events in 2009 along with some comments .

If you are interested in seeing this presentation live (either in German or English) then please contact me.

In an agile project, the architecture has to evolve together with the requirements and the code. In this presentation, I’ll show you our agile architecture lifecycle.

Agile, Architecture, Methodology Agile, Architecture, scrum

Living and breathing Scrum means for a team being self organized. My experience in different Scrum projects tells me that this is not always an easy task to grasp. Experienced Agile teams are self organized when it comes to maintain the code base or gathering information for user stories from the product owner. But what happens when soft skills are involved?

Agile, Methodology scrum, Self Organized, team

When I talk with fellow developers new to Scrum, I often hear a fundamental misunderstanding about Sprints. These colleagues  are normally used to Waterfall or RUP methodologies. As a consequence, they think of Sprints as very short repetitions of the following phases: requirements (planning meeting), design, implementation, test (sprint review as acceptance).

And this is completely wrong!

Let me tell you why.

Agile, Methodology scrum, Waterfall

Recently, I was asked by a colleague why I like Scrum. I didn’t have a good answer at hand immediately, and since then the question bugged me. Therefore it’s time to give you my top ten now:

1. Team Spirit
2. Continuum Of Work Pressure
3. Don’t Assume, Show
4. Team Knowledge Over Experts
5. Control Is Good, Presentation Is Better
6. Continuous Improvement
7. True Incremental Development
8. No One-Man Shows
9. ROI Is The King
10. Fun

Agile, Methodology Agile, Continuous Improvement, Planning, ROI, scrum, team, Velocity

Peter Stevens from scrum-breakfast.com blogged today a really interesting article about an adapted scrum process for IT support. As Peter Stevens describes in his post on of his attendees in his workshop was the leader of IT Support for the EE Department of the ETH Zurich. They where facing the problem that their support group had to deal with daily business and they had to successfully compete medium term projects but their daily business was consuming all their time.

The answer to their problem was not strictly speaking Scrum… I suggest you read the interesting article from Peter!

Towards Agile Support

http://www.scrum-breakfast.com/2009/05/towards-agile-support.html

Methodology peter stevens, scrum, scrum-breakfast, Support