4 ms·
The question is, for a product, which approach is best? Do you solve the low hanging fruit, and are responsive to clients but with high risk of breaking somethi
by kabouseng 12y ago
The question is, for a product, which approach is best? Do you solve the low hanging fruit, and are responsive to clients but with high risk of breaking something else, or do you work methodologically through your product road map but are less responsive to clients.
The Agile movement's aim can be said, is to reduce the feedback loop of software development, so favouring a stack approach (echo'ed in facebooks "move fast and break things" approach), but I have also seen situations where there is no strategic planning, and the team can churn for a year like a dog chasing its own tail. Methodologically working through your roadmap can again be seen echo'd in Steve Jobs approach of saying the client doesn't know what he wants, its your job to give it to him.
- falcolas 12y agoI think there is room in larger teams for both types. There are always high priority tasks which need immediate attention, and a backlog of tasks which needs to be churned through. If you can have both types of people on a team, you can assign the tasks appropriately and be sure they will all get done.