For the last few weeks I read a lot on how to improve my team's Scrum environment and on how to create a more Agily workspace. I might also add here that we Scrumming for 9 months (on each month we change something else, improving, destroying, thinking again, etc...).

Collecting and reading great posts, I will share them with you:

• Cork Task Boards
• Scrum Room = Fun Room
• Oren Ellenbogen on Continuous Integration
• Chris - talking about Done

Those few Samples cause me think about how can I upgrade our environment, And I'll Explain my changes:

Programmer environment - better productivity
Upgrading the Programmer environment to a more productive workplace - Thanks to Yossi, we have two screens for each programmer. Now everyone can code on once and test on the other screen Or maybe can code on one and read the Design Requirements on the other, etc.

Cork board 
I've found out that most a the programmers do not really understand what everyone telling at the daily-standup-meeting, which cause them to dislike the meeting or maybe even forget the importance of this meeting.
The Cork-Board will help us to see (visualization) and understand(movement-at-realtime) the actual point of the team in the current sprint.

Done
People are different, This is a good fact, and we should understand it.
You need every one in your team understand what the Team want from him only his best. But when we can't explain ourself, someone can understand things not properly as we meant them, this will cause anger and disappointment.
Create a short document explaining what is Done - so everyone will be coordinated.
(Some types for Tasks that need to be Done: Writing Story Cards, Updating documentation, Coding, Bug-fixing. each one of those need to be fully Done)

Testing (not TDD yet)
Logic:
For me, one step before TDD-ing, the team must have a solid tests and a good understanding about the difference between integration, functionality and unit.
Framework:
After understanding the logic, you must have a solid framework for testing and a daily notification about your operations, so you and everyone else could see that you are working as we expect you to work.
So we create the Continuous-Integration workspace using the CC-Tray so everyone could know whether their friends are helping them or preventing from them to work properly.
The Imporatnce of testing:
After having this simple understanding, and this framework, everyone will finally understand that his testing methods are important.
And everyone will understand that unit-testing are part of the Done statement.
Moving to TDD-ing:
From here I believe that we could move toward TDD-ing.

Daily Scrum Standards
Right on time meeting, Every one standing, Only one people talking, Exactly 15 minutes, clarifications questions only.
Selecting the leading watch - everyone has its own watch, the team should understand which-watch is the one to set the scrum time. (I should buy an Egg-Watch, I am still looking for a funny one).

Setting Punishments (Penalties)
They should be a funny penalties, so everyone will like it (everyone but the one who doing it, of course).
like bringing the milk, or making coffee for everyone.
I see those punishments for a few fields:
a) destroying the build(errors and warnings)
b) checking-in tests that fail
c) decreasing the Code-Coverage,
d) late for Daily-Scrum

Here are some pictures from the new environment

                                            My Agile Workspace 

                                           Two Scrum Boards

 
                           The new Cork-Board (still empty, till the next sprint)

Things To Be Done, {Till the end of the year}:

1. Find a funny (noisy) Egg-Watch
2. Create a field_penalty_list
3. Moving toward a TDD-ing sessions
4. Decide about the best period for the sprint (today we decide about two weeks, I am start thinking this one is too short)
5. Find the Product-Owner (This one may sounds funny, but we still did not find him\her, no one can take this position for now)

Scrum is not only the things you are saying and doing, it is more about what you (and your team) are feeling.
Scrum should be part of everyone in the team, so it will succeed.