You waste time on decisions that are going to change anyway. You get lost in things that don’t really matter. When you insist on writing a functional specification before any development begins suddenly you hear the cry to “go Agile on this one” when it seems to be based on little more than knowledge from a few blog posts and an impression that it’s the way forward, that it will magically mean the digital project is delivered quicker, to a better standard and probably on budget.īut getting infatuated with details too early leads to disagreement, meetings, and delays. The Waterfall Project Management team as seen by developers They use examples like the great success of Basecamp to confidently demonstrate their point and laugh at your seemingly old skool way of thinking. The problem is that I run into production teams that hero-worship 37signals, read all their books, blog posts and podcasts and take away from it that planning is rubbish in web development and digital projects. The problem I want to address is rather more abstract than if 37signals are right or wrong, I want to talk about the effect their attitudes combined with huge success and massive exposure have had on some web folk. But is that planning? Tim Berry, No, 37signals, Planning Is NOT What You Thinkīut although this article of mine may sound like just another one like the above that flat out disagrees with the 37signals mentality, it’s very much not… Running digital projects is not running a business Sure, if you define planning as messy and preventing you from getting real, then it would be a waste of time. …Really bad advice there, based on a bad premise. Imulus, 37signals Is Arrogant, And For Good Reason. I think 37signals dominance in the web products field has distorted their ability to critique the client-based approach. Or articles that have a similar tone to mine: Now let’s get one thing clear, I without question utterly admire the 37signals gang!! In this article I’d like to expose a common and potentially damaging trait I’ve noticed in the web design and development community that has stemmed from 37signal’s philosophy and Agile methodologies. ![]() Jason Fried, Let’s Just Call Plans What They Are: Guesses So next time call a plan a guess and just get to work. I think companies often overthink, overdo, and over devote to planning. That’s all plans really are anyway: guesses. The interview focuses on his, and 37signal’s, planning philosophy of which the crux is that too many people over plan and that the best way to progress is to plan loosely stay relaxed and adapt as you build, rather than deciding exactly what to build before starting and while in motion trying not to deviate from the plan.īusting your ass planning something important? Feel like you can’t proceed until you have a bulletproof plan in place? Replace “plan” with “guess” and take it easy. net magazine inspired me to finally write an article I first had the idea for after reading Rework. An interview with 37signal’s David Heinemeier Hansson in this month’s.
0 Comments
Leave a Reply. |