News

Sociocracy 3.0 is an open framework which supports collaboration in agile organizations and helps them to continuously improve products and services. The framework provides patterns for activities like coordinating work, effective meetings, governance, and building organizations.

More and more now value is created through connected organizations and individuals using seamless collaboration across boundaries. At the same time however, many companies are still influenced by management practices invented in 19th century. A paradigm shift is needed to successfully manage in the networked society.

Alan O’Callaghan gave a presentation at the Scrum Gathering Portugal 2016 on what José Mourinho can teach us about team building. Starting with the similarities between Football and Scrum, the talk addresses the less understood characteristic that affects Scrum’s effectiveness, that is, according to the speaker, the building of self-organising teams.

To remain agile while offshoring software development, you have to invest time to make agile practices work under conditions where they are not supposed to work. Giving up is often not an option; you need to stretch agile practices by going back to the principles and collaboratively find ways to scale them and make them work effectively in a distributed environment.

People are hardwired to instantly decide who we trust, but also to work collaboratively in small groups. Cognitive biases can get in the way of collaboration, but when you understand how these biases work and what agile practices can do to help, you are more likely to build better interpersonal relationships and create successful products.

To drive operational maturity you need a microservices architecture, continuous delivery process, DevOps culture and platform automation. Together these four help you to transform your whole organization for achieving cloud-native operability to continuously deliver additional value to your customers.

Continuous delivery should be treated as an agile project as it is about automating your deployment. You have to speed up in small steps and gain trust by doing small deliveries and solve problems fast. The story about how Klaverblad insurance has implemented Agile, DevOps, continuous delivery, and microservices.

The Spotify model can help you to understand how things are done at Spotify, but you shouldn’t copy it in your own organization. It changes all the time as people at Spotify learn and discover new things. There is no one way in which software is developed at Spotify.

When developing a high speed printer based on a new print technology things change often; you need an effective and flexible solution for managing a large project with many different disciplines. Océ Printing Systems decided to customize Scrum and scale it to enable collaboration and make progress transparent.

Ordinariness in leadership can help us to accomplish extraordinary results, argues agile/lean coach Katherine Kirk. Several more people have explored approaches that suggest to rethink leadership and go back to behaviour basics for leading people. Although these approaches are about small ordinary things, their effect may cause a revolution in the way organizations are being managed.

Cross-cultural team building enables collaboration and teamwork in dispersed or distributed agile teams. You need to invest to get the best out of a dispersed team. An exploration about what is needed to make agile work with dispersed or distributed teams.

Truly agile is what you are, and to become agile you need to overcome paradigms, argues Arie van Bennekum, co-author of the agile manifesto. It takes "being agile" and not "doing agile" to achieve success. Agile is an interaction concept based on the values and principles of the agile manifesto. Technology facilitates agile working, but tools don’t make you agile.

The Agile community has lost a thought leader, influencer and friend, Jean Tabaka, who passed away earlier this week. She was best known through her work as an Agile Fellow at CA Technologies (formerly Rally Software) and author of the book "Collaboration Explained: Facilitation Skills for Software Product Leaders".

InfoQ interviewed John Willis about what made him decide to talk about burnout, the possible effects of burnout for a person, how burnouts are impacting the software development industry, leading indicators of a potential burnout and how they can be used to prevent burnouts, and suggestions for dealing with mismatches between employees and organizations that can cause a burnout.

Is your profile up-to-date? Please take a moment to review and update.

Email Address

Note: If updating/changing your email, a validation request will be sent

Company name:

Keep current company name

Update Company name to:

Company role:

Keep current company role

Update company role to:

Company size:

Keep current company Size

Update company size to:

Country/Zone:

Keep current country/zone

Update country/zone to:

State/Province/Region:

Keep current state/province/region

Update state/province/region to:

Subscribe to our newsletter?

Subscribe to our industry email notices?

You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.

We notice you're using an ad blocker

We understand why you use ad blockers. However to keep InfoQ free we need your support. InfoQ will not provide your data to third parties without individual opt-in consent. We only work with advertisers relevant to our readers. Please consider whitelisting us.