10 Agile Tips From Pokemon Go Coach Training - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

12:06 PM

10 Agile Tips From Pokémon Go Coach Training

Pokémon Go players want to improve and become better trainers. The same tips that help you catch more Pokémon can help you become a better scrum master. We caught 10 of those pointers that can be applied to leading an agile team developing enterprise software.
1 of 11

(Image: 2funki4wheelz via Pixabay)

(Image: 2funki4wheelz via Pixabay)

Have you heard of this new game everyone's playing? "Pokémon Go," I think is what they're calling it. I had read about it, but it really came into focus when I saw a group of people with smart phones held at arm's length wandering around the lawn outside a nearby hospital. This is a serious game with serious implications ... for agile development.

As with so many aspects of life, it only took a few days before articles started appearing on the web with advice on how to be a better Pokémon Go trainer. It was only a couple of days later we began to see ads for people willing to catch and train Pokémon for you, but we're not here to talk about PaaS (Pokémon-as-a-Service).

Instead, we're here to talk about how becoming a better Pokémon trainer can help you become a better product owner or scrum master within the agile development discipline.

I know that there are many who will see absolutely no parallels between running around the landscape chasing imaginary monsters with a smartphone and leading an agile team developing enterprise software.

I think those people haven't looked deeply enough at the process of catching and training all those pocket monsters now scattered about the landscape. The link between the two is strong, with deep lessons for scrum masters to be taken from the exercises necessary to "catch them all" in the Pokémon universe.

[See Agile vs. DevOps: 10 Ways They're Different.]

I went around the internet looking for tips on becoming a better Pokémon Go trainer and found a bunch that translate directly into ideas that will help you be a better product owner or scrum master. Out of that group, I've chosen 10 that you should be able to put to use very quickly in order to make a real impact on your next sprint.

Have you become a great Pokémon trainer? Is Pokémon Go taking over your office? I'd really like to hear about your experience with Pokémon Go -- and about all the ways that the game has helped you with your agile experience. The links are out there. Let's hit the parks and catch those Pokémon -- and the lessons they carry!

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
1 of 11
Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Susan Fourtané
Susan Fourtané,
User Rank: Author
7/25/2016 | 1:53:17 PM
Creative comparison
This was a very creative comparison. I haven't spent one minute thinking about Pekémon Go. I would like to know if more enterprise people have found these or other similarities as well. 

Joe Stanganelli
Joe Stanganelli,
User Rank: Author
7/24/2016 | 12:31:40 PM
On #2
Re: #2, "Do Whatever Task Is Required"

Ultimately, the sublesson here comes down to: "What is it worth to you."

In Pokemon Go, some people just want the game to be about collecting the Pokemon.  They don't want to hassle of strengthening their collection beyond adding to it.  That aspect is not fun to them.  They've put a value on their time and, as per their cost analysis, they've determined it's not worth it.

Same thing with software development -- and, really, anything in business in any industry (indeed, agile and scrum are increasingly being adopted in non-software contexts/environments).  Sometimes, you may run into a problem that is substantial enough that it may actually be more cost-effective to call it quits or find an alternative.

Or, as the old Zen saying goes, "No matter how far you are down the wrong road, turn back."
InformationWeek Is Getting an Upgrade!

Find out more about our plans to improve the look, functionality, and performance of the InformationWeek site in the coming months.

New Storage Trends Promise to Help Enterprises Handle a Data Avalanche
John Edwards, Technology Journalist & Author,  4/1/2021
11 Things IT Professionals Wish They Knew Earlier in Their Careers
Lisa Morgan, Freelance Writer,  4/6/2021
How to Submit a Column to InformationWeek
InformationWeek Staff 4/9/2021
White Papers
Register for InformationWeek Newsletters
The State of Cloud Computing - Fall 2020
The State of Cloud Computing - Fall 2020
Download this report to compare how cloud usage and spending patterns have changed in 2020, and how respondents think they'll evolve over the next two years.
Current Issue
Successful Strategies for Digital Transformation
Download this report to learn about the latest technologies and best practices or ensuring a successful transition from outdated business transformation tactics.
Flash Poll