>Teaching developers who are used to building things for how they think they will need to be in the future
I'm trying to convey this very thing to my [new] manager and [new] BA/QA. With them coming on and taking over we are now doing agile in name only ... they brought their process/documents/outputs(over outcomes) waterfall ways here. It's a bit hellish lately. (I get those things were needed for SOX compliance but that overhead isn't needed here. They know a hammer, we are a screw. They are now trying to hammer the screw to make things work. SMH)
I'm trying to convey this very thing to my [new] manager and [new] BA/QA. With them coming on and taking over we are now doing agile in name only ... they brought their process/documents/outputs(over outcomes) waterfall ways here. It's a bit hellish lately. (I get those things were needed for SOX compliance but that overhead isn't needed here. They know a hammer, we are a screw. They are now trying to hammer the screw to make things work. SMH)