• all the other bells and whistles will be along in a little while...

    The devs need to know which bells and whistles are wanted in order to do that, and they need to be able to gauge how much each bell / whistle is wanted to determine which ones to add. If improvements are going to be made, the way to get them isn't for everybody to sit quietly and wait for the devs to figure out what they might be on their own without any input from users, innit. That's how software works.

  • @bothwell - We should have specific sessions set up, so that we can help the devs create code on a nimble, active and quick basis.

    We could call these groups "huddles", which would mean everyone stands up in them too

    There could be a huddle boss, maybe?

    Ooh - how about a board that has post-it notes on to show what stage each feature is in, and a graph showing progress?

    This is an awesome idea of yours! We should call it Bothwell's Nimble Job Getting Done Method (BoNJoGeDoM for short).

About