If you’re a project manager, you have probably heard of and are likely to have used the Product X in the comparison below. It’s overall a strong product that does a lot more than most of us need it to do. Some other SaaS products aimed at enterprise-wide license penetration (Product X also has such a version) have code bases and logic similar to Product X and so may share many of the strengths and weaknesses in common, which is the main reason I haven’t named it.
I built Proper Plan because the several other products I have used do an awful lot that I don’t need, and partly as a result of that, do a lot of the things I really need not well enough for my own satisfaction. You can read my summary beneath the analysis, which of course I have tried to make as unbiased as possible. Of course it is subjective and I am bound to carry some bias.
My own personal motivations for building Proper Plan were to make a much more usable product that did all of the things I really need, really well. It’s therefore no surprise that I score Proper Plan much higher on usability, whilst it only just edges on capability. Many of you may use other tools in different ways to me and so your analysis might be different. But if much of the above sounds familiar to you, and you spend more time than you’d like wrestling with your plan at the expense of managing, refining and updating it, and waste hours generating manual dashboards and other reporting, then Proper Plan is probably for you.
Instructions:
Ever struggled to justify the duration you’re proposing for complex landscape end-to-end testing cycles, including user acceptance testing? Being asked for objective justification? I’ve encountered it more than once and so I built a modelling tool with an algorithm that combines all the factors. Download and have a play if you think it might be useful.
