Age of Product’s Food for Thought of August 28th, 2016—shared with 4,165 peers—checks in on the state of autonomous teams from Dublin to Africa, and how team membership is usually managed in organizations.
Arrrgh! We also learn that pirates were pretty agile, true examples of self-organization, the application of which nowadays needs to be explained by a Harvard Business School professor.
We then try to better understand the cultural habits of highly effective (cross-functional) product teams, that allow, for example, AirBnB to spearhead the assimilation process of Cuba into the international tourism industry. (Product borgs, so to speak.)
Last, but not least, we need to come to terms with the idea, that work can actually fulfilling and fun, and not just pain and misery, at least at Menlo Innovations. Enjoy a great Sunday!
This fourth part of the Lean User Tests series focuses on equipment and location: What hard- and software do you need to run your user tests, and where to run them? (Spoiler alert: It’s preferably not your office.)
How are your preparations progressing? If anything is impeding you from reaching this goal, please do not hesitate to contact me by commenting this post, and I will gladly help you.
Stakeholder communication: It is simply not enough for an agile product development organization to create great code and ship the resulting product like a clockwork. You also need to talk about it, particularly in the beginning of your agile transition. Marketing the agile journey of product and engineering to the rest of the organization—and thus getting their buy-in—is a critical success factor to step up the game: You want to become agile, not doing “Agile”.
So, learn more about ten proven stakeholder communications tactics that contribute to making this happen.
This part of the Lean User Tests series focuses on selecting and inviting interviewees: Who is a suitable candidate, how to invite them and why you will need replacement candidates.
You should now be around three to four weeks away from your next—or first—user test. If anything is impeding you from reaching that goal, please do not hesitate to contact me by commenting this post, and I will gladly help you.
Disclaimer: Of course, this post is in no way intended to be gender-specific. In my experience, there is no difference between the Scrum pop and the Scrum mom. This post is all about the emerging trend of Scrum helicopter parenting.
Beware the Scrum Mom
Trying to be supportive and do good, is most of the time a honorable thing. This is particularly true in your capacity as a Scrum master. However, doing too much good can quickly have the opposite effect. It’s a known Scrum anti pattern, often referred to as the Scrum mom syndrome.
Read on to learn more about its manifestations, and the damage to your team caused by being overly protective.
From Scrum master to product owner, this set of questions addresses the future collaboration between the both and the rest of the team. The questions have been modeled after some basic principles, that high performing teams have in common. (You can read more on this topic in Marty Cagan’s post Product Success.)
20 Questions to Ask the Product Owner to Get up to Speed as a New Scrum Master
In a world where data-driven decision making is often prevalent, some people feel uncomfortable with agile methodologies as those provide only a few useful metrics. One of those few, however, is the cycle time from idea to shipping a valuable product increment to your customers.
If you want to optimize this metric for your organization, speeding up your product discovery process is essential. And this requires two things: a) rapid prototyping and b) people to test your prototypes with. That’s the main reason why running user tests continuously is so important.
Learn how to best organize and run user tests in this series of six blog posts. Today, we start with answering the “why” question and what huge benefits user tests will provide to your product discovery and delivery process.
When dealing with product roadmap failure, stop debating whether you are doing product roadmaps “right”, or whether roadmaps are evil. Look instead at the job you are hiring your roadmap to achieve. And then ask if the roadmap is the best tool for the job.
14 Common Product Roadmap Failures
A Summary of Almost all Methodology Debates on Twitter
Roadmap Needs and Being Awesome
New to Product Management? What is a product roadmap? For a standard definition see here.
Agile turns into micromanagement as a result of the middle management’s resistance to change. Despite better knowledge, changing an organization into a learning one, that embraces experimentation and failure is not in the best interest of everybody. Self-organizing, empowered teams often conflict with the middle management’s drive to execute on personals agendas.
The agile consulting industry repackages an originally human-centered, technology-driven philosophy into a standardized, all-weather project-risk mitigating methodology. Sold to command & control organizations, their middle managers turn “Agile” into a 21. century adoption of Taylorism for knowledge workers. Beyond this meta-level, the reasons, why engineers despise Agile, fall into five categories: Control, manipulation, monitoring, technology and teamwork.
You want to know the state of agility in your organization? Here we go: Download the checklist, distribute it generously among your colleagues and run a quick poll. It will only take 5 minutes of their time–and then run an analysis on their feedback. If the average number of checkboxes marked is higher than nine, then you are probably practicing cargo cult agile. Consider changing it. Or abandon your agile experiment all together. But don’t refer to it as “agile” any longer.
Everyday Failures in Applying Agile
Agile methodologies, like Scrum, have been on the rise across organizations of all kind and sizes for some years by now. Many consultants responded to the increasing demand for agile practitioners, particularly from corporate organizations, with rebranding themselves.
Customer care as entity, its function and status within a company, can act as a good litmus test for a company’s culture, its product management, and thus its potential for innovation and agile change.
If customer care is regarded solely as a cost center that needs to be outsourced, agile change is unlikely to happen in that organization.
20 questions for you — the new Scrum master — that fit into a 60 minutes time-box. Start learning how the new Scrum team is currently working and get up to speed. Download an easy printable template for your convenience.
Start Learning the Ropes in 60 Minutes
I was recently asked to participate in the product backlog grooming of a team that was looking for a new Scrum master. I was skeptical in the beginning. I had only limited knowledge about the project—a commercial website based on a CMS—, the grooming session was time-boxed to 60 minutes, and I hadn’t met the team members before beyond a very brief “hello”.
So, I prepared a questionnaire with topics I wanted to learn more about, and listened to the team grooming several user stories asking questions from the list when appropriate. Surprisingly, the insights turned out to be much more qualified than I expected. Particularly, the low-hanging (user story and Scrum improvement) fruits could be identified rather easily.
Scrum Master Hiring: Demand Creates Supply and the Job Market for Agile Practitioners is No Exception
Maybe, “Agile” in general is a management fad and not trend at the moment. But what we can say for sure is that Scrum has become very popular for software development purposes. A seasoned Scrum master is nowadays in high demand. And that demand causes the market-entry of new professionals from other project management branches, probably believing that reading one or two Scrum books will be sufficient.
If you are looking to fill a position for a Scrum master (or agile coach) in your organization, you may find the following 38 interview questions useful to identify the right candidate. They are derived from my ten years of practical experience with XP as well as Scrum, serving both as Product owner and Scrum master as well as interviewing dozens of Scrum master candidates on behalf of my clients.
Yes, even absolute beginners can prototype an app. And learn a lot about product management, product design and user experience along the way. It is a low cost exercise that will greatly improve communication within your organization.
Intro: Why Organize an App Prototyping Workshop?
A few weeks ago, I wrote a post titled “No More LEGO® At Agile Workshops – I Am Tired Of Building Airports” expressing my annoyance with the common practice of exercises in workshops that use an inappropriate means in my eyes. I also promised to experiment with an alternative: Building app prototypes, utilizing one of the many prototyping apps in the market. And here is what I have learned over three workshops into this experiment.
The end of 2015 is nearing and it’s product roadmap building time again—at least for those companies that are still dedicated to the old command-and-control model. In the next few weeks, execs and (key) stakeholders will come together and define what needs to be built to meet business demands in 2016. So, here are the seven best practices on how to build product roadmaps the agile way.
When I wrote the Agile Failure Patterns In Organizations post in October, I could not anticipate the feedback it would receive: Over 80 comments on the Hacker News thread and almost 15,000 readers on the blog and additional channels like DZone or Business2Community.
The Fine Line Between Risk Mitigation and Falling Back into Covering Your Butt
The team hasn’t met its commitments once. Not once.
The atmosphere was becoming thicker by the minute. The management was displeased with the progress of the project and was looking for answers, starring at a bunch of Jira charts, I prepared earlier. “How can we claim that we are working in Scrum mode, if the team is not sticking with the rules?”
Throughout the majority of projects I have been working on I could observe an obsession with burn-down charts and other Scrum metrics, mainly team commitments. And as a consequence, a side product of backlog grooming, estimation and sprint planning is elevated to the most important management indicator that “Agile” works: The team’s commitment is matching or outperforming its average velocity.
Building a valuable, useable and feasible product does not happen overnight. These are my four core learnings from focusing on customer value, looking back at the projects I have been pursuing over the years.
Lessons Learned #1: Customers Don’t Know What They Want. And You Cannot Just Ask Them.
It’s really hard to design products by focus groups. A lot of times, people don’t know what they want until you show it to them.
Age of Product’s Food for Thought of August 21st, 2016—shared with 4,036 peers—points to 15 simple phrases from great leaders that boost team engagement. Which might prove to be helpful, when Agile will break your organization.
We also learn why removing “Agile Coach” from your profile might make the resulting 100% Scrum master more authentic, and how to land your next Scrum master position in the first place. Or your dream product manager job.
We then try to weight the benefits and potential risks of Spotify’s product squad concept, and finally have to admit that not every great product automatically creates a great business. Speaking of which: What is also not creating a great business, is a bunch of 50% solution.
Last, but not least, we come back to the question if we will have a job in ten years from now, given the advances of machine learning, and hear from Mr. Facebook himself how to build a better tomorrow. Enjoy a great Sunday!
Age of Product’s Food for Thought of August 14th, 2016—shared with 3,929 peers—finally explains why Scrum sucks, sort of, and whether agile is really about change. We learn to better understand Scrum aficionados, and that we have had so far a completely twisted understanding of technical debt.
We also learn how to build teams that can cope with today’s complexity, and that we should avoid falling for the innovator’s bias. Good news is, though, that poker is a great training for product management. (I knew it…)
We then dive deep into product roadmap strategies, and that the senior leadership needs to embrace Steve Blank, too, and get out of the building to test new ideas.
Last, but not least, we revisit the state of holacracy at Zappos.com, and get a better understanding what companies can learn from the human immune system to last at least a century. Enjoy a great Sunday!
Age of Product’s Food for Thought of August 7th, 2016—shared with 3,817 peers—lets you steal agile insights from BMW, and encourages you to redefine your attitude towards technical debt.
We also learn why the CSM certification originally was created, why public roadmaps with release dates are bordering on being moronic, and why the art of product management requires empathy. (I know, you thought that A/B testing and Analytics would suffice—sorry for breaking the bad news…)
We then dive deep into creating happiness at work, and this even seems to work in the software industry, given the lastest DZone poll among developers on agile methods.
Last, but not least, we are getting the price of our product right, at least we could fix it now, and we have an in-depth look at a place where pair programming is the norm, and not an exception. Enjoy a great Sunday!