I'm not sure what you're saying here, but I disagree. In general agile processes are defined a certain way because they work. If you take only pieces, you're not following the known-working process so your expected results are indeterminant. If you're filling binders with documentation, you're probably not doing any form of agile.

That may be true if you're the only one working on it. However some of the benefits of TDD include arriving at an early consensus on design details and allowing different roles to work in parallel. Once you've defined the tests, everyone knows exactly how it needs to work and you can have your developers go ahead at the same time as your qe at the sae time as your doc at the same time as your consumers. You've flattened out the pipeline.

By your reasoning without TDD, yes, your stage in the pipeline is quicker, but the pipeline is much longer and more serial.

My group is still having that argument, but people seem to misunderestand that agile requires no documentation. Agile does not assume any documentation. Starting from zero, YOU define what is necessary for your project then implement it. The result should be significantly less and significantly more effective documentation than the traditional approach of starting with a heavy doc requirement regardless of project needs. However it does assume you have competent people willing and able to make the right decisions.

I always think that is the fundamental difference. Waterfall assumes everyone may be lazy, incompetent or malicious and tries to keep everyone in line by predefining everything and including lots of checks and balances, and command and control. Agile assumes you have competent professionals so you need to get out of their way, empower the right person to make the right decision, and help the team work together.

Yes, that's clearly not.

Some of the other fundamental principles of scrum are:

Transparency - In a traditional process the costs of change are often hidden, but with scrum, the costs should be more immediately apparent. Traditional process draws a line to limit change but scrum welcomes change while providing better feedback on the cost to allow a better decision.

Accountability - In scrum you have one person, the product owner, who is responsible (has the authority AND the accountability) for deciding on the balance between changes and costs.

In a case like this, the arguments about not following scrum come down to: either you screwed up the process so you don't have the transparency or you screwed up the product owner role so he either didn't have the authority to make a decision or wasn't held accountable for it (not that I've seen a PO with either of those).

Anyone else see an x-rated activity between The Gambia and Senegal?

I don't know if Apple handles this, but NetAlert kept application signatures. You could choose to allow once or allow always, and you'd be alerted if it wanted a new port or if the application changed in any way.

Same with my Mother-in-law, but then I looked it up ... apparently back when they used these sheets of compressed dried wood pulp and printed with handheld sticks containing ink or carbon black, LOL did indeed mean "Lots of Love". Just ask wikipedia.

Not just any media extender, but how about a dlna client? Get a network drive that serves dlna (many possibilities), then you just need to throw your pictures, video and music out on your network and you should be able to use the xbox to see/hear them through your entertainment center.

Supposedly this works: ever since I discovered my network drive serves dlna, I've been considering getting an xbox as a good, cheap dlna client, but I haven't actually tried this yet.

For those who want to run a media server: my network drive only draws 20 watts and serves most of the same features except for DVR functionality.