How to Recover from Business Failure? Fail Fast, Learn Faster

By now, most readers will already be familiar with the Agile concept of failing fast. For those who aren’t, however, this is a highly influential development approach that encourages companies to take bold, decisive action, because failure — paralysing though the fear thereof may be — is simply a part of living. 

In this way, Agile developers are encouraged to keep an eye out for red flags and be ready to shift gears as soon as the need arises.

Unfortunately, however, by focusing on the term “failure,” companies are often left with more questions than actual answers. So for today’s article, Software Planet Group would like to clarify what exactly failing fast means by turning our attention to the real crux of the matter: learning faster.

Read More



Avoiding Ambiguity

Last October, Prime Minister Theresa May caused quite a stir in Parliament when she bravely announced to the world that her Brexit deal was “95 percent complete.” The widespread confusion, however, was wholly understandable. After all, with two years of negotiations behind her, what exactly did that mean? To anyone but her cabinet ministers and EU negotiators, of course, it was simply impossible to know.

The same, however, could easily take place in software development. If we told you that your project was 99 percent complete, however would you know that that pesky last percentage point wouldn’t take twice as long to finalise as the other 99 together? Again, an impossibility. For this reason, in order to avoid all potential ambiguity, Software Planet Group will always steer clear of percentages. Instead, we make use of hours, velocity and complexity points.

For more information, please contact our support team.

Read More


Why We Work with Full-Stack Developers

The “one expert per technology” mindset is as culturally pervasive as it is clearly detrimental, yet its origin is actually understandable. After all, if you have a heart condition, you go see a cardiologist, if your child has a high fever, you’ll likely take him to the paediatrician. General practitioners, on the other hand, are not typically afforded the credit they deserve.

Much in the same way, when it comes to full-stack developers, a lingering myth exists that they are somehow less capable than other software engineers.

For this reason, today we would like to compare narrow expertise and full-stack capabilities and explain why we at Software Planet are significantly more partial to the latter.

Read More


Our Fail Fast Approach: Turning Failure Into Success

From an early age, we are taught that failure is a bad thing. You should never fail exams, you aim to pass them; you don’t become something in life through a series of floundering events, you work hard to succeed and keep winning.

So when the Agile concept of “failing fast” is met with wide eyes and a spattering of bad publicity, is that really such a surprise? After all, surely we should all be striving towards success, not failure.

To be fair, such an assumption is indeed perfectly logical, yet allow us to reframe the matter by focusing on a case in point: Thomas Edison. You see, before finally succeeding at perfecting his light bulb, it is said that the inventor was first destined to see it fail — not once, not twice, but approximately 1,000 times.

Read More


What to Expect from Our Product Teams

As explained in a previous article, working on a product instead of a project demands a totally different mindset, which often makes it difficult to discern and form a winning team.

At Software Planet, however, we strive to equip our team members with the knowledge they need at all times — and of course, in product development, this is certainly not an exception.

With this in mind, we would like to spell out the various qualities our company look for when putting together our specialised teams, so you too can know exactly what to expect when entrusting us with your valued products.

Read More


The Cost of Technical Debt

We live in an increasingly debt-driven society.

Think about it. Without a credit history, you are likely to struggle to be accepted for a mortgage or a tenancy agreement, your chances of landing that job you wanted might significantly be reduced, and wonder of wonders, irony of ironies — even a basic credit card could be strictly off the table!

Perhaps unsurprisingly, therefore, in many ways, the same holds true for our software systems. While here, debt is never accumulated as a result of borrowing more funds, it does nonetheless still manifest itself by accruing dues of another kind — technical debt, as it is known.

Put simply, the term refers to the implied cost of additional work that is caused by choosing an easy solution now as opposed to taking a better, yet more complicated approach that would likely take much longer to deliver.

Read More


Software Metrics: How We Promote Transparency

If you’ve ever worked on a project where very little — if any — attempt was made to keep everyone involved up to speed with development, then you’ll certainly understand how infuriating this can be.

In fact, even those who were blessed enough to have never suffered the ordeal will more than likely still relate, at least on an intellectual level. The Dalai Lama, for instance, while never once a software guru, famously stated that “a lack of transparency results in distrust and a deep sense of insecurity.”

And naturally, here at Software Planet, we couldn’t be more in agreement.

This is why we have put in place a series of mechanisms that can guarantee that you, our valued customers, will be kept informed at all times.

Yet of all of these, perhaps the best example is that of our software metrics.

 

Read More


What to Expect from Our Estimates

If you are reading this article, our trusted business analysts have likely agreed to impart upon your project some much-needed estimates; and well, you’ve come to the right place!

After all, for today’s blog post, we would like to spell out our meticulous process for preparing estimations, the different sorts of artefacts you should be ready to receive and how this all will play out in the end — on that note, by the by, if you find that any or all your expectations have not been adequately lived up to, please do not hesitate to contact us at any time. This will help SPG to continue improving our company’s services for you as well as our future customers.

So, with this in mind and without further ado, let us dive right in!

Read More


Making the Most of Code Review

Every Agile development process strongly stresses the motif that the main goal of developers should not be to concern themselves with side issues, but rather to generate working code. This allows us to implement a variety of features in accordance with our customers’ requirements.

Unfortunately, however, out in the real world, it is crucial to not only strive to implement functionality, but also to ensure your code will be kept clean and without duplicates, being easy to understand, support and extend, makes extensive use of automated tests and presents as little as possible technical debt — that is, valuable work postponed by virtue of restrictive deadlines or other more pressing priorities.

This is why over the years, both customers and programmers have jointly devised a number of solutions for assessing code quality as well as providing projects with the appropriate level of support, throughout development. Of all of these, however, one popular technique distinctly stands out — the exceptional practice of code review.

Read More