Agile Cooperation is a critical aspect of the Agile software development process, emphasizing the importance of close collaboration and communication between different departments, such as business stakeholders, developers, and operations. This principle, often ignored in practice, aims to break down silos and facilitate effective teamwork to deliver value to the customer in a predictable and repeatable way. To start small with Agile Cooperation, technical and business teams should come together to define their shared vision and goals, and regular meetings can help build trust and facilitate teamwork.

In today’s rapidly changing business environment, organizations should increasingly recognize the importance of cross-functional collaboration and seamless integration between departments. The silo mentality, where each department operates in isolation, can negatively impact an organization’s ability to respond to market changes, customer needs and new opportunities in their software development approach. To overcome this challenge, companies should turn to Agile Cooperation and Intelligent DevOps to break down silos and foster a culture of collaboration, agility and innovation. By implementing these approaches, organizations can streamline processes, improve communication, and increase their ability to deliver high-quality software in a timely and cost-effective manner. 

As the use of artificial intelligence (AI) becomes more prevalent in our daily lives, the need for responsible and trustworthy AI systems, aligned with human values and following human intent, is becoming increasingly important. In their quest to develop such systems, both Microsoft and OpenAI have outlined their approaches to responsible AI development. Microsoft has recently shared its Responsible AI Standard, a framework to guide the development of AI systems. OpenAI, on the other hand, takes an empirical and iterative approach to aligning AI with human values. In this blog post, we will take a closer look at both companies’ approaches and how they can serve as valuable resources for software teams looking to implement responsible AI in their own work. We will explore the specific guidelines and best practices outlined by Microsoft and OpenAI for responsible AI development, and how these frameworks can help ensure that AI systems are built with fairness, reliability, safety, privacy and security, inclusiveness, transparency, and accountability in mind.

On January 16th, 2023, Logius, the Dutch government organization responsible for the DigiD app, released the source code of this app to the public. The DigiD app is a widely used authentication app in the Netherlands, with over 15 million active users. The release of the source code is in line with government policy to promote transparency in government-developed software. The source code is available on Github under the EUPL license, with certain exceptions for security and privacy concerns. This release allows for greater scrutiny of the app’s security and privacy measures and enables developers to learn from and build upon the existing code.

Developing a business strategy for your software factory is essential for achieving long-term success in today’s competitive market. A strategic approach to planning and decision-making can help you align your goals with your target market, differentiate your offerings from competitors, and create a roadmap for growth. In this blog post, we’ll guide you through the strategic approaches, tactical phases and operational aspects of creating a comprehensive business strategy for your software factory. From defining your overall development process and unique value proposition, to outlining your internal communication, business model, and technical strategy, we’ll cover all the key components you need to consider. Download our white paper for our more elaborate take on all aspects, the key takeaways some final tips for success.

You might know that Spotify is very well know for their Agile methodology. But they are also very much investing in tooling for developers. Backstage is an internal developer portal that was originally built by Spotify and later contributed to the open source community. In recent years, it has gained a lot of attention within the developer community due to Spotify’s marketing efforts. In this blog post, we’ll take a closer look at the features of Backstage and discuss the pros and cons of using it as your internal developer platform. We’ll also provide some information on what you need to consider when evaluating Backstage versus other specialist solutions. By the end of this post, you should have a better understanding of whether or not Backstage is the right choice for your engineering team’s home base.

Backstage has a rich history that is closely tied to the growth and evolution of Spotify as a company. According to Spotify, Backstage was “born out of necessity” as the company’s infrastructure grew rapidly and development teams became distributed across multiple regions. This led to a fragmented and difficult-to-manage system of tools and processes, and engineers found themselves spending more time trying to get started than actually building and testing code. In order to solve this problem, Spotify began building a layer on top of its tools and infrastructure in the 2010s, which made it easier to find, use, and manage services and tooling. However, building a fully-featured internal developer portal requires a significant engineering investment. In 2020, Spotify made the decision to donate core components of Backstage to the open source community and has since worked to build a community around the project to advance its development.

Backstage: a quick introduction

Backstage is an internal developer portal built around a catalog that helps you organize all your services, data pipelines, and other resources in one place. It also includes a scaffolder tool that allows you to spin up new projects using approved architectural blueprints and a docs-as-code solution. With Backstage, you can easily keep track of all your services and key information about them, enable your engineers to quickly create new projects using established templates, and monitor basic analytics on tech health, cloud costs, language usage, and more. In short, Backstage is a powerful and convenient tool that helps you manage and organize your development resources in one central location.

Backstage Components

Backstage consists of four main components: a catalog, analytics, a scaffolder, and docs-as-code.

The Backstage Catalog is a central location for tracking and managing internal applications, libraries, pipelines, and websites. It allows engineering teams to register entities in the catalog via YAML files, which make up an index of components, APIs, and resources. The catalog expects these YAML files to be stored in your git repositories, so it can back up your catalog and make it recoverable with a complete history. You can also declare dependencies among catalog entries manually. The catalog ingests metadata about its entries from your tools via plugins that are configured in the service’s YAML. This makes it easier for teams to manage and maintain their software, provides a consistent view of all their software, and makes all the software in your company indexed and discoverable.

The Backstage Analytics component provides basic analytics on tech health, cloud costs, language usage, and other metrics. It allows teams to track the performance and health of their systems and make informed decisions about resource allocation and optimization. The analytics component also integrates with other tools and services, such as monitoring and logging platforms, to provide a more comprehensive view of your systems.

The Golden Path Scaffolder is a feature that makes it easy for teams to spin up new services while maintaining consistency across projects. You can create templates inside Backstage that, with the click of a button, create new projects in places like GitLab and GitHub. This helps teams start new projects on the right foot without having to follow strict conventions and standards. The scaffolder also integrates with other tools and services, such as infrastructure as code platforms, to streamline the process of creating and deploying new projects.

TechDocs is a component of Backstage that allows you to store your documentation with your code while still making it easy for engineers to view. Engineers write their documentation in Markdown and store it in source control, right next to their code. An MkDocs build step creates a documentation website when your CI pipeline builds the code. Backstage then pulls in the site and displays it in the portal. This makes it easy for engineers to access documentation without having to leave the Backstage interface. TechDocs also integrates with other tools and services, such as search engines, to make it easier to find and access documentation across your organization.

Pro’s and Con’s

One of the main pros of using Backstage is that it provides a central location for tracking and managing internal applications, libraries, pipelines, and websites. This can be especially useful for large organizations with distributed engineering teams, as it helps to provide a consistent view of all the software assets and resources available to the team. The catalog feature also makes it easy to declare dependencies among catalog entries and to ingest metadata from other tools and services via plugins.

Another pro of Backstage is that it includes a scaffolder tool that makes it easy for teams to spin up new projects using approved architectural blueprints. This helps to ensure consistency across projects and can save time and effort for teams that would otherwise have to follow strict conventions and standards.

One potential con of using Backstage is that it requires a significant engineering investment to set up and maintain. This may not be feasible or desirable for smaller organizations or teams with limited resources. In addition, Backstage may not be the right fit for organizations with very specific or unique requirements, as it may not offer all the features or customization options that they need.

Another potential con is that Backstage is a relatively new project, and as such, it may still have some rough edges or areas that need improvement. While the project has a growing community of contributors, it may not yet have the level of support and resources that more established solutions offer. It’s important to carefully evaluate your needs and resources when deciding whether or not to use Backstage.

Conclusion

In conclusion, Backstage is a powerful and convenient tool that can help engineering teams organize and manage their resources in one central location. With its catalog feature, teams can track and manage internal applications, libraries, pipelines, and websites, and declare dependencies among catalog entries. The scaffolder tool makes it easy to spin up new projects using approved architectural blueprints, saving time and effort for teams that would otherwise have to follow strict conventions and standards. And with TechDocs, teams can store their documentation with their code while still making it easy for engineers to view.

Overall, Backstage is a valuable resource for engineering teams looking to streamline their workflows and improve efficiency. Its combination of features and integrations makes it a powerful tool for managing and organizing resources, and its open source nature means that it is constantly evolving and improving. If you’re considering using Backstage for your team, we highly recommend giving it a try. We think you’ll find it to be a valuable addition to your engineering toolkit.

A growing software team can be like a well-oiled machine. With the right culture and processes in place, your team can churn out quality software at an impressive rate. But to create a true “software factory,” you need more than just a team of skilled developers. You also need to engage managers who understand how to participate in the process, QA testers to make sure everything works as it should, and support staff to help with customer service and other tasks. With the right people in place, your software team can become a true force to be reckoned with!

In this blogpost we are going to look at the software team itself. Creating a software development team that functions well together is not an easy task. However, if you put in the time and effort to cultivate synergy among your team members, you will be able to reap the benefits in terms of productivity and morale, but most of all: you will create a great atmosphere in your company!

A well-functioning team will have individuals with complementary skills who can work together smoothly to achieve common goals. But what makes for a great software development team? And how can you ensure that your team functions at its best?

One way to create team synergy is by establishing common goals and working towards them together. This can involve brainstorming sessions where everyone has a chance to share their ideas, as well as regular check-ins to ensure that everyone is on track. Additionally, it’s important for team members to feel like they are part of a larger whole, so make sure that they are included in decision-making processes whenever possible.

If you use scrum within your organization these brainstorming sessions will be called refinement meetings. Refinement is a core part of scrum but often neglected. Keep in mind that it’s nice to get the whole team involved in a refinement meeting, but sometimes it’s just as relevant to do the brainstorming with just a few people working on a particular topic.