[logfromblammo]

Code up an "instant stand-up" team status web page, such that everyone on the team can see at a glance what everyone else is doing, what they just finished, and whether they have any blocks. Update your status once per day.

Congratulations, you have now saved 10 minutes per day for everyone in the office. Oops, now they have to come up with some other reason for everyone to be physically present at 9 AM sharp.

"Flexible hours" have always been BS at almost every company I have worked for.

[dragonwriter]

> Code up an "instant stand-up" team status web page, such that everyone on the team can see at a glance what everyone else is doing, what they just finished, and whether they have any blocks. Update your status once per day.

Basically, kanban, sure; but you've also missed what is (IMO) the main values provided by the "Daily Scrum", and the reason something like it is useful even in systems that use better methods for communicating status of progress items:

1. Coordination and conflict resolution on next tasks, and 2. Early and rapid identification (and, ideally, resolution or escalation) of barriers/issues.

(That's not to say that there aren't ways other than a daily in-person meeting that could be proposed to meet these goals, just that a status board doesn't replace the functionality of the Daily Scrum.)

[logfromblammo]

I haven't had many positive experiences with daily stand-ups, so I'm heavily biased against them.

For the record, I didn't like doing oral reports in front of the entire class in school, either.