I’ve been accused of being a narcissist before. Not in those exact words, but I will never forget the conversation. I was 25 and a good friend of mine and I were talking. She finally said (in a rare pause of my banter), “Natalie, you always talk about you and never ask about me.” Wow, that one hit hard and I felt guilty and ashamed. I had never thought about it before. I wondered where my baby-boomer parents had gone wrong in raising me as a millennial snowflake (who was nothing but extraordinary) who didn’t know the true definition of meaningful discourse. Ever since then, I’ve put a concerted effort into making sure that I ask the other person I’m talking to questions about themselves. It’s a constant reminder in my awkward conversational brain – “ask them about their day, weekend, year…yeah—that’s perfect!” We often run into a narcissism problem in product development, too, and it can stem from fear and shame.
I spent the beginning of this week at the Scrum Gathering – New Orleans (SGNOLA). As always, it proved to be a great time full of culture, learning, networking, and fun. I like to do recaps after conferences sometimes: first to ensure that I don’t lose what I captured, and second to share my thoughts with those who were unable to attend. The highlight of SGNOLA was my co-presentation with Leslie J. Morse: Can Definition of Ready make Scrum “The Big Easy?”
On a project I was ScrumMastering for I noticed much contention between many of the different roles on the team. In keeping true to Agile and Scrum we are supposed to be “cross-functional” but what does that really mean? I kept hearing “they’re not doing their job” and “that’s not MY job” in regard to requirements gathering, writing stories, and even bug fixes. There have been many pieces written on the roles of members of a Scrum team as well as many things written on cross-functionality of members, but what does that really mean and where do we draw the line to keep people accountable?
So I’ve alluded to a UX runway and my work with Agile and UX in some of my previous posts, but what does that mean? Agile has been the buzz for the past decade and UX was quick behind. First, let me give some background on UX and my role on the team.
The Definition of Ready is a concept that is gathering more momentum within Scrum. Where it likely sounds most familiar is from the “Ready” state in Kanban development. You obviously would not pull a Kanban story to “In Progess” if it was not already in the “Ready” queue. The same should be true of stories…