The goal in your test cases is to validate a problem that has been solved. It starts with understanding the problem and reproducing it. If you don’t know the problem you can’t reproduce it. If you can’t reproduce it, you can’t validate the fix. One action drives another, impacts another, and makes another come to fruition. Without knowing the problem, you cannot reproduce it, without reproducing it you cannot test it. You need one to…

Every few months I get prompted to reconnect my profile on my blog to LinkedIn. It’s the only active connection I have, it never changes. But I only get alerted when I go to write a post and “gasp” Sometimes I schedule them based on when thoughts strike me. It doesn’t bother me much, I’ve had to delete it now and again when the profile got messed up. And I know I have become desensitized…

If you can’t do it through the app, there is probably an API that will you do it or a background process. And although this is great, this begs the question – why can’t you do it through the app itself? Why is it restricted?  What was the reasoning? And if you’re now doing it through the API, why do you then need the app?  What is it giving you? Give your App the same…

Don’t believe everything you read, you’re still in it. You still have 9 months in the year. You’re taking steps and making progress. Don’t stop now, if you’ve fallen behind, take a day and get back on track. But you’re not out of it unless you take yourself out of it.

When your company is new, your licensing model is simple and perhaps even non-existent. “Want our product, please take it, and thanks for using it.” “Want to use it for your team?  Here’s a team license.” “Want to use it for this building?  Here’s a site license.” Simple, achieves the goal. You might not need a license today, but if your customers need to hire a licensing expert to understand what they need to buy…