4 ms·
Since you consider yourself a "resource" I'm assuming you do hands-on development work on some sort of product. If so: introduce and start enforcing Scrum. If
by bartimus 4y ago
Since you consider yourself a "resource" I'm assuming you do hands-on development work on some sort of product.
If so: introduce and start enforcing Scrum. If agile is not in the DNA of your company Scrum offers a way to force an Agile process withing your company. With Scrum you (and your team) can gain autonomy over the development process. It allows you to create a clear separation of responsibilities towards whomever is using you as a resource. You own the development process. They own the business process. Turn the tables: start pushing them to have their business processes in order (Scrum gives you many options). Demand proper business requirements.
But there's a but: Some developers exactly prefer not to have ownership. They just want to work from 9 to 5 and have them handed a list of to-do's that they can work on. This is where development themselves gives away autonomy.