Let’s say you have a working product, a growing number of customers, and a lot of ideas for new features.
Great! Now what?
It’s one thing to hit the ground running, and something else entirely to keep going. You need a plan for the future and you need it fast, otherwise your lucky streak will end before long.
So where do you start? What do you do first?
Two words: product analytics. Use product analytics tools to develop your software product the right way.
It’s okay to be a little nervous when you first start working with an outsourced development team.
After all, ordering a remote team to code for you can feel like putting your eggs in some mysterious basket. Hidden in a black box. Hundreds of kilometers away. And still expecting a return on investment!
But it doesn’t have to feel that way. No matter the time or space, a remote team can work with you almost as closely as if they were right beside you.
In 2018, software houses have the tools and proven practices to make that happen.
Team composition is one of the key aspects you need to consider when launching a software development project.
The value of some roles is clear from the get-go. For example, developers and testers write and test the code, respectively. However, roles such as Product Owner or Scrum Master are a little less straightforward.
So why do you need a Product Owner?
That’s the question we’ll be answering in this article, from both your perspective and the perspective of your development team, highlighting the potential benefits.
SuttaCentral approached STX Next for support with a website collecting early Buddhist texts and their translations. They wanted their product to be easy to access, simple to use, and available to all.
To that end, we helped the client build a Progressive Web App to provide them with offline functionality and a mobile component.
As a Product Owner, working with SuttaCentral has been an absolute highlight of my professional career. This is a story of the deciding factors that made our cooperation a glowing success.
We all want our companies to be something... more.
Beyond mere machines to churn out profit, we want to grow into organizations that represent something: a change in the world that we want to make reality.
We want the people who work with us to feel an unmistakable vibe, a character that is uniquely ours. This applies to co-workers and clients alike.
The road to building such an organization is long and full of surprises. But one step you can’t skip is spending some time to think about your core company values.
Over the last 13 years, STX Next has always been characterized by continuous growth, improvement, and exploration. Our decision to implement new technologies in 2018 is a direct result of that philosophy.
We have taken an active interest in Artificial Intelligence, Machine Learning, Internet of Things, Golang, Blockchain, and React Native. At the same time, we remain faithful to Python.
To continue creating exciting growth opportunities for STX Nexters, we are also putting together events such as the Tech Power Summit—our company’s annual international conference.
And the best part? We’re just getting started.
Are you a software tester?
Looking to hire software testers?
Want to know where to find the best software testers in Europe?
If you responded “yes” to any of these questions, you’re in luck. Mark your calendar and don’t miss out—the eyes of the entire European software testing scene will be turning to Łódź on May 28–29.
Why, you may ask? That’s when TestingCup 2018 takes place.
We get a lot of emails from CTOs, many of whom write to us with concerns about outsourcing software development.
One particular problem has stood out in our recent correspondence: moving development back in-house after concluding your outsourcing business.
Handing your software project over to you should be seamless. Scaling down or ending cooperation with an external software house is perfectly natural.
Here are some of the practices we recommend for an optimal knowledge transfer and a smooth handover process.
Speed is essential in business; you need to move, ship, and validate your product as quickly as possible. The same principle applies to Minimum Viable Products.
Some time ago, a client approached us with a clear, but demanding idea for a fintech platform. The greatest challenge there was the set deadline of 5 weeks.
It wasn’t easy, but my team and I persisted and delivered the MVP on schedule and within the planned scope.
Want to know how we did it? Here are my 5 tips for building a successful MVP in 5 weeks.
Whether you're an up-and-coming developer, a seasoned player in the coding business, or a successful investor, your resources are likely stretched thin and you may be understandably concerned about the quality of your software.
Code, after all, is the beating heart of your product, whatever it may be, and as such you deserve to be sure that it is top-notch.
A fail-safe way to achieve that guarantee is code review. Here is why.