Get to completion

Now a days, in my workplace, we are all (working hard, trust me) trying to meet deadlines and get the product out of the door! This does involve a lot of stress with meticulous planning and making sure we do not pass away important things. And I myself do realize the fact that there is no limit to writing code and there is always scope for improvement. And most of the time, when there is a great product idea, one cannot wait to see the idea become a reality. When I conduct the meeting every day, I always keep in mind the following:

1) Keep the scope as simple as possible and take "baby steps" - Don't try to everything at one go. The more you try to do, the more it gets complex because the time-lines do not change but scope does increase adding to hell lot complexity.

2) Perfection is the enemy of completion. Try to get the product the "good enough" state and not really THE perfect state.

3) My favorite 80-20 rule applies here too. Concentrate the most of 80% use cases and not 20%. Kill all the features that will be used by 20% of clients as they are really not mandatory for completion.

4) With the constant change in technology and high competition, one needs to make sure to get the product out fast in a good enough working form as simply as possible.

And, remember every product has a scope of improvement and also possible to add more and more and MANY MORE features :-).