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.
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.
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.
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.
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.
Data science is about the data that you need; deciding which data to collect, create, or keep is fundamental argues Lukas Vermeer, an experienced Data Science professional and Product Owner for Experimentation at Booking.com. True innovation starts with asking big questions, then it becomes apparent which data is needed to find the answers you seek.
Continuous deployment results in a higher sense of responsibility and better quality of deployments, argues Paul de Raaij, technical pathfinder at Coolblue. Coding standards prevent your code base from becoming a mess, automated inspections are great for tedious and boring checks, and manual checks are great for checking if the logic or use of code actually makes sense.
Good engineering practices are the tools that help agile teams to deliver shippable products. Although many engineering practices have proved to be effective, they are not as widely used as they should be. Agile anti-patterns like the software testing ice-cream cone, accumulating technical debt and functional silos prevent teams from delivering a potentially releasable product.
At the Agile 2016 conference Andy Hircock, Mike Lowery, and Rob Vandenburg, discussed how they transitioned to persona-based teams, instead of feature or component based, and how they used this to help teams keep focused on their customers despite significant growth.
At the recent Agile 2016 conference in Atlanta, Joshua Kerievsky, CEO of Industrial Logic and author of "Refactoring to Patterns" gave a thought-provoking keynote around the idea of Modern Agile.
Johanna Rothman gave a talk at Agile 2016 about measurements for agile program management. She explored the challenges around selecting what to measure, how traditional measurements don't provide the right information to make decisions from and provided examples of measurements that can be useful.