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.
At the Agile on the Beach 2016 conference, held in Cornwall, UK, Rebecca Parsons argued that the requirements for improved time-to-market and increased business agility can be achieved by architecting software for real evolvability, keeping systems poised for change, lowering the cost (and risk) of experimentation, maximising visibility and feedback, and aligning the organisation.
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.
Bias, priming, and salience are the main psychological factors that influence our ability to estimate. Knowing what happens psychologically when we estimate, and using techniques from psychology, helps us to deal with those factors so that we can improve our estimations argued Joseph Pelrine, social complexity scientist and PhD researcher in psychology.
Docker in Action, written by Jeff Nickoloff, provides a comprehensive introduction to Docker and how to integrate it into a development workflow. This book is intended for developers and operations engineers who wish to adopt Docker for application development and integrate it into their software delivery process.
Eduardo Salas is recognized by the APA for his 30 years of research on team work. His implementation of team training includes defining team structure, identifying specific communication needs, clarifying roles and leadership skills, and practicing with scenarios. This technique has been used across many fields of work, and is part of the program as NASA prepares to send a team to Mars.
The Agile Alliance hosted a one-day Executive Forum in San Jose, CA on September 19. The event attracted participants from around the world and a range of senior speakers from large organisations, and focused on how adopting agile development impacts companies and what executives need to do to help ensure successful cultural transformation, which is what agile adoption at scale is about.
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.
Refactoring helps to move towards cleaner code that is easier to understand and maintain. It takes practice and experience to recognise code smells: symptoms of bad design which indicate deeper problems in the code. Tools can be helpful to refactor in small steps and prevent breaking the code.
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.
Alistair Cockburn recently posted his viewpoint on the history of the Agile Manifesto, from the perspective of one of the original authors and signatories. He encourages readers to understand the perspective taken at the time by the authors, and also to explore the ongoing work of many of the original signatories. The original authors explicitly refuted the idea of rewriting the manifesto.
People stopped seeing the need to define the architecture or do software design due to incorrect interpretation of the agile manifesto, argued Simon Brown. Many software developers don’t seem to have a sufficient toolbox of practices and the software industry lacks a common vocabulary for architecture. A good architecture enables agility with just enough up front design to create firm foundations.
At the recent Agile 2016 conference Lee Cunningham, VersionOne’s Senior Director of Enterprise Agile Strategy, spoke to InfoQ about scaling agile, expanding agile beyond IT, identifying value and the direction of the VersionOne platform.
At the sixth ‘Agile on the Beach’ conference, held in Cornwall, UK, several leading practitioners of agile software delivery presented the state-of-the-art and emerging trends within this domain. Key takeaways included the value of the scientific method to drive change; the use of Continuous Delivery (CD) for improving safety and speed; and the power of cognitive bias during the user testing.
Increased throughput, reduced code complexity, less production incidents, shorter deployment cycles and higher happiness in teams; these are some of the benefits that the agile transformation at Barclays has delivered. Within the first year of the transformation, which is based on Disciplined Agile, more than 800 teams adopted agile making this one of the largest agile implementations.