Since we began our transition to a scrum team, I’ve been looking for ways to help “marketize” our process as much as possible. Since this is my first time operating in this mode outside of an engineering department, I was searching for clarity on how this being a marketing scrum team changes the dynamics (if at all). I like this article because it covers a lot of ground, and I take from it that a marketing scrum team can, for the most part, be as similar or as different from an engineering team as you want it to be.
I’m trying my best to not overthink this too much, and to go with the flow as much as possible. There are going to be mistakes, there are going to be things done one way that could have been done more efficiently a different way, and it’s going to take time before we can officially call ourselves a “settled” scrum team. That’s part of the process, and trying to eliminate that simply pushes those growing pains off to be dealt with later on.
I liked this article because I think it really connects with where we are now in our evolution. At our tasking meeting this week we asked ourselves for the first time as we went through each story, “What does successful completion look like for this?” We’d been going at it from the other direction previously, which meant we would simply list out the steps needed to complete a project in principle, and then follow those subtasks until they were all finished. Looking at it this way and considering how we want something to look when it’s finished has really helped me consider how I can make it easier for my team with my tasking.