4 ms·
yes, absolutely. 2 freaked me out the most. I managed to get enterprise github installed, taught people how to use it, set up the client on their computers, poi
by jfoutz 11y ago
yes, absolutely. 2 freaked me out the most. I managed to get enterprise github installed, taught people how to use it, set up the client on their computers, pointed them at tutorials, and pestered them regularly. For all that effort, over the 6 months the adoption rate was pretty much just 1 developer in one department - me.
It's just so damn hard to get people to change.
- kbenson 11y agoYes. Any change from the norm can be pointed to add a reason for failure/delay/cost overrun. There needs to be management buy-in and possibly even requirements for projects to reverse this inertia. Which is why there needs to be pressure on management.
- ryandrake 11y agoThe mentality is: typing in code = assembling the widget, while setting up source control and an issue tracker = decorating the assembly line.
- bnj 11y agoI'm in the position of trying to push towards changes just like these- introducing better issue management, team communication. Anyone aware of useful resources on rolling out institutional changes like that?
- jtrtoo 11y agoYes. See "The Phoenix Project" (book)