How to Finish Big Projects

Posted May 11, 2007 in Management, Starting It, 5 Comments »


Scenario: "Dude, we need to plan everything, then work incrementally by parts until we get there! Then, we'll get super-awesome product on time. Yay!"

You know how it works:

  1. Plan every-and-all project details.
  2. Work on each part one-by-one.
  3. At the end, combine everything.

You'd think you'll make it by the deadline; but weeks/months -- no years! -- pass, and you're wonder what the !@#$ just happened.

The problem with completing big projects using conventional methods?

  1. It's inflexible.

    If you need to change something, it affects everything else. Planning stages? That's right: seemingly, it's time to plan everything all-over.
  2. It's long.

    You won't get a working product until you're done; by then, market conditions change -- meaning you'll have to adapt from your plans. Oh no!
  3. It becomes de-motivating.

    Remember building that last big project? "I had passion when I started, but that quickly faded..." you're probably telling yourself. By the latter stages, you're tired, groggy, and working like a snail on weed.
  4. It gets you a blah-product.

    Complacency produces mediocrity. Instead of filling the every nook-and-cranny of the project with juicy-good fillet mignon, you start filling it with burnt-soggy-steak. Need real-world examples? Demo 95% of business software.

To rock a big project, do sumthin' else.

The Solution: Adopt Agile Development

All-world software developers use a method they crazily call: Agile Software Development.

(We call it by its street name: ASD.)

That is:

  1. They build a releasable product within weeks.
  2. Then, they build outward to create successively bigger product releases.

The first releasable product has the most important stuff done.

They'll term it Version 0.1 (or, something similarly nerdy).

Next, they'll expand that version outward with additional features -- where those krazy-kids will term it Version 0.2 -- releasing that version within weeks as well.

Gradually, the successive small releases ultimately form one frickin'-juicy-good completed software item.

Completo.

Why Does ASD Rock?

You start focusing on the most important sucka in the project -- get that out of the way, then fill in the other parts.

That way, you allow yourself (or your team/business/yadda) to use the magic right away -- instead of waiting for a completed product with lesser important parts.

Remember, in whatever humongous product you're building, keep this in mind:

  • 20% of the project serves 80% importance.
Likewise, regarding that above 'twenty-percent':
  • 20% within the twenty-percent serves 80% importance within the twenty-percent.

In other words, completing 4% of the project (i.e. 20% * 20%) serves as the absolutely-freakishly crucial role in the project's success, which you can complete within weeks (or days/hours).

  1. So, instead of aiming to complete 100% of your big-frickin' project, complete the crucial 4%.
  2. Then, build outward with successive releases.

Example: You + Your Web Design Business

Let's say you've decided to build the most influential web design business in the world.

So what does your butt do?

You start building business with its most crucial parts -- where you set a two-week launch date.

After those two weeks: "I gotta start selling my web design services, or else!" you scream at the mirror.

So, you get the essential parts done to sell web design in 2 weeks:

  • You produce a 1-page website detailing your awesome stuff.
  • You provide screenshots of your 5 previous homepage designs.
  • You get a phone number for people to order your shizzle.
  • You solicit testimonials to wow prospects on your marketing collateral.
  • You create an order form on that 1-page site to order online.
  • You get a business license, and a DBA.

Ta-da!

You start selling your web design services by your deadline.

Now, seeing how magical you were, you now tell yourself:

"It's time to service the B2B sector!"

So, how do you expand your web design business?

  • You give yourself two weeks to target the B2B sector.
  • You contract with one full-time experienced B2B salesperson.
  • You expand on the 1-page website with an additional link to your new service.
  • To not confuse your initial service, you term the new B2B service: B2Bdezigns2.0.
  • You describe the bottom-line advantages of having a pretty web design.
  • You emphasize how you optimize your designs to generate the most leads.
  • For marketing collateral, you solicit testimonials from your previous B2B customers.
  • You provide screenshots of your previous B2B designs, and show the % increase in leads.

You start selling the sucka within 2 weeks to those biznizzy-folks.

Not only do you (1) now have a kick-ass web design service, but you've also (2) complemented the service with your B2Bdezigns2.0 to the business crowd.

Next thing you know:

Your business starts to rocket as you continually build outward -- and slowly-but-surely, it becomes one freakish behemoth with tons of profitable offerings, servicing 52 countries around the world, getting you on the cover of Forbes and Fortune, snatching you a million-dollar movie deal with Brad Pitt starring your life -- and, finally, the ultimate of it all:

You get on Oprah.

To finish big stuff: Complete the releasable tiny stuff -- then build the mutha-!@#$%^ outward.

If you enjoyed How to Finish Big Projects, get Trizle's popular new articles freshly sent to your inbox.


More Business Tips You Might Enjoy

  1. Why 90% Of Entrepreneurs Fail & Why You Won't
  2. Why A Billion Dollars Won't Excite You
  3. Why Doing Philanthropy Rocks
  4. How To Make People Like You
  5. How To Completely Fail At Your Business (tip #1)

5 Comments on How to Finish Big Projects

Senia Positive Psychology Coaching

Posted @ 12:13 PM on May 11, 2007

Hi Andrew and Trizle folks,

This is my favorite post that I've read on your site so far. I've been reading for a while, and this one really, really rocks!

It's so true that 1) life is easy, and you can build the easy parts of the software/product/company FIRST, and that 2) small successes (what Albert Bandura calls mastery experiences) are what motivate people to keep going, plus 3) flexibility is key to life.

On flexibility, there's a story I once heard of a man who at age 18 wrote down 150 things he wanted to accomplish. By age 40, he had accomplished them. BUT WHO CARES?!? He didn't change his goals while he changed as a person. He didn't achieve any new goals that he might have thought of.

Nice article. One of the best technologists I've ever known - he lived by this philosophy - build the core and then build outwards. He also lived by "build the easy things first, then we'll see if we still need the hard things" philosophy, aka life-is-easy.

Thanks,
Senia


Andrew

Posted @ 11:50 PM on May 15, 2007

Hi Senia,

Thanks for your compliment! We appreciate it.

"On flexibility, there’s a story I once heard of a man who at age 18 wrote down 150 things he wanted to accomplish. By age 40, he had accomplished them. BUT WHO CARES?!? He didn’t change his goals while he changed as a person. He didn’t achieve any new goals that he might have thought of."

Great story. I love the philosophy: Do what's absolutely most important now, then grow outward as your life progresses. Life's too long to plan for those things that might not be important decades from now.

Thanks for the input, Senia!

-Andrew


Tom

Posted @ 08:35 AM on May 25, 2007

Fun article about abut Agile. On the same topic, I think it might be worth some discussion around the organization and wether or not it's mature enough to implement Agile.

From some experiences around here, our early attempts at Agile development lead to a somewhat incomplete feature envelope in the product. The features that got implemented were the ones that the owner/founder was interested in. The remainder (which of course were truly required to complete the product) were left out which resulting in an application that was rather annoying in it's deficiencies to the end user base.

As our software development organization has matured, we have been able to invite end users into the testing process and make sure that we answered their big issues in the later builds.

As always, any new process comes with the learning line item.

TC.


Agile and Offshore « Software Quality & Management Insights

Posted @ 03:51 AM on June 30, 2007

[...] P.S: A great article on Agile Software Development on Trizle titled How to Finish Big Projects where the author emphasizes on creating crucial chunk first and then build outwards.   [...]


steve the asd

Posted @ 07:13 AM on May 23, 2008

yeh, the importance of agile is after you build your 2 week iteration, you need to show it to the shareholders and make sure you are going done the right track. and your shareholders must be chosen carefully. in the example above, the shareholder wasn't the boss, it was the end user, the person who would be paying for it. and those testing shareholders must be realistically chosen to represent a true sampling of your real world market. in other words they can't be your parents cuz they won't tell the the truth that you need to succeed in the world. they should be paying customers. if they don't like it, they won't pay. that will get you on the correct path quickly...


Comment on How to Finish Big Projects





Submit comment

About Trizle

Trizle helps your business rock the world.

Subscribe to Trizle


Subscribe

Get Trizle's Lil' Guide

Get Trizle's little guide to build your business. We filled the lil' guide with our best tips to build your thriving business. The lil' guide comes with a 100% satisfaction-guarantee.

 

Copyright © 2003-2008 Trizle. Contact us. Photos provided by Photocase


back  |  next