1. Priorities in Feature
Development
Fares Farhan, General Manager @ LJ System Indonesia P.T

2. The Idea
• Explicity define a point for each feature
existence. Why should it be there? what’s
the purpose?
• Create clear picture for the idea,
communicate it.

3. Ignore Details
• Details reveal themselves as the feature is
being build.
• Details is not a guarantee for accepted
feature(s). We’ll find stagnation,
disagreement, meetings and delays. Focus
on that, save the details for later.

4. Foresee issue(s)
• Issue is issue when it is. In the beginning,
just see it as “possibly happen” which
should make us think the anticipation, not
arguing the solution for thing(s) that might
happen in (maybe) several years to come,
when everything needs to be changed
anyway.

5. Focus on client’s
requirement
• Build a feature that is required. Standards is
important, but we can’t please everyone
from developer to client. We can’t create
something that is “pleaseable” by everyone.
Because when we try to built something to
please everyone, we won’t please anyone.

6. Scale later
• Should we make our product scaleable,
extensible? Yes.
• Think big is must, act big? later. Anticipate,
put good solid core for the product.
Observing over scalability later.
• The problem is not scaling, it is getting to
the point where we need to scale that is
the real problem. We won’t have second
problem when there is no first.

7. Things to discuss
• How can we define the most important point for a
feature?
• How to avoid stagnation, disagreement among team
member?
• What are things that needs to be exist when we need to
foresee issue(s)?
• What should be the main points which are in a
requirement?
• How we define the scalability or extensibility of the
feature that is going to be developed?