[Adapted from a post to our internal Slack team.] My manager has been working to get an agile consultancy into our university's central IT department to help us progress in our journey toward being more agile. I hope that the training and coaching we receive will focus more on the root principles of value in agile processes rather than on a single process like Scrum. Are there any root agile principles that you think we need to be better at embracing? Here are some that come to mind for me. Develop functionality vertically instead of horizontally. You don't create the database layer all the way, and then the web services layer all the way, and finally--after 9 months--start to create the web user interface. Instead, you find a way to introduce a complete feature that touches all those technology layers so that you can get real feedback about the usage and value of the system or feature. Be willing to throw things away. If we're going to experiment, we have to be okay
We haven't had a refresh on our strategy direction in my office for a few years. It seems like we are frequently torn between being efficient and being innovative. Efficient Lower cost speed to production minimal failures maximum uptime Innovative Higher cost lots of failures freedom to pursue non-"approved" activities shorter attention span I'm part of an IT shop with nearly 200 services that we offer to campus and internally. I love the feeling of being innovative, but I'm concerned that our current push is to be innovative at the expense of being efficient. The result is that we can't accomplish as much near-term good for the campus because our focus is on the longer term.