ok ra na bai if daghan mo. but if ikaw ra nya he's not sure what he wants. patay ka sa maintenance ana. :P
ok ra na bai if daghan mo. but if ikaw ra nya he's not sure what he wants. patay ka sa maintenance ana. :P
one mistake that most programmer encounter also is that we tend to make things perfect all at once, resulting into delays of deliverables. We should at first submit the minimum requirements needed by the clients and work for improvements later. Even the most prominent software company releases software which are buggy and work with patch and servcice packs later.
Your developement lifecycle must not reluctant to changes, it should love and welcome chages. Because changes would meant additional income.
up up up up
nice info. we really need this. in-depth and witty.![]()

dili ra sad sa mga developers, one thing also about the clients, is that naka set na ang plan, layout, and everything, naa mahuna hunaan nga nindot nga idea, usbon na sad ang layout sa website, ang structure, the "I dont like this, that...Hey, got a cool idea, maybe you can put this on my site...blah blah blah," kalagot, daghan kaayo changes na di maka contribute sa development sa site.
diba naa mana sa agile development bai? like you should have like a cut-off for changes and do it in the next phase or iteration?
dili ba naa na sa agile software dev't bai? like to have a cut-off sa mga changes and let them see the working product in the first phase of dev't and so on? and then if naai changes diha isugod sa next phase para dili ma disrupt and dev't halfway through?

hmm,,wala na sa amo, what i do is i list down all the client's ideas, nya after ma implement then next nasad, next, next...mao ra,hehehe,,,mao na hangtod karon wala jud kahumanan, mas maayo nuon kay naa pa ta trabaho.
careful ana bai. sometimes makagubot na sa code.
Similar Threads |
|