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.
Skill matrixes support self organization in teams and help to create intrinsic motivation, where people want to learn new things. They can show how cross-functional teams really function and provide insight into bottlenecks found in teams.
Alexandre Magno, author of the book ”How Creative Workers Learn", gave a masterclass at the Scrum Gathering Portugal 2016 showing the power of the practices that emerge from the inside of an organization instead of being imported from the outside.
When you want to scale the number of A/B tests to do many experiments at the same time, you need to adopt your processes and platform, and it might also impact your culture. Doing product research with controlled experiments helps to confront your ideas about how customers will use your product in reality, and check if those ideas actually impact user behaviour.
The Cloud, infrastructure as code, federated architectures with APIs, and anti-fragile systems: these are technologies for developing software systems that are rapidly coming into focus, claimed Mary Poppendieck. Systems are moving towards the cloud, and APIs are replacing central shared databases and enable the internet of things. We need to develop anti-fragile systems which embrace failure.
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.
New code developed for GOV.UK will be open by default. Coding in the open enables reuse and increases transparency. The UK government wants to provide digital services which are so good that people want to use them; services which are leading to better interaction between the government and citizen.
The impostor syndrome refers to people who fear being exposed as a "fraud". They think that they do not belong where they are, don't deserve the success they have achieved, and are not as smart as other people think. According to Agile Coach Gitte Klitgaard, many high-achieving people suffer from the impostor syndrome. It hinders people in their work and stops them from following their dreams.
At the recent Agile 2016 conference, InfoQ spoke to Kyle McMeekin about the real world challenges around software testing in agile development, the push to have more test automation and how exploratory testing is different from and more effective than scripted manual testing.
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.
Giving teams autonomy to spend 10% of their time for learning reduces delivery time, increases quality, and increases motivation. The 10% rule gives teams full autonomy to work on things they consider important. It results in freeing up people's creativity and letting teams grow their potential.
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.
Scalability should be considered when developing a Minimum Viable Product (MVP). An MVP needs to be technically scalable and you need to have a plan on how to scale quickly when your MVP attracts many users and becomes successful. Knowing your possible performance bottlenecks and using common sense while developing your MVP will get you very far, says Erik Duindam, CTO at Unboxd.
If you want continuous improvement you can start with retrospectives, but you must go far beyond that with change management, culture change, and innovation. The most important thing in order to make change happen in organizations is creating new habits and changing your culture.