In any organization, large or small, a defined strategy and tireless accountability are essential to making sure all teams are aligned and focused as they go about their day-to-day work. For a company operating in a scaled agile environment, where teams are empowered to make decisions, strategic context must be crystal clear to create a trusting environment where teams can do their best work and drive business results.

By 2022, the skills employees will need to thrive will include creativity, trustworthiness, emotional intelligence, and leadership, according to the World Economic Forum’s Future of Jobs Report 2018. Intelligence matters. But recently, business leaders have begun to place more emphasis on “soft skills” – you know, those intangible qualities that make the difference between being a dear or dreary coworker.

Since the inception of Glo Boards for task and issue tracking, the GitKraken team has continued to add robust features that allow developers to be more productive. And our latest addition is no different. GitKraken Glo Boards now supports linking GitHub pull requests with Glo cards.

It’s been a few years since the “Spotify Model” became the latest trend for structuring an engineering team. But, like its predecessors, the model based on tribes and squads has some pitfalls. How to structure an engineering team is a question that’s been covered at length, from the strengths and weaknesses of common team structures to a matrix of organization based on risk and scale to why you should choose your own model.

At first, learning software development can feel like being lost in a maze…like the weird, scary maze from the Labyrinth. You’re learning languages upon languages, equations and variables, time management and organization – it’s madness I tell you, madness!! But fear not! Learning software development in 2019 means that you have numerous tools at your disposal to help ease the transition from normal human to coding master. And the best part?!