Skip to main content

Beyond Scrum?

[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 building things "incorrectly" the first time. We won't realize it is incorrect or suboptimal, so we're not building it badly on purpose. But we don't want to be stuck in analysis mode too long. We want to get something to users that they can feel and give us feedback on. This is ultimately more reliable than our up-front analysis. (I'm not arguing for no analysis or design, just not to let it go on too long.)
  • Develop a culture of testing. This includes user testing, unit testing, A/B testing. Pre-release testing. Post-release testing.
  • Encourage teams to reflect on how their version of the project process is working. This is the concept behind a sprint retrospective. I've been really bad at encouraging this, but I should be better.
These thoughts were stimulated by receiving this article in my inbox this morning. "Life After Scrum: Development Methodologies for DevOps"

Here are some interesting quotes from the article.
DevOps stalls unless organizations move past Scrum
Many people erroneously equate "doing Scrum" with "being agile"
Be aware that constraints to autonomy may be indirect. For example, teams cannot choose to employ an estimates-free way of working if they are subject to governance processes that demand estimates. Similarly, enterprise-mandated tools such as enterprise agile planning software may enforce processes.
This previous quote about tools guiding our process is one we definitely want to think about as we adopt NetSuite as our OIT ERP tool.
Accept that a short-term disruption is a part of growing into a high-performing team.


Popular posts from this blog

Deceptive Per Captia Rankings for Brain Cancer

We're working on a project to produce a report on the ratings that students give to their professors at the end of the semester. There is a big concern by the math people on the committee that we will give some professors an unfair bad (or good) rap because of the variability in these rankings. They don't want to report the ratings as a mean (average). Instead, they want to plot an uncertainty range.  I was reading a book this week (How Not to Be Wrong by Jordan Ellenberg) that provided a great example of the risk of ranking things when there is uncertainty. It can lead to erroneous conclusions. Here is a summary of his argument that appeared in an NPR interview . Perhaps this sort of example will be helpful for the committee to share when teaching the general faculty about the new instrument. If you take a rare disease like brain cancer and you look at its rate of incidents in different states , there are very big differences. And so you might say, "Well, I should

Hammers and Nails: Technology Push Design

"We need to refine our requirements first, before we look at tools." This is a common phrase that I hear. While I sympathize with the sentiment, I think it is frequently wasteful. I suspect that we'd get to the right requirements faster by looking at tools already available in a given problem space. Pushing the concept further, is it foolish to find a cool technology and then look for ways that that technology can apply to current problem spaces?  What if you don't even recognize you have a problem space? Without a constant search and openness, we'll miss many serendipitous opportunities. Here is BYU professor Larry Howell discussing this issue. I often enjoy doing something ... that is sometimes controversial. In this approach, rather than starting with a need, you start with a new technology and you search to identify a need that it can fulfill. This second more controversial approach is called "technology push design."   You can imagine t