Everytime a company does this, they throw away 90% of the value of
Scrum, while telling themselves that they've only lost about 10% of
This is such a big issue it is specifically referenced in the core
Scrum texts - and yet people still do it. Sigh.
> blogging - basically had a page with "things I did", "things I will
> do", and "roadblocks"... we tried to do this weekly, it didn't always
> work out, but it can be somewhat useful - I could see it being more
> useful if it was more like a social network so you could actually see
> updates from your colleagues on roadblocks in realtime.
We did this over IM, every day, before I learnt about Scrum. It worked
very well that way. Of course, people in different timezones would
drop theirs into the DailyScrum IM window when they woke up. It was an
excellent way both to announce their online presence / availability
for work issues, and to contribute to the dailyscrum (-style meeting,
since - as noted - we weren't aware of scrum at the time)
> you know of? Just seems like it could be useful... I don't necessarily
> want blogs, but tweets would be nice ;)
I think a lot of the things that people try to do with blogs could be
better replaced by private tweets.
However, even tweets throw away a lot of value and ease of use
(browsing archives, length of messages, etc), so I'd personally start
with IM and master that first, and then be cautious about branching
You can do all that with any modern IM system too.
But in addition you get:
- much better GUI
- much higher acceptance rate with users
- much better protocols (e.g. skype with built-in 256-bit encryption)
- much richer value-adds (again e.g. skype you can switch to voice or
video at any time, and then drop back to text - although I've never
done a multi-person video call on skype, never quite needed *that*)