Get short, timely messages from David Laribee.

Twitter is a rich source of instantly updated information. It's easy to stay updated on an incredibly wide variety of topics. Join today and follow @laribee.

Get updates via SMS by texting follow laribee to 40404 in the United States
Codes for other countries

Two-way (sending and receiving) short codes:
Country Code For customers of
Australia
  • 0198089488 Telstra
Canada
  • 21212 (any)
United Kingdom
  • 86444 Vodafone, Orange, 3, O2
Indonesia
  • 89887 AXIS, 3, Telkomsel
Ireland
  • 51210 O2
India
  • 53000 Bharti Airtel
Jordan
  • 90903 Zain
New Zealand
  • 8987 Vodafone, Telecom NZ
United States
  • 40404 (any)

laribee

  1. @whitebarrel the typical story format (in order to... as a... i want...), estimate, owner about 10 hours ago via web in reply to whitebarrel
  2. @jgboghos @johnboghoscares? ;) about 10 hours ago via web in reply to jgboghos
  3. @ShawnWildermuth Discovery should blend a little more into delivery - continuous discovery and continuous delivery. about 10 hours ago via web in reply to ShawnWildermuth
  4. @ShawnWildermuth yes. and iterations are meant to give you that course correction feedback cycle. about 10 hours ago via web in reply to ShawnWildermuth
  5. @drusellers I'll write a short (probably equally incoherent) blog post. about 10 hours ago via web in reply to drusellers
  6. i've seen that work well. rendering knowledge into action, that is. about 10 hours ago via web
  7. or perhaps an initial iteration would yield solution-oriented stories that are up front estimable. about 10 hours ago via web
  8. the problem then comes around estimation. i think that design-to-schedule would work fine here... about 10 hours ago via web
  9. @orangy I wonder if certain dev teams (creative ones) wouldn't do better with problem context / research going into innovation work. about 10 hours ago via web in reply to orangy
  10. @drusellers I'm mainly wondering where, in a lot of places, where the "I want <feature>" part comes from. Does anyone know? about 10 hours ago via web in reply to drusellers
  11. starting to think if we're really focused on understanding problems and innovating, user stories (as they exist) aren't the best solution. about 10 hours ago via web
  12. @jeremydmiller So here's some context: I'm dealing with a system where the only trusted source is the DB. No objects in memory. 1:48 PM Sep 2nd via web in reply to jeremydmiller
  13. @Ben_Hall oh, you'll know it when you see it. 1:44 PM Sep 2nd via web in reply to Ben_Hall
  14. protip: make sure your architecture allows you to introduce caching in sensible locations. 1:28 PM Sep 2nd via web
  15. Looking for feedback on a conference track idea (http://laribee.com/creative-analogs)... Please RT! 8:18 AM Sep 2nd via web
  16. Blogged: "Creative Analogs" ~ http://laribee.com/creative-analogs 8:17 AM Sep 2nd via David Laribee
  17. @jeffdeville that's too bad. the iterative/incremental thing really does require buy in all the way. 12:08 PM Aug 30th via web in reply to jeffdeville
  18. @jeffdeville when are they asking you to do this extra stuff? if it's way out in the future, it's likely you have big bang planning going on 10:30 AM Aug 30th via web in reply to jeffdeville
  19. Blogged: "Yestimation" ~ http://laribee.com/yestimation 9:14 AM Aug 30th via WP to Twitter