Every year they seem to continue to introduce (via neglect/decisions/priorities) more reasons to pause at purchase time. And, recommendation time.
145 karma · joined July 26, 2015
Every year they seem to continue to introduce (via neglect/decisions/priorities) more reasons to pause at purchase time. And, recommendation time.
Without these gambles, the project will often fail too.
It's a really rather difficult problem.
Wouldn't surprise me if iPhone 9 was wireless only. Somehow.
I can understand why this could be a useful internal experiment. But, clearly, some people at Google expected this to be a viable product. Baffling.
I _think_ we are saying the same thing. I'd put 'done' in quotes for exactly the reasons you mention.
Timeboxing is merely used as a forced checkpoint; to re-assess across all activities/plans. It doesn't mean we can't follow on with more spike work.
At the end of the day, we, as a business, have to determine what we do (or don't do) and when. And we use spikes (or 'research', sic) to try to help inform those decisions.
If a problem occurs - as per your scalability example - or we identify more 'unknowns', we now need to make more decisions, and use spikes (and experience, and etc) to help inform those ... rinse/repeat.
In addition to the great information you've provided, we identify features/decisions/choices that require spikes based on assessment that they are high risk and/or we have low confidence in our estimate. In addition, we sometimes use spikes to break xxx-large estimates into smaller pieces.
That way, until a project/plan/item has low (enough) risk, and high (enough) confidence, it needs more spikes.
We've found this model is a great way of identifying what needs spiking, and when a spike is 'done'. And, it also helps to ensure spikes don't end up consuming too much time.
Hope this is useful.
I doubt the author would admit it, but, I think a lot of hyperbole is due to long-standing "Mac devs" and the author's circle of friends and acquaintances being unable to sustain a living from (merely) writing their own apps. Which is especially frustrating for them as the audience has grown dramatically over the past 5+ years.
Sure, the supply has grown considerably, and with that there are more 'light, snackable, mass-market apps'. But, that's what happens when the barrier to entry gets lower, and supply increases.
It is a true shame when we lose gifted 'indie' developers and some truly fantastic apps. But, no one has a right to a living.
Interestingly, and perhaps a hidden message in this article, is that there are significant parallels to draw to journalism.