Nightly builds are an excellent best practice. Most teams don’t do this.

“I agree with you, but most people think of Scrum when they think of Agile.” it is prevalent. Why is so?

I can see it is tempting to try to handle soft-development as car-manufacturing,but really, how wrong and far from the truth that is 🙁

The agile manifesto is good enough for me.

I will look into Kanbanand, but what I’m really looking for is to get out of the office work 🙁

it is too much stress and frustration for me combined.

I do believe the internal politics and even weak talent can be overcome if you have a few key technical leaders with good people skills that can break down tasks and get the team working together right, but I am an optimist. 🙂

I agree with you, but most people think of Scrum when they think of Agile.
See my link about Kanbanand, to see how I think software should be developed.

in fact SCRUM brings a common-denominator and facilitates mediocrity as far tech goes!

1) this is not “Build Master” but CI , continuous integration

2) what do you mean? do you imply moving code out of 1 single central source control? all the NOT tested should go there too, what the point of CI otherwise :)) ?

3) too much juggling

4) lock and checkout ? you lost me completely

“That ensures that everyone has the daily approved-good-code”

have CI with test and you have it implicitly true

“completely eliminates having to rebuild the project throughout the day.” how the heck do i test? good that i compile only part of the project, but what if I need change elsewhere?