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.
Being a software developer is all about constantly honing your skills. But how do you find the time to grow professionally, living in a world where there’s hardly any time to waste?
It’s simple: you learn on the run.
Whether it’s commuting, working out, or taking a walk, just grab a phone and a pair of earphones and you’re good to go.
Well, not quite. You’ll also need some killer listening material.
Here is a list of podcasts and audiobooks to help you become a better developer—if you only listen.
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.
At STX Next (and your company too, I’d wager), all employees are offered a training budget to improve their skills and competences. We can spend the money on training, conferences, workshops, or books. As long as the training is in line with your position, you’re good to go.
Since the new year is in full swing and our budgets are renewed, you may be wondering about the best way to spend your training budget. That’s why I’ll be sharing my experience using my training budget in 2016 and 2017. I hope this will be an inspiration ...
Whenever you’re managing a team of developers, productivity problems may occur.
Productivity may be an overused word these days. But in the end, aren’t we all looking for results?
Hours of development work don’t come cheap these days - and yet when you ask the team about progress during a Sprint, it’s almost always a disappointment.
It’s a common situation - but it doesn’t have to be your reality. It is possible for you to call your devs and hear that everything is done according to the schedule. They might ask you eagerly for more work ...