scrum

Blog Post: @ev Is Bringing #Holacracy Mainstream

Ev Williams has made quite a name for himself. Not just with the software products he has helped create, but also in the way he runs a company. This post on Medium describes one of the principles of a social technology called holacracy.

Simply put, holacracy is a system for running an organization based upon ideas such as empowering employees, limiting office politics and boosting meeting efficacy.

I really liked the concept in this article, which involves ending meetings with a “closing round” by all attendees. It can be used for summary, takeaways, confirmation, affirmation, etc. Even with 30 seconds of concise dialogue, a ton of information could be communicated to team members going forward.

“Great meeting today. It highlighted that I need to follow up with marketing on their projections for the new product hitting production next month. It will allow sales to start generating buzz with customers beforehand.”

Try this out in your next planning session or retrospective. It allow confidence to be built, remind others of roadblocks and issues, or tasks to be confirmed before starting them.

Blog Post: @ev Is Bringing #Holacracy Mainstream

Read more "Blog Post: @ev Is Bringing #Holacracy Mainstream"

Blog Post: User Stories are Overrated?!?

Today’s link really got my blood boiling this morning, mainly because I have had Scrum training from Mike Cohn. I also hate it when people feel the need to go after the top people or businesses in an industry as a means of getting some notoriety. That may or may not be the case, nevertheless I watched the video from Tom Gilb seething.

After some Googling, I found out Gilb is a engineer and has made quite a career out of the inspection and metrics behind great software. I didn’t need to search to find this out, though, because that world view is clear from his approach to user stories.

That’s when it dawned on me that this video is a great teaching tool for product personnel. As I always say to my colleagues: user stories are the beginning of the conversation with development, not the end. The mistake I think Gilb makes is seeing stories by themselves as the sole piece of information an engineer needs to do complex work.

Having used this method of communicating requirements at several different companies, trying to lump all user stories in the same boat is hard. We all write them differently, and compile acceptance criteria differently. Within the same release, I am capable of providing a great amount of information that gives developers everything they need as well as the opposite. That’s where the conversation takes place.

Every engineer and architect I have spoken to have had their fair share of poorly written requirements. My favorite joke is to tell my team, “show me on the doll where the product owner touched you.” The challenge to my job is finding a way to meet them in the middle of the conversation and craft stories towards a method of delivering the best features possible.

So, instead of bashing Mr. Gilb for not reading and understanding Cohn’s methods, I would like to thank him for reminding me the purpose of my job. It’s not to stand in the way of great software, but making it easier and well thought out.

We involve stakeholders, help with design, converse with our teams, and document everything along the way. We are product managers, Tom, and our user stories can be your friends.

Blog Post: User Stories are Overrated?!?

Read more "Blog Post: User Stories are Overrated?!?"

Blog Post: Minimum User Design

In all honesty, I was drawn to the title of this post on Smashing Magazine because of my affinity for the Minimum Viable Product. In it, the author describes a way to gauge the progress of a website design and then add functionality after it accomplishes it’s primary need. What a way to approach product […]

Read more "Blog Post: Minimum User Design"