SessId004

name: Solving Problems in Introducing Change (Such as Introducing Technical Reviews)

designers: Esther and Jerry

max number of participants: no max

min number of participants: 5

optimum number: 5 to 50

duration of session: 3 hours

configuration of room: flexible, chairs only

There's no mystery about technical reviews being one of the simplest, most straightforward, and inexpensive ways to increase the quality of software. The mystery, however, is why organizations and individuals should have so much trouble increasing their effectiveness by adopting reviews. This session will explore some of the more frequent "stoppers" that hijack the effort to adopt technical reviews, and also other ways to increase the quality of software - using technical review experience as the baseline.

People who are trying to do technical reviews (or other initiatives) should come and contribute to and learn from this session, as we surface the problems, then share solutions.

What would you like to know about this session? What can you suggest for it?

I think it would be helpful to have someone take notes and capture the wisdom of the group... any volunteers to take notes for this session? EstherDerby

I'm thinking of changing the emphasis of this session slightly, to include introducing tools in general. We'd start with a focus on technical reviews, then expand the focus and see what general principles apply to the introduction of any tool - Jerry

(James) When I was in control of a test tools team at Apple, I made us do reviews. They were certainly useful, but our problem was how to schedule them. Just wanting to do something and knowing how to do it aren't enough. With reviews, you also have to get people to review specific things at specific times, while they are also doing work of their own.

It's hard enough to schedule meetings, as it is. How do organizations stomach the many review meetings that go along with a robust review strategy?

(Jerry) James' question is typical of the kind of topic we'll bring up at this session.

(Esther) Here's the current design:

*form groups around the tools and processes that participants are introducing

*within groups identify problems and obstacles

*distribute the problems among the groups

*each group will report out on their solution-ideas

There's bound to be lots of experience and creativity in the room!

(Nynke) You really intend to distribute the problems among the groups?
Hhhmmm ...

(Jerry) Yes, we certainly do. We hope to establish an environment where it's safe to do so, but if you have some problem that's too delicate for public consumption, bring it with you and we'll have some private consulting based on the lessons learned in this session.

Return to NewSessionDescriptions

Updated: Wednesday, September 27, 2000