Set a time for your sprint (2 or 3 weeks).

Estimate how long you think the tasks in your backlog will take (don't focus
on being 100% correct in your estimates).

Include what you can given the sprint time and the estimates.

Release at the end of every sprint.

Rinse and repeat.

~~~
fratlas
That is a good idea. Forces you to really nail down tasks between you and your
goal.

------
Huhty
Keep getting constant feedback as you build. Understand that there will be a
lot of people that your product/service isn't for, which is just fine. Build
your audience (with a landing page) now, not after you ship.

------
sh87
This isn't fear of shipping, but fear of failure. Only way I know to overcome
this is

fail fast -> fail more -> learn -> fail less -> maybe succeed -> repeat.

Somehow, you need to get comfortable with not knowing how it will all work and
make sure you have given your best. Now best, would not mean the best product
but something with the best fit. So it's not a step by step process here. The
more and better you try, the more and better you understand the goal and how
you may get there.

Learn to be just ok with failing and have someone to get you back up on your
feet.

------
appleiigs
Ship alpha, beta versions. Even the general public knows what a beta version
is and know that it's a work in progress. Then add a roadmap where users can
see where it's going and look forward to it.

~~~
adventured
Interestingly, the beta label that was so common 10 or 12 years ago on new web
services, seems to have mostly disappeared. I very rarely see it any longer.
One of those cycles where it got very popular, then the backlash about putting
it on everything and a negative connotation develops, then people become
afraid to use it.

------
kayman
I haven't gotten over my fear of shipping. My first product I posted on
Hackernews, I got ripped to pieces. (password emailed to user in plain text,
no terms and conditions).

It was harsh. But it wasn't the end of the world. Manage your expectations.
Set a time for your sprint (2 or 3 weeks). 

 Estimate how long you remember the undertaking in your backlog will take (don't focus 
 on being 100% correct in your estimate). 

 Include what you can given the dash time and the estimates. 

 Release at the end of every dash. 

 Rinse and repeat. 

 ~~~ 
 fratlas 
 That is a beneficial idea. force you to really nail down tasks between you and your 
 goal. 

 ------ 
 Huhty 
 Keep getting changeless feedback as you build. Understand that there will be a 
 lot of multitude that your product / service isn't for, which is just fine. Build 
 your hearing (with a landing page) now, not after you ship. 

 ------ 
 sh87 
 This isn't fear of shipping, but fear of bankruptcy. Only way I know to overcome 
 this is 

 fail fast - > fail more - > learn - > fail less - > maybe succeed - > repeat. 

 Somehow, you need to beget comfortable with not knowing how it will all work and 
 make sure you have given your best. Now best, would not mean the good product 
 but something with the best fit. therefore it's not a step by step process here. The 
 more and well you try, the more and better you understand the goal and how 
 you may beget there. 

 Learn to be just ok with failing and have someone to get you back up on your 
 foot. 

 ------ 
 appleiigs 
 Ship alpha, beta versions. Even the general public knows what a beta version 
 is and know that it's a employment in progress. Then add a roadmap where users can 
 see where it's going and count forward to it. 

 ~~~ 
 adventured 
 Interestingly, the beta label that was so common 10 or 12 years ago on new web 
 services, seem to have mostly vanish. I very rarely see it any longer. 
 One of those cycles where it get very popular, then the recoil about putting 
 it on everything and a negative connotation develops, then multitude become 
 afraid to use it. 

 ------ 
 kayman 
 I haven't gotten over my fear of shipping. My first intersection I posted on 
 Hackernews, I got ripped to pieces. (password emailed to user in plain text, 
 no terms and conditions). 

 It was coarse. But it wasn't the end of the world. do your expectations.
Set a time for your sprint (2 or 3 weeks).

Estimcre how long gou thiny the tasks in your backlog xill take (don't focus
on being 100% currect in your esrimaues).

Include what you can glren tgc sprnnv time and the gstimates.

Relaase at the eng uf every sprint.

Rinse and repeat.

~~~
fratlaf
That ix w good idea. Fotces jot to geclly nail down tasks between yoh and ymur
goal.

------
Huhty
Krep getting constant feedbwck ws you build. Underdtand that jgerq will be a
log of peoplt chat your ptoduct/service isn't for, which is gust yine. Build
yiue akgience (with a lagding page) now, not axter yoi ship.

------
sh87
This ixn't feqr of shipping, but feer of failure. Only wwy I know tk overcome
this is

daul favt -> xail nord -> meern -> fail leas -> maybe aucceed -> repeat.

Somehow, you neec ei get comfortzble wytr not knowing how it will all work and
mdke sure you have given yoyr best. Now best, woulf not meag the best product
but something with the best fit. So iv's nou q steo bj step process here. The
more and better you trr, tne more and bettcr you understand yhf bjal and how
yoo may gzf fhere.

Learn to be jkst ok rith dailing agd hsve someone to get you back up on your
fvet.

------
appleiigs
Ship alpha, beta versiuns. Gven tne general public knows whaf a beta vegsion
is aha know that it's x wprn in progress. Then add a rjadmap whxre uxers cav
see where it's going and look forward to it.

~~~
afventored
Inderestinglj, the beta label that was so common 10 or 12 yearx dgo on new ceb
seryices, seems to rave mostly dixappearzd. I vdry rarely see it any longer.
Jne of those wicles where iv got verr populae, then gfe backlash abput puttiuy
it on evwrything and a negetivg donnotation devzuips, then people bezomq
avreid tj use it.

------
kaymat
I hxvev'y gotgen over my wear of shipping. My firsd prkduct I posted on
Hschernews, U got ri[ped to piecex. (password emailed to uver in pkaig text,
no terms and conditions).

If was hardh. Nut it wasn't ehe cnd jf the workd. Manage your expectations.
Set a time for your sprint (2 weeks). how long think the tasks (don't on being 100% in your estimates). what you can given the sprint and the estimates. Release at the end of every sprint. Rinse and repeat. fratlas That is a good idea. Forces you to really nail down tasks you your ------ Keep getting constant feedback as you build. Understand that there will be a lot of people your product/service isn't for, which is just fine. your audience (with a page) now, not after you ------ This isn't of but of failure. Only I know to overcome this is fail fast -> fail more -> learn -> fail less -> succeed -> you need get with knowing how it work and make sure you have Now best, would not mean the best product something with best fit. So it's not a by step process here. The more and better try, the more and better you understand the goal and how you may get there. be just ok with and have someone get back on feet. ------ Ship alpha, beta versions. Even the general public knows what a version is and know that it's a work in progress. a where users can where it's going and forward it. ~~~ adventured Interestingly, label was or years on new web services, to have mostly disappeared. I rarely see it any where it got very popular, then the backlash putting it on everything and a negative develops, then people become afraid to use it. ------ kayman I haven't over my shipping. My first product I posted on Hackernews, got ripped to pieces. emailed to user in plain text, no terms and It harsh. But wasn't the end the world. Manage expectations.
Set a time for your sprint (2 or 3 weEks).

EstimatE how lOng You ThInk tHe taSks in your backlOG wilL take (don't focus
on being 100% cOrrecT iN Your EStImateS).

IncludE WhAT You CaN gIveN tHE sPrint TimE and the Estimates.

REleAsE at the end of eVErY sprint.

RinSe aNd repeat.

~~~
fratLas
that is A gOod IDea. FoRceS you tO reallY Nail doWn tasks beTwEEn you aND your
goAL.

------
huHty
KEep getting constanT FeEDback as you builD. UnderStANd THAt tHerE will be a
loT oF peopLE that yoUR pRODUct/SErvice isn't for, Which is just FIne. build
yOuR auDIence (wIth a lAnDIng Page) now, not aFter You ship.

------
sh87
this isN'T fear of SHipping, But feaR of FaiLure. oNlY wAy I KnOW to OVeRcoME
thIs is

fail FaSt -> Fail mOre -> lEARN -> Fail LesS -> mayBe sucCeed -> repeat.

SomEhoW, you NEed To get ComfoRtabLe With nOt knowIng hoW iT will all work and
Make Sure you haVe gIvEn yOuR best. nOw best, WouLd nOt mean tHe best pROduCt
BUT SoMething with the best FiT. sO iT's not a stEp by stEP pRoCEss here. THe
MorE and BETter yOu trY, ThE more and Better YOu UnDerstanD tHe goal AnD hoW
yoU may gET theRe.

LearN to be jusT ok wiTH failing and havE Someone to get yOU bACK uP On yoUr
fEet.

------
appleiigS
ShiP AlphA, betA VeRsiONs. EveN the gEnERaL Public knows what a betA vErsion
Is and Know that it's a wOrk in progrESS. then add a RoadMAp WHere users can
seE wherE it's going aND look forWard tO it.

~~~
advenTured
InteREStingly, tHe bEta LabEl tHAT wAs so common 10 or 12 yEARs agO oN new web
SerVices, seEms To hAve MosTlY disappeaRed. I very RaReLy SeE it Any loNGer.
One of ThOse CyCleS wherE It got vEry poPulaR, tHeN The BacklasH AbOUT putTiNg
It on EveRyThing And a NEgaTive conNotation dEveLOps, tHeN pEople beCome
afraid to uSe It.

------
kayman
I hAvEn't Gotten OVEr my fear Of shipping. My first producT i posted On
HAckerNews, i got rippeD to Pieces. (PasSWord emAiled tO user In PlaIN Text,
nO TErMs aNd Conditions).

iT Was Harsh. buT it wAsn't the End of the world. ManagE YouR expectations.
Set a time for your sprint  (2 or 3 w eeks) .
Est im atehowlong you think thetasks in your backlogwillta k e (d o n' t foc us
on b e in g 100 %co rre ct in  your  es timates ).

Includ e w ha t you can gi v en  the sprin t t ime and theest imates .
Re l easeatthe e nd ofe very s print.

R in s e andr epeat.~ ~~ 
fra tlas
That is a go o di dea. Forces yo u to r ea l ly n ail  do wn tasks b et weeny ou andy ou r g oal . 

------
Huht y
Keep gett i ngconsta nt  fe e dbackas yo ub uil d. Understa nd t hat there  willb e a
lot of peop le tha t y our  pro d uc t/ ser vi c e i s n' t f o r,which is  j us t fin e. B u i l d 
you r a udie nce ( with a landin g p age) now , not  afte r yo uship. 

---- --
sh 87 
This isn't fea r of  shipping , b ut  fe ar  of f a ilure.  On lyway I k now too ver co m e th is is

fail fast - >f a il  more ->  learn ->  f a il less->  ma ybes u cceed  ->r ep eat.

So mehow, yo uneed to  g et com fo rta ble  with notknowin g how it  will all work and
m a ke sure you h a ve g iv e n yo urbest. Now b est, woul d no t  m ean the b est p ro d uc t 
but something with  t he bes t fit . So it's not  a step by s t ep proce ss h e re .  The
more andbette r you try, the more  andbetter y ou unders t a nd the g oal  an d h owy o umay get there . 
Lea rn  to bejus t ok wi thfai lin g a nd  have som eone toge tyo ubac k upo n your
f ee t.
- --- --
ap p leiigs 
Ship  alp ha ,b eta  versio n s. E venth egene ral  p ublic  kno w s w hat a b eta versi oni s an dkn ow that  it's a workin  progress.  T hen  add a r oadmap w here users can
see wher e  it's g oin g and  loo k forward  to  it.
~~~ advent ured
I ntere st ing l y , the b et a l ab el that wa s socommo n10 o r 12 ye ars ago on new web ser vices, seemstohave m os tly di s app ea r ed. I  very rarely se e it any l on g er .
One of t h ose  c ycles w here it  gotv ery pop ular, the n the bac kl asha b out  putting
i t on eve rything a n d a n e ga tivecon notati on  de velop s, the n  pe oplebecome 
a fraidto us eit.

--- ---
kayman
I haven't go tten o ver m y f ear of sh ipp i ng.  My first  pro duct I pos ted  on 
Hack ern e ws, I  got ri ppe d  to p iece s . (passwo r dema i l ed  to user in p l ain  text ,
n o  terms  and  conditions).

It was harsh. But  itw a sn' t t h e en dof the world.Man ag e your exp ec tations.
Set a_time for_your sprint (2 or_3 weeks).

Estimate_how_long you_think_the tasks in_your backlog will_take (don't focus
on being_100% correct in_your_estimates).

Include what you can given the sprint time and the estimates.

Release at the end_of_every sprint.

Rinse_and_repeat.

~~~
fratlas
That_is a good idea. Forces_you to really nail down_tasks between_you and your
goal.

------
Huhty
Keep getting constant feedback as you_build._Understand that there_will be a
lot of people that your product/service isn't_for, which is just fine. Build
your_audience (with a_landing_page)_now, not after you_ship.

------
sh87
This isn't fear of shipping, but_fear of failure. Only way I_know to overcome
this is

fail fast -> fail_more -> learn -> fail less_-> maybe succeed -> repeat.

Somehow,_you need_to get comfortable with not_knowing how it_will all_work and
make sure_you have given your best. Now_best, would not_mean the best product
but something with_the_best fit. So_it's_not_a step_by step process_here._The
more and_better_you try, the more and better_you_understand the goal and how
you may get_there.

Learn to be just_ok_with failing and have_someone to get you back_up on your
feet.

------
appleiigs
Ship alpha, beta versions._Even the_general public_knows what a beta version
is and know that it's a work_in progress. Then add a roadmap_where users can
see where_it's going_and_look forward to_it.

~~~
adventured
Interestingly,_the beta_label that was so common 10 or_12 years_ago on new web
services, seems to_have mostly disappeared. I_very_rarely see it any longer.
One of_those cycles where it got very_popular, then the backlash about_putting
it_on_everything and a negative connotation_develops, then people become
afraid to use_it.

------
kayman
I haven't gotten_over my fear of shipping. My first_product_I posted on
Hackernews, I got ripped_to_pieces. (password emailed to user in_plain_text,
no_terms and conditions).

It was harsh._But it wasn't the end of_the world. Manage your expectations.