Try This


1.

At your next team meeting, discuss this: What, exactly, is our biggest problem? And what, exactly, are we going to do about it?

2.

Talk about set-based design at a team meeting. Find out if anyone has any examples of when they used such an approach while developing software. (In a group of eight, there will usually be someone who has. If not, try for an experience of set-based design outside of software.) Have the person describe the experience, the rationale, and whether or not it was a good idea.

3.

What is your team's practice regarding refactoring? Before you add any new features, do you first change the design to simplify it, without making any feature changes, and test the new design to be sure nothing has changed? Do you refactor to simplify immediately after getting a new feature working?

4.

Take one document that your team is expected to produce and at a team meeting work to figure out how it can be fit into the A3 report format. Does the new format adequately summarize all of the information in the old document? The next time the document is distributed, attach the A3 version on the front. After doing this a few timesif it is practicaltry distributing just the A3 report and not the longer document. What happens?

5.

If something small goes wrong on a regular basis, do the people annoyed by the problem have a way to fix it? Does your team have a regular meeting for discussing these annoying problems, reflecting on how things are done and what could be done better? How often is it held? Does the team work together using a disciplined problem-solving approach to do something about the issues that arise? Does it work on one problem at a time?




Implementing Lean Software Development. From Concept to Cash
Implementing Lean Software Development: From Concept to Cash
ISBN: 0321437381
EAN: 2147483647
Year: 2006
Pages: 89

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net