3 ms·
Post-its on a whiteboard.
by nostrademons 17y ago
Post-its on a whiteboard.
- dtran 17y agoYou probably meant this as a joke, but I have a friend who is hyper-organized with all of her to-dos on a whiteboard... different sections are different things/different priority levels. Maybe we will hack together a Wii whiteboard Johnny Chung Lee style and use virtual post-its! (http://johnnylee.net/projects/wii/ http://johnnylee.net/projects/wii/)
- m0nty 17y agoYou probably meant that as a joke too, but I think a virtual whiteboard with Post-Its would be a great product. Colour-coded notes to indicate priority, clustering by physical location on the screen, larger text sizes for very-urgent-do-it-today tasks. You could draw lines on the whiteboard to show the relationship between notes, could have the ability to roll back to previous days to track history, attach files to Post-Its, etc, etc. I currently do something like this using index cards on a pinboard, and it works really well.
- gaustin 17y agoI think it could be a great product too. Anyone working on it and want help? Anyone want to work on it with me?
- dtran 17y agoI don't have any more time for side projects, but lots of students in one of my HCI classes have built software to do stuff like this in a relatively short timespan (~4 weeks): http://www.youtube.com/watch?v=5s5EvhHy7eQ http://www.youtube.com/watch?v=5s5EvhHy7eQ
- projectileboy 17y agostixy.com is exactly that. The usability is pretty good.
- vog 17y agoYour advice is great, but it is too simple and too obvious to be used by any modern team. It is old-fashioned, without any noise and hype around it. Fortunately, the guys at http://73primenumbers.com/ http://73primenumbers.com/ started a campaign to add the missing buzz.
- nostrademons 17y agoMy tech lead from two projects ago used post-its on a whiteboard, and one of the teams I work closely with still does. For search options, we used a 2D-grid, where the vertical axis was the component and the horizontal access was the state of done-ness (unassigned, being worked on, in code review, finished). If you have a small, colocated team, this is basically ideal. There's low overhead, and the overhead consists of physically taking off a post-it and sticking it in the next column, which feels very satisfying. At a glance, you can see how done the project is - lots of post-its on the left means you have a while to go, lots of post-its on the right mean you're almost done. If you have components that need lots more attention, they'll show up as stragglers on the grid, and then you can either allocate more resources or cut the feature as appropriate. (In our project, that was usually self-allocation, because we didn't have particular engineers assigned to particular components, and each engineer was familiar with a few different components). If a lot of tasks get stuck in the code review stage, you know that it's time to lean on the code reviewers a bit.