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 ...
So you’ve gone through the effort of hiring a team of software developers for your project. Now is the time to manage their work. How do you get the most out of their skills?
I’ve talked with Rafał Gajewski, one of our Service Delivery Managers, to find out what his experience can tell you about managing software developers effectively.
How can you save money and effort as a manager for software developers? We recommend focusing on 4 areas in particular that yield the best results.
Not too long ago I heard a developer sharing this gem of wisdom: “Resolving technical issues is much easier than those of a personal nature.”
It was quite a surprise to hear it. I don’t think it is a popular thing to say, especially not by a person with a programming background. On the other hand, it sounds like a natural thing: technical problems are rational and we can resolve them using our reasoning skills. The only question is whether you are capable to think in abstract terms to find the solution.
Personal issues, or let’s call them ...
Not so long ago, I presented the basics of the Scrum framework based on my interview with Dominika Brzezińska. In that article, I promised to go deeper into the subject and talk about the common criticisms directed towards Scrum (and Agile as well, to some extent).
The moment has come to deliver on that promise.
To learn more about common Scrum misconceptions, including what Dominika calls the Number 1 Scrum Mistake, just click the button below.
When you select software professionals to work with, you want them to know their game. You may go through tens or hundreds of their previous projects, but you are still vulnerable. You are out of your area of expertise and you are about to face the first challenge: signing a contract.
We're here to help you tackle this challenge. This list will help you spot the most common traps in software development contracts. Click to learn how to avoid copyright issues and ensure a fair and productive relationship.
While working in various IT projects I realized that regardless of all these ‘lean’ product development movements, many companies still encounter major issues in terms of product validation. In other words - it is hard for people to understand if the product they develop is what the market desires.
To help you with your validation efforts, I’d like to give you an inside look into the day-by-day product validation process for a live product that we have worked out with one of our clients. Let’s start by answering the fundamental question: What is product validation?
Being a CTO (Chief Technology Officer) takes insight and vision, in technology and business alike. Part manager, part software engineer and part entrepreneur, the CTO can benefit from a wide range of sources to brush up both on the newest developments in tech and to shape the software philosophy of the company.
We know it might be challenging to find useful reading material, or a strong starting point for newly-appointed CTOs - which is why we’ve created this list of must-read books for CTOs. Let’s begin!
They say that a job well begun is half done. Software development projects are no different.
Each software development project starts with a project kickoff. My work at STX Next involves quite a few of those, so today I’d like to share what you can do to ensure your kickoff is as productive as possible. I've also included a sample kickoff agenda and the checklist I use to measure kickoff success.
Transitioning to agile software development brings with it a set of new roles and concepts which can be a bit murky at first. One of those roles is the Product Owner.
If you’re looking to hire a software development company, they’ll recommend adding a Product Owner to your team, and for good reason. If you feel like you can do without one, read on; you might change your mind once you discover the many responsibilities that the PO can take over to facilitate development and improve your product.
You can start by closing your eyes.