“What is the value of a Scrum Master?”
This question may very well be on your mind if you’re about to sign a software development outsourcing contract and need to decide on team composition.
Paweł Jurdeczka—one of the most experienced Product Owners and Scrum Masters at STX Next—sat down with me to solve the mystery of the elusive Scrum Master and dispel any doubts about them once and for all.
Read on to learn everything you need to know about the role of Scrum Master and the value they introduce to your team.
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.
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.
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.
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.
It might seem that software development and predictable results go together like fire and water - which is to say, not at all. Your developers might hit unexpected snags, productivity varies between Sprints and it's difficult to say how much exactly will be done, and when.
But it doesn't have to be that way. Introducing: burndown charts.
A burndown chart enables the monitoring of work progress in a Sprint and in a product release by clearly visualizing the difference between the actual and forecasted effort.
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.
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.
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.
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!