A deep dive into 3 steps to Grow Your Product Mindset and creating products your customers love.

1. Identify the Problem “Discovery is the new knowing.”

2. Value is what your customer is willing to pay for “Stop thinking about your customers and start thinking like them.” ~Chris Spagnuolo

3. Validate the Outcome “We don’t know what’s possible with technology—none of us really know until we actually see it." ~Marty Cagan

Unless you have been living on a remote island unconnected from civilization for the past few decades, you have no doubt heard the term “servant leadership.” It has a very interesting past and may go back farther than you think.

In Agile regression testing, a software programmer’s primary job is to still create code, but rather than leaving the task of finding any bugs to testers, they're expected to check their code as its created for errors.

I get often asked when I work with people or teach a class how to show real progress on an Agile project. Roadmaps, Release Burnup's, Velocity, how to answer questions on delivery. We build products for external clients using Scrum and will show people how we visualize progress sprint by sprint for our customers. Showing how velocity changes, roadmap, release plan changes and most importantly how customer feedback has affected the release date. This isn't hypothetical talk but real world experiences and conversations.

However, first I will start out with showing the old ways of doing things with Gantt charts. Why the traditional way doesn't work. Comparing the Green, Yellow, Red method and how it doesn't work. The roll that into the better, agile mindset of delivering questions like when will be done, what will we get and how we communicate good and bad news to our clients.

I've linked some information for those that are interested in learning more about the ethos of Pair Programming. For this post we are assuming you, the reader,  are either familiar or already use this technique. This post will introduce some ideas to improve your Pair Programming environment.

I had the pleasure to work with The Braintrust Group and review their book to provide feedback and editorial comments. It has now been published up on Amazon. I definitely would recommend this book for anyone new or experienced with Scrum. It has a lot of interesting tips and real world problems/solutions as well as pitfalls to look out for....The great thing about the book is that the word "software" isn't used once.