Sourcery Academy for Product Managers, a four-week educational program in Chicago, concluded with a grand finale last week. This video summarizes Sourcery, why we organized it, and why we think it's important for the field of product management.
Metrics are an important tool for product managers, but metrics alone don't solve problems. Metrics are a starting point for conversations about objectives, and how we're progressing toward meeting them—metrics aren't the end of the story, but rather the beginning. This article explores how product managers can use metrics to create a vision for a product, then work with teams to execute that vision.
We’re proud to announce Sourcery Academy for Product Managers, a four-week course will provide hands-on, real-world experience and insight from Devbridge employees and leadership. We believe the best way to learn is by doing. That's why we've created a curriculum that puts you in the driver's seat. You'll build your knowledge through first-hand experience, working alongside some of the brightest minds in the industry.
Defining Lean Requirements helps accelerate software development by shortening the cycle time to gather requirements. Over the past few years, we've continued to iterate and grow this approach. This article shares what we've learned in that time and explains how we use Lean Requirements in more detail.
Role definition and change management are the most difficult obstacles to overcome for large organizations that adopt Agile. Employees can feel threatened and pushed out of their comfort zone by the barrage of changes—from the process they use, to the changes in titles, the reporting structure, and the focus on results versus risk mitigation. This article explores how best to facilitate role changes during an agile transformation.
Have you had the same requirements-gathering discussion multiple times but still don’t know what to do next? Does your team shudder when they see you break out sticky notes in a meeting? (Hint: If you answered yes to either of these questions, keep reading) Practice the five skills outlined in this post for effective workshop facilitation.
When developing a product, it’s important to build things the right way—high-quality code that’s tightly aligned to requirements. But even perfectly built software is worthless if it has no value to the end user. That’s where results-driven development comes in. We explore how to build products the right way, while making sure we're building the right products.
The concept of Dual-Track Scrum was first evangelized by Marty Cagan back in 2012, and more recently elements of it have been incorporated into Google's Design Sprint. We recently wrote about how Dual-Track works from a design perspective, and want to demonstrate how it can be applied in practice. By leveraging Dual-Track Scrum, teams are more focused, reduce their rework and significantly improve their ability to plan while still retaining their agility. In this article, we'll review the benefits of Dual-Track Scrum and show how we implement it in practice using agile tools.
In a recent post, Aurimas talked about product thinking—building what your customers need, and a culture of innovation. In that post, he mentioned a recent workshop wherein one of the executives asked how we could avoid failure. Figuring out a Minimum Viable Product (MVP) is a great place to start. But how do you create a good MVP? And why?
Estimation. Such a hotly debated, time-consuming exercise. Are they a necessary evil? Should we eliminate estimates? Where do we stand?
Defining software requirements can be messy. The traditional process is bloated and overweight. It’s time to lose that weight and get your requirements lean.
At Devbridge, when we work with our clients on projects, it’s essential for everyone to understand the big picture. When our clients have a hard time visualizing and communicating their vision and strategy, we help by working with them to create a visual product roadmap by way of an approach called "story mapping".