The art of interrupting software engineers

Re:The art of interrupting software engineers by pflenker on Tuesday July 30, 2019 @06:49AM (#20563613)

Not necessarily. The idea here is that the customer has an idea about what he wants, but has only a vague idea about what he actually _needs_, and no idea about what is technologically possible.

Methods like XP embrace that by allowing requirements to change over time, to account for the customer accumulating more knowledge about all three areas.

[ Parent | on HN ]

Re:The art of interrupting software engineers by repolfx on Tuesday July 30, 2019 @07:22AM (#20563799)

But you can nail those things down before coding begins, just through talking with them. You don't need to literally change the code completely every week - iterating a plan is much easier than iterating a codebase!

[ Parent | on HN ]

Re:The art of interrupting software engineers by pflenker on Tuesday July 30, 2019 @08:39AM (#20564242)

Not necessarily, and it really depends on the customer and on the software. You feed the learnings from one iteration into the next - it's not intended to change the code completely every week, but to allow maximum flexibility in the backlog.

[ Parent | on HN ]

Re:The art of interrupting software engineers by afarrell on Tuesday July 30, 2019 @08:14AM (#20564098)

But with 2 weeks of coding, you can save yourself an hour of planning.

[ Parent | on HN ]