Re: [teampractices] [Discussion] Term for always prepping for the next thing

2015-10-01 Thread Kevin Smith
I'm not ad adherent of any zero inbox plans, although I try to keep my inbox under one page. My main advice would be: Experiment, and find out what works best for you. Experiment, inspect, adapt, and iterate. Don't be afraid to try something that might end up being worse rather than better. As an

Re: [teampractices] [Discussion] Term for always prepping for the next thing

2015-09-30 Thread Max Binder
I think it is good to frame time as a budget, because it is a finite resource. Then the mantra becomes "I need to spend less" rather than "I need more resources." Hofstadter's Law (a favorite) relates better to our previous point on measuring capacity. Estimating task size and complexity is a key

Re: [teampractices] [Discussion] Term for always prepping for the next thing

2015-09-30 Thread S Page
On Wed, Sep 9, 2015 at 10:32 AM, Kevin Smith wrote: > I'm imagining someone whose "todo" queue is growing linearly while their > "done" pile eternally remains empty. It seems odd that new higher-priority > work would be coming in so fast that not only can the old work not get done > first, but t

Re: [teampractices] [Discussion] Term for always prepping for the next thing

2015-09-15 Thread Kevin Smith
Your 4 bullets are good, but I think "reduce batch (task) size" deserves a bullet as well, or at least should be featured prominently on another bullet. Kevin Smith Agile Coach, Wikimedia Foundation On Mon, Sep 14, 2015 at 5:34 PM, Max Binder wrote: > Thanks all. I distilled the best practic

Re: [teampractices] [Discussion] Term for always prepping for the next thing

2015-09-14 Thread Max Binder
Thanks all. I distilled the best practices for "sensation X" to: - Set priorities, execute in order, interrupt only if necessary - Stop starting, and start finishing - Forecast capacity, and use forecasting accuracy as a barometer for iteration length/batch size - Create MVPs, and s

Re: [teampractices] [Discussion] Term for always prepping for the next thing

2015-09-09 Thread Kevin Smith
Hopefully this depiction is an exaggeration of what is really happening, because right now I'm imagining someone whose "todo" queue is growing linearly while their "done" pile eternally remains empty. It seems odd that new higher-priority work would be coming in so fast that not only can the old wo

Re: [teampractices] [Discussion] Term for always prepping for the next thing

2015-09-09 Thread Joel Aufrecht
How much overlap is there between your sensation X and "future tripping "? *--Joel Aufrecht* Team Practices Group Wikimedia Foundation On Mon, Sep 7, 2015 at 9:10 PM, Rob Lanphier wrote: > On Mon, Sep 7, 2015 at 1:27 PM, Max Bi

Re: [teampractices] [Discussion] Term for always prepping for the next thing

2015-09-07 Thread Rob Lanphier
On Mon, Sep 7, 2015 at 1:27 PM, Max Binder wrote: > Everything is set at an equally high priority, with each upcoming task > usurping the priority of the current task. There are no low priority moments > because stress of the upcoming tasks is the motivator to do the work. I also > do believe that

Re: [teampractices] [Discussion] Term for always prepping for the next thing

2015-09-07 Thread Max Binder
Thanks, Rob. It sounds to me like this particular case is a lack of good prioritization, and tasks that are different enough from one another to feel like context-switching even when doing one thing at at time. Everything is set at an equally high priority, with each upcoming task usurping the pri

Re: [teampractices] [Discussion] Term for always prepping for the next thing

2015-09-05 Thread Rob Lanphier
On Fri, Sep 4, 2015 at 1:27 PM, Max Binder wrote: > The future tasks matter, but so do the current tasks, and yet in order to > execute the next task, a sacrifice is made to current productivity. > I think the term you may be looking for is "analysis paralysis

Re: [teampractices] [Discussion] Term for always prepping for the next thing

2015-09-04 Thread Max Binder
The future tasks matter, but so do the current tasks, and yet in order to execute the next task, a sacrifice is made to current productivity. On Fri, Sep 4, 2015 at 1:25 PM, Max Binder wrote: > Clarification: > > When I get into "busy mode" I always focus and give priority to the future >> task.

Re: [teampractices] [Discussion] Term for always prepping for the next thing

2015-09-04 Thread Max Binder
Clarification: When I get into "busy mode" I always focus and give priority to the future > task. It's about getting through the whole day as opposed to focusing on > the task at hand. So not exactly context switching, and not exactly tunnel > vision--something in between both. > > It's the feelin

Re: [teampractices] [Discussion] Term for always prepping for the next thing

2015-09-04 Thread Kevin Smith
It doesn't sound the same as Endless Deathmarch, but I don't feel like I really understand the question yet. Can you elaborate on "always prepping for the next thing" aka "future blindness"? Kevin Smith Agile Coach, Wikimedia Foundation On Thu, Sep 3, 2015 at 4:43 PM, Max Binder wrote: > A q

[teampractices] [Discussion] Term for always prepping for the next thing

2015-09-03 Thread Max Binder
A question came to me from a friend, and I thought I'd pose it here for discussion: Question for a scrum master: I know you call "multi-tasking" the far more > accurate "context-switching," but do you have a real term for what I can > only call "future blindness"? It isn't exactly tunnel vision th