Couldn't have said it better. In my experience with Agile, I have had great managers who actually use it to push back against their managers. Agile is there to work for us as developers, not to be a yoke. We say what we can fit into a sprint and if some change they want isn't in the scope of that story, it is out. Scope creep is one of the worst things about developing software as the people who aren't working on it everyday come up with new little ideas and tweaks that sometimes aren't simple to implement. This causes delays in deliverables which makes you and your team look bad. It causes delays in features which make the company look bad. It is just a mess. Agile helps with this.
"While you are in there can you do ..." "NO". Agile allows us as developers to say "that 'small change' will take 2 of us 3 weeks to change and test" and then management can decide if that small change is worth the cost of 2 developer salaries for nearly a month.
Agile done right is an amazing tool that we as developers can use to push back on stupid timelines and features. It is all about setting expectations in my eyes.
To be fair though I haven't been exposed to agile done poorly. I could see it being a disaster, but that is like a poorly written program; it is just bad implementation.
Couldn't have said it better. In my experience with Agile, I have had great managers who actually use it to push back against their managers. Agile is there to work for us as developers, not to be a yoke. We say what we can fit into a sprint and if some change they want isn't in the scope of that story, it is out. Scope creep is one of the worst things about developing software as the people who aren't working on it everyday come up with new little ideas and tweaks that sometimes aren't simple to implement. This causes delays in deliverables which makes you and your team look bad. It causes delays in features which make the company look bad. It is just a mess. Agile helps with this.
"While you are in there can you do ..." "NO". Agile allows us as developers to say "that 'small change' will take 2 of us 3 weeks to change and test" and then management can decide if that small change is worth the cost of 2 developer salaries for nearly a month.
Agile done right is an amazing tool that we as developers can use to push back on stupid timelines and features. It is all about setting expectations in my eyes.
To be fair though I haven't been exposed to agile done poorly. I could see it being a disaster, but that is like a poorly written program; it is just bad implementation.