How is what working defined? I’ve seen companies where they say, well the feature shipped so our agile is working. But how the feature released was such a mess
Well I’d say if you are calling it a mess it’s probably not working. Can you think of a single practice, or aspect of the last time you released software that didn’t go well? Maybe figuring out what you would do differently and then identifying who needs to approve that change or be impacted by it. Then get to know those people, and figure out what about your change will make their life easier. Get everyone on board and make that small change. When it’s successful - repeat. The improvements will go faster as you gain reputation for each incremental improvement.
How is what working defined? I’ve seen companies where they say, well the feature shipped so our agile is working. But how the feature released was such a mess
Well I’d say if you are calling it a mess it’s probably not working. Can you think of a single practice, or aspect of the last time you released software that didn’t go well? Maybe figuring out what you would do differently and then identifying who needs to approve that change or be impacted by it. Then get to know those people, and figure out what about your change will make their life easier. Get everyone on board and make that small change. When it’s successful - repeat. The improvements will go faster as you gain reputation for each incremental improvement.
Just one way that’s working for me, YMMV.
Well the devs know it’s not working but upper mgmt thinks it is because thinks are shipping
Were there any times where you were pressured to not follow a process or maybe compromise something with the code?
If so, is there anything you can teach some of the managers before your next project or sprint to get you support for doing it right going forward?