How do software engineers architect and design software in the era of agile/scrum?
We embrace scrum with short cycles but that seems to drive out design time in favor of code in order to get it done. What passes for software design these days in the modern age of agile SCRUM?
It seems design is considered top-down, waterfall thinking, but when you step away from a white board the code produced is not usually traceable back to a white board, which essentially a high-level macro.
So what tools or approaches are being used in the white board's place?
It seems design is considered top-down, waterfall thinking, but when you step away from a white board the code produced is not usually traceable back to a white board, which essentially a high-level macro.
So what tools or approaches are being used in the white board's place?
