4 ms·
I'm going to ignore the high levels of content marketing here and share my favorite trick: minimize work-in-process. At my last startup, we limited WIP (that i
by wpietri 10y ago
I'm going to ignore the high levels of content marketing here and share my favorite trick: minimize work-in-process.
At my last startup, we limited WIP (that is, the number of open tasks) to be smaller than the number of developers. You can see a picture of our task board here:
http://williampietri.com/writing/2015/the-big-board/#toc4 http://williampietri.com/writing/2015/the-big-board/#toc4
This was great. It really forced us to focus and collaborate. It helped management to accept the true capacity of the team, preventing them from flooding us with requests. It also let us get things done at a lively pace, creating a continuous sense of progress that built trust.
I've visited so many teams that have a dozen things going on at once, which leaves everybody scattered. Especially when people then sneak in another dozen "unofficial" requests because they have learned not to trust the main work queue. And then another dozen urgent bugs, most of which happened because of the chaotic work environment, because nobody has enough time to focus and do something right.
In some: if you want to get more done, do fewer things. And then fewer things still. It seems crazy, but it works.
- drvdevd 10y agoSounds rather brilliant actually and a good rule of thumb.
- Animats 10y agoSomeone is from an industrial environment. Work in process, in the form of partially complete goods, is a curse of badly organized factories. It's more visible in a factory environment; you have to walk around the stuff on the shop floor. It also costs real money - you've bought the parts, but can't sell the product yet. One form of limiting work in progress is this: if you want reliable software, insist that no new features go in until all the reported bugs have been fixed. A weaker form of this is to have a master branch, which gets bug fixes only, and a development branch, into which new features go. Merging can happen only when there are no open issues in the master branch. This is the opposite of "shit early, shit often" development.
- gertef 10y agoJoel Test, #5: Do you fix bugs before writing new code? http://www.joelonsoftware.com/articles/fog0000000043.html http://www.joelonsoftware.com/articles/fog0000000043.html 0 hits for "shit early, shit often" development.: https://www.google.com/?#q=shit+early+shit+often+development https://www.google.com/?#q=shit+early+shit+often+development Were you mocking "ship early, ship often"?https://en.wikipedia.org/wiki/Release_early,_release_often https://en.wikipedia.org/wiki/Release_early,_release_often That's about when you ship, not what you work on. It's not the opposite of fixing bugs.
- marcosdumay 10y agoNever heard the phrase, but it is what bad managers mean when they say "ship early, ship often".
- TeMPOraL 10y ago"Shit early, shit often" is what usually happens with the "ship early, ship often" in real life. See also, "move fast and break things" as implemented in a typical startup. But then again, business incentives are usually against software that works well and is useful - what matters is whether software works just enough to look sellable.
- zaidf 10y ago"If you want reliable software, insist that no new features go in until all the reported bugs have been fixed." That is a massive oversimplification. In fact, a key job of a product manager is differentiating between critical bugs that must be fixed, bugs that should be fixed but can wait and bugs that don't need fixing in the near term. Otherwise, for any mature piece of software (particular enterprise software), you will be fixing almost an infinite number of bugs that add little value at the expense of critical features that make the needle move. This is one of the biggest lessons I got when working on a decade old enterprise software. At first, I was shocked that our VP of Product put certain bugs in the "won't fix any time soon" category. But now, I see how much more value we'be been able to drive because we decided to ignore certain category of bugs for new feature or other feature improvements. Insisting on blindly prioritizing bug fixes over any thing else does nothing more than satisfy our engineering ego. Don't assume it automatically making the product more useful for the user or driving more value to the company or its customers
- aantix 10y agoSpot on. The best team I ever worked with used Pivotal Tracker. When you delivered a story, you picked the next story off the top of the backlog. No cherry picking of stories. We paired on all but the simplest stories. You were constantly learning new tricks from other devs and since you could only take from the top, you quickly got a taste of most of the major components of the system. In short, you could actually take a fucking vacation because there's no longer the situation of being the only designated "backend guy". Everyone had some backend experience.
- dasmoth 10y agoI can see the merits, but it also seems a rather joyless environment -- just do what Pivotal tells you. Was there any feeling of autonomy?
- andor 10y ago(I work at Pivotal) Tracker is only a communication medium. In such an environment you don't "do what Pivotal tells you", you do what you decided to do as a team, because as a team you prioritized stories in the backlog. That means, as a team, you have pretty high autonomy. You also have autonomy when working on stories, because they should only tell you what and why to do something, not how. If have to compromise a lot to take team decisions, your team is probably not aligned very much. Do you share the same goals with everybody else? For most people around me, joy comes from being productive, helping your team to make good products at a fast pace, and from interacting with people the whole day.
- TeMPOraL 10y agoSounds like the worry I used to have for a long time about todo lists and calendars in personal life. I eventually realized that those tools are not meant to be your boss - they're only means of storing what you figured out when you had more time to focus on something. You can disobey them at any time, freely, but if you find yourself constantly disagreeing with your own todo list, it suggests you need to work on what you put in there in the first place. They're meant to optimize, not take away your autonomy. (Shared todo lists, as it's what all those project planning / issue tracking tools essentially boil down to, is a little different thing because other people put stuff in it too, but the principle is still the same - it's not there to limit your autonomy, it's there to improve your focus and free up your memory.)
- lockedoutwhoops 10y agoVery insightful and well stated. Doing fewer things is a great way to define focus. Too many tasks in progress seems to lead to cognitive drain, perhaps due to all the context switching.